-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix Witness limits #1958
Fix Witness limits #1958
Conversation
@neo-project/ngd-shanghai Test? |
// Invocation = 11 * (64 + 2) = 726 | ||
InvocationScript = reader.ReadVarBytes(744); | ||
// Verification = m + (PUSH_PubKey * 21) + length + null + syscall = 1 + ((2 + 33) * 21) + 2 + 1 + 5 = 744 | ||
VerificationScript = reader.ReadVarBytes(760); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These seem to be too perfectly calculated to me. I'd rather have some simpler values here like 2048 or 4096 so that we would have at least some reserve for the future.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1024 and 1024 ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't have any strong opinion here. 2048 seems to be a bit more future-proof to me, but 1024 is already better than 744/760.
@neo-project/ngd-shanghai any update? |
* Fix Witness max size * Fix comment * Fix comment * Change it to use constants * Changed to 1024 * Fix UT
* Fix Witness max size * Fix comment * Fix comment * Change it to use constants * Changed to 1024 * Fix UT
The committee signature (21/11) can't fit with the current limits.