feat: add preferVerificationMethod to verifyMessage / verifyHash#4395
Closed
jacopo-eth wants to merge 1 commit intowevm:mainfrom
Closed
feat: add preferVerificationMethod to verifyMessage / verifyHash#4395jacopo-eth wants to merge 1 commit intowevm:mainfrom
preferVerificationMethod to verifyMessage / verifyHash#4395jacopo-eth wants to merge 1 commit intowevm:mainfrom
Conversation
|
|
@jacopo-eth is attempting to deploy a commit to the Wevm Team on Vercel. A member of the Team first needs to authorize it. |
bdf8494 to
69e0d6e
Compare
Member
|
Closing in favor of #4405. |
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.
Adds an optional verification preference for cases where the caller already knows the signature should be verified as an EOA.
Today,
verifyHashandverifyMessagealways begin with the default universal verification flow. That is the right default for interoperability, but in contexts where the verification method is known in advance, it can add unnecessary latency and RPC calls. For EOAs specifically, verification can often be resolved locally via signature recovery, so this change allows callers to prefer that path first.What changed:
VerifyHashVerificationMethodpreferVerificationMethodparam toverifyHashandverifyMessage