Update ERC-3009: Replace EOA v,r,s signature with generic bytes signature #1013
+8
−20
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
eip-review-bot
changed the title
atimark
approved these changes
May 2, 2025
atimark
approved these changes
May 2, 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.
ERC-3009's external functions support limited signature types by enforcing a
v,r,sinterface. To support a more generic interface, parity with ERC-1271 is a simple change that expands potential users to include smart contract accounts. Note that USDC, the leading example of ERC-3009, actually implements copies oftransferWithAuthorization,receiveWithAuthorization, andcancelAuthorizationwith the proposed interface here for the exact same reason.This PR's goal is to formalize this approach to simplify integration of smart contract accounts and more.