-
Notifications
You must be signed in to change notification settings - Fork 185
FIPs: Add draft for EIP-7702 (Set Code for EOAs) #1209
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
base: master
Are you sure you want to change the base?
Conversation
|
|
||
| #### Delegation Indicator | ||
|
|
||
| When a delegation is active, the EOA is virtually associated with a 23-byte delegation indicator bytecode: |
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.
what is the meaning of virtual association?
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.
Thank you for raising this point. The term 'virtually' introduced an ambiguity that was not intended for the technical specification. I have removed the word from the document, and believe this improves clarity and precision.
Clarifies the relationship between the EOA and the delegation indicator bytecode by removing the term "virtually," which was flagged as ambiguous during review. The EOA is effectively associated with the bytecode during active delegation.
|
@snissn let's assign this number |
EIP-7702 defines a new EIP-2718 transaction type (
0x04) that includes anauthorization_list. Each authorization is a signed tuple from an EOA (the "authority") designating a smart contract (the "delegate") to execute on its behalf.This FIP adapts EIP-7702 to the FEVM architecture. The implementation introduces a new method,
ApplyAndCall, in the EVM actor. This method atomically processes the authorization list—validating signatures, updating the delegation mapping, and incrementing authority nonces—and then executes the outer transaction call. The FEVM interpreter is updated to recognize these delegations: when aCALLtargets a delegated EOA, the interpreter executes the delegate's code within the authority's context. This implementation ensures that delegation mappings and nonce increments persist even if the outer transaction call reverts, adhering to the EIP's specified atomicity model.Discussion: #1143