[core] check for excessive secp256r1 signature verification in the banking stage#3938
Merged
samkim-crypto merged 1 commit intoanza-xyz:masterfrom Dec 6, 2024
Merged
Conversation
samkim-crypto
force-pushed
the
excessive-secp256r1
branch
from
8a5ae6c to
cb39410
Compare
jstarry
approved these changes
Dec 5, 2024
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Problem
The secp256r1 precompile (#3152) was added, but it is not yet incorporated in some of the logic in the monorepo. In particular, we do not check for excessive secp256r1 signature verification in the banking stage.
Summary of Changes
Added logic to check for excessive secp256r1 signature verification.
Fixes #