From 7a2e811426d13805a05279a0ecd2c58c70ae45c6 Mon Sep 17 00:00:00 2001
From: pdobacz <5735525+pdobacz@users.noreply.github.com>
Date: Thu, 13 Jun 2024 16:07:50 +0200
Subject: [PATCH] Update EIP-3540: note on mid-creation EXTCODE* behavior

Align with https://github.com/ipsilon/eof/pull/128
---
 EIPS/eip-3540.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/EIPS/eip-3540.md b/EIPS/eip-3540.md
index 137ecc2ae5d9c..01d23a34ca038 100644
--- 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.