Explicitly allow EXTCODE* opcodes to access 'sender' from the 'factory'

forshtat · Aug 16, 2023 · 1bcd209 · 1bcd209
1 parent f3dd7a5
commit 1bcd209
Showing 1 changed file with 1 addition and 0 deletions.
diff --git a/EIPS/eip-4337.md b/EIPS/eip-4337.md
@@ -382,6 +382,7 @@ While simulating `userOp` validation, the client should make sure that:
    4. cannot call EntryPoint's methods, except `depositFor` (to avoid recursion)
 5. `EXTCODEHASH` of every address accessed (by any opcode) does not change between first and second simulations of the op.
 6. `EXTCODEHASH`, `EXTCODELENGTH`, `EXTCODECOPY` may not access address with no code.
+The exception is accessing the `sender` address from the `factory` contract as it is guaranteed to deploy the `sender`.
 7. If `op.initcode.length != 0` , allow only one `CREATE2` opcode call (in the first (deployment) block), otherwise forbid `CREATE2`.
 
 Transient Storage slots defined in [EIP-1153](./eip-1153.md) and accessed using `TLOAD` (`0x5c`) and `TSTORE` (`0x5d`) opcodes