respond to comments

ethereum · Aug 28, 2024 · ab79897 · ab79897
1 parent 9179883
commit ab79897
Showing 1 changed file with 4 additions and 4 deletions.
diff --git a/EIPS/eip-7702.md b/EIPS/eip-7702.md
@@ -63,8 +63,8 @@ The [EIP-2718](./eip-2718.md) `ReceiptPayload` for this transaction is `rlp([sta
 
 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:
 
-1. Verify the chain id is either 0 or the chain's current ID.
-2. `authority = ecrecover(keccak(MAGIC || rlp([chain_id, address, nonce])), y_parity, r, s]`
+1. `authority = ecrecover(keccak(MAGIC || rlp([chain_id, address, nonce])), y_parity, r, s]`
+2. Verify the chain id is either 0 or the chain's current ID.
 3. Add `authority` to `accessed_addresses` (as defined in [EIP-2929](./eip-2929.md).)
 4. Verify the code of `authority` is either empty or already delegated.
 5. Verify the nonce of `authority` is equal to `nonce`.
@@ -120,11 +120,11 @@ The main families of instructions where a ban was considered were storage relate
 
 Creation instructions were considered for a ban on other similar EIPs, however because this EIP allows EOAs to spend value intra-transaction, the concern with bumping the nonce intra-transaction and invalidating pending transactions is not significant. A neat byproduct of this is that by combining EIP-7702 and CREATE2 it will be possible to commit to deploy specific bytecode to an address without committing to any fee market parameters. This solves the long standing issue of universal cross-chain contract deployment.
 
-### behaviour of SELFDESTRUCT opcode
+### Behaviour of SELFDESTRUCT opcode
 
 [EIP-6780](./eip-6780.md) restricted SELFDESTRUCT opcode behaviour, allowing account data deletion only if the account was created in the same transaction. A 7702 transaction essentially allows code to be assigned to an EOA. The subsequent execution of such code in the same transaction can cause the EOA to selfdestruct, causing account data deletion, leading to issues like transaction replay.
 
-To prevent problems arising from EOAs selfdestructing, this EIP updates the opcode behaviour, by not deleting account data for EOAs with delegated designation.
+To prevent problems arising from EOAs selfdestructing, this EIP updates the opcode behaviour, which will not delete account data for EOAs with delegated designation.
 
 ### Signature structure