Skip to content

Conversation

@lightclient
Copy link
Member

This is a rough, initial sketch of the core changes for EIP-7701. The following spec questions remain:

  • pseudocode doesn't check if tx.deployer is non-nil when sender has no code
  • should CallWithRole be able to pass data instead of using txparam?
  • roles and top level access to tx params will make it easy to discriminate against AA txs, is this an issue?
  • what is the point of returning data from different roles? isn't accepting the role sufficient?
  • accept role should take the role as stack element (not really defined yet)
  • should remove authList from 7701 tx type
  • need to define opcode for instructions CURRENTROLE and ACCEPTROLE
    • define gas for ops
  • how does 7701 interplay with 7623
  • doesn't define what happens when param id is out of bounds
  • tx_hash_for_signature not defined
  • access list and auth list hashes not defined in tx param

Comment on lines +169 to +170
AllData []byte
TotalGasLimit uint64
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Really dislike these fields, will find a cleaner way to expose this data. Mostly need to decide if we will repurpose Data and GasLimit for this and make separate SenderExecutionData and SenderExecutionGas to fulfill their current role.

@lightclient lightclient changed the title all: implement EIP-7701, native account abstraction core: implement EIP-7701, native account abstraction Jan 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant