Update EIP-3540: note on mid-creation EXTCODE* behavior

Align with ipsilon/eof#128
ethereum · Jun 13, 2024 · 7a2e811 · 7a2e811
1 parent 83e11f0
commit 7a2e811
Showing 1 changed file with 2 additions and 0 deletions.
diff --git a/EIPS/eip-3540.md b/EIPS/eip-3540.md
@@ -180,6 +180,8 @@ For a legacy contract:
 - If the target account of `EXTCODEHASH` is an EOF contract, then it will return `0x9dbf3648db8210552e9c4f75c6a1c3057c0ca432043bd648be15fe7be05646f5` (the hash of `EF00`, as if that would be the code).
 - If the target account of `EXTCODESIZE` is an EOF contract, then it will return 2.
 
+**NOTE** Like for legacy targets, the aforementioned behavior of `EXTCODECOPY`, `EXTCODEHASH` and `EXTCODESIZE` does not apply to EOF contract targets mid-creation, i.e. those report same as accounts without code.
+
 ## Rationale
 
 EVM and/or account versioning has been discussed numerous times over the past years. This proposal aims to learn from them.