pdobacz
September 2, 2024, 10:19am
1
Discussion topic for EIP-7761
Update Log
External Reviews
None as of 2024-09-02.
Outstanding Issues
None as of 2024-09-02.
2 Likes
The EIP should name the specific EIP that disables EXTCODESIZE rather than the meta EIP for EOF.
1 Like
shemnon
September 11, 2024, 6:54pm
3
That would be EIP-3540, and it is already listed.
The Changes to Execution Sematics section of EIP-3540 is where EXTCODE* is banned in EOF.
It seems much easier to just add back EXTCODESIZE. I haven’t yet found the rationale for removing the extcode
opcodes.
1 Like
pdobacz
September 25, 2024, 7:37am
5
I distilled some takeaways from a Eth R&D discord conversation here: Update EIP-7761: Fill Endgame AA's Rationale section by pdobacz · Pull Request #8904 · ethereum/EIPs · GitHub (Endgame AA concerns), hopefully this is accurate. If there are more arguments to be made, let’s continue the discussion here.
1 Like
frangio
September 25, 2024, 8:35pm
6
Overall the arguments are not very convincing to me either.
@vbuterin ’s initial proposal was to ban code introspection of EOF accounts only, the rationale was very clear, and there was at least an idea of how to migrate legacy accounts. Current EOF seems to have gone way beyond this initial proposal to ban code introspecion by EOF accounts of all accounts , with unclear rationale, and to my knowledge no idea of how to eventually migrate.
One of the arguments against any EVM changes is that it’s much harder to add features to the EVM than to remove them (eg. the complexities around even removing a little-used opcode like SELFDESTRUCT), and so if the EVM keeps changing, ever-increasing ugliness and complexity is likely to be the outcome.
One way to greatly reduce this tradeoff is to find a way to automatically convert version n EVM code to version n+1 EVM code every time there is an upgrade (not necessarily immediately; perhaps c…
1 Like