Fix >23 nodes multitransfer in frostfs-adm #352
Labels
No labels
P0
P1
P2
P3
badger
frostfs-adm
frostfs-cli
frostfs-ir
frostfs-lens
frostfs-node
good first issue
triage
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#352
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We have 1024 byte limit on a tx witness invocation script.
740488f7f3/pkg/core/transaction/witness.go (L10)
Committee of >23 nodes effectively can't sign anything. (signature is 64 byte, we have 16 signatures needed, 16 * 64 = 1024).
I am not sure we can simply fix this, though.
Let's at least document the behaviour first:
It seems the doc is already here
// MaxAlphabetNodes is the maximum number of candidates allowed, which is currently limited by the size
helper
in part of reading alphabet wallets #1203