Update EIP-3026: fix input size specification in G2 multiexponentiation ABI #9711
+6
−7
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
c-update
File
|
eth-bot
changed the title
|
The commit 3b74d9b (as a parent of ba27bfb) contains errors. |
g11tech
reviewed
May 6, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
corrected an error in the ABI for G2 multiexponentiation section. It previously stated that the call expects
240*kbytes, but this contradicts the encoding sizes defined elsewhere (192 bytes for a G2 point + 64 bytes for a scalar = 256 bytes per slice). updated it to256*kfor consistency with the rest of the spec and the gas cost calculation logic.also clarified the input length validation rule to explicitly require a multiple of 256.