Update EIP-3540: Clarify EXTDELEGATECALL to "legacy"

Merged by EIP-Bot.
ethereum · Jun 5, 2024 · 73f68e7 · 73f68e7
1 parent 84f7756
commit 73f68e7
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/EIPS/eip-3540.md b/EIPS/eip-3540.md
@@ -172,7 +172,7 @@ For an EOF contract:
 - Execution starts at the first byte of code section 0
 - `CODESIZE`, `CODECOPY`, `EXTCODESIZE`, `EXTCODECOPY`, `EXTCODEHASH`, `GAS` are rejected by validation in EOF contracts, with no replacements
 - `CALL`, `DELEGATECALL`, `STATICCALL` are rejected by validation in EOF contracts, replacement instructions to be introduced in a separate EIP.
-- `EXTDELEGATECALL` (`DELEGATECALL` replacement) from an EOF contract to a legacy contract is disallowed, and it should fail in the same mode as if the call depth check failed. We allow legacy to EOF path for existing proxy contracts to be able to use EOF upgrades.
+- `EXTDELEGATECALL` (`DELEGATECALL` replacement) from an EOF contract to a non-EOF contract (legacy contract, EOA, empty account) is disallowed, and it should fail in the same mode as if the call depth check failed. We allow legacy to EOF path for existing proxy contracts to be able to use EOF upgrades.
 
 For a legacy contract: