Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Update EIP-7702: Update eip-7702.md #9032

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
+5 −2
Open

Update EIP-7702: Update eip-7702.md #9032

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions EIPS/eip-7702.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,7 @@
```
rlp([chain_id, nonce, max_priority_fee_per_gas, max_fee_per_gas, gas_limit, destination, value, data, access_list, authorization_list, signature_y_parity, signature_r, signature_s])

authorization_list = [[chain_id, address, nonce, y_parity, r, s], ...]
authorization_list = [[chain_id, address, nonce, hash, y_parity, r, s], ...]
```

The fields `chain_id`, `nonce`, `max_priority_fee_per_gas`, `max_fee_per_gas`, `gas_limit`, `destination`, `value`, `data`, and `access_list` of the outer transaction follow the same semantics as [EIP-4844](./eip-4844.md). *Note, this means a null destination is not valid.*
Expand All @@ -64,7 +64,7 @@

#### Behavior

At the start of executing the transaction, after incrementing the sender's nonce, for each `[chain_id, address, nonce, y_parity, r, s]` tuple do the following:
At the start of executing the transaction, after incrementing the sender's nonce, for each `[chain_id, address, nonce, hash, y_parity, r, s]` tuple do the following:

1. Verify the chain id is either 0 or the chain's current ID.
2. Verify the `nonce` is less than `2**64 - 1`.
Expand All @@ -78,6 +78,8 @@
* As a special case, if `address` is `0x0000000000000000000000000000000000000000` do not write the designation. Clear the accounts code and reset the account's code hash to the empty hash `0xc5d2460186f7233c927e7db2dcc703c0e500b653ca82273b7bfad8045d85a470`.
9. Increase the nonce of `authority` by one.

The `hash` value of the auth tuple is not checked in any way. It is used by outer transaction.

If any of the above steps fail, immediately stop processing that tuple and continue to the next tuple in the list. It will in the case of multiple tuples for the same authority, set the code using the address in the last valid occurrence.

Note that the signer of an authorization tuple may be different than `tx.origin` of the transaction.
Expand Down Expand Up @@ -193,6 +195,7 @@
* Hence, it avoids the problem of "creating two separate code ecosystems" because, to a large extent, they would be the same ecosystem. There would be some workflows that require kludges under this solution that would be better done in some different "more native" under "endgame AA", but this is relatively a small subset.
* It does not require adding any opcodes, that would become dangling and useless in a post-EOA world.
* It allows EOAs to masquerade as contracts to be included in ERC-4337 bundles, in a way that's compatible with the existing `EntryPoint`.
* The auth tuple contains a `hash` value, which is unused by [EIP-7702] itself, but can be used to authenticate the wrapping UserOperation. This way, a single signature by the user is required, for both eip-7702 and the outer UserOperation.

Check failure on line 198 in EIPS/eip-7702.md

View workflow job for this annotation

GitHub Actions / EIP Walidator

references to proposals with a `category` of `Core` must use a prefix of `EIP` 

error[markdown-refs]: references to proposals with a `category` of `Core` must use a prefix of `EIP`
   --> EIPS/eip-7702.md
    |
198 | * The auth tuple contains a `hash` value, which is unused by [EIP-7702] itself, but can be used to authenticate the wrapping UserOp...
    |
    = help: see https://ethereum.github.io/eipw/markdown-refs/

Check failure on line 198 in EIPS/eip-7702.md

View workflow job for this annotation

GitHub Actions / EIP Walidator

references to proposals with a `category` of `Core` must use a prefix of `EIP` 

error[markdown-refs]: references to proposals with a `category` of `Core` must use a prefix of `EIP`
   --> EIPS/eip-7702.md
    |
198 | * The auth tuple contains a `hash` value, which is unused by [EIP-7702] itself, but can be used to authenticate the wrapping UserOp...
    |
    = help: see https://ethereum.github.io/eipw/markdown-refs/

### Clearing Delegation Designations

Expand Down
Loading