Contract address made warm on aborted create call

[benSepanski]

Metadata

• Hardfork: london

What was wrong?

In the execution python specs, a contract_address is added to the accessed_addresses before the check validating that the sender nonce is small enough, the sender has enough balance, and the call-stack-depth has not overflowed.

This does not appear to match the behavior of CREATE as specified in Appendix H of the yellow paper. go-ethereum also appears to not include the new contract address if the aforementioned checks fail before loading the account at the address of the to-be-created account.

Sources

• https://ethereum.github.io/yellowpaper/paper.pdf Appendix H, p38
• https://github.com/ethereum/execution-specs/blob/0f116b58173d3871c98dabec0163b216b463288e/src/ethereum/london/vm/instructions/system.py#L71-L89
• https://github.com/ethereum/go-ethereum/blob/65e5ca7d8126f7a8c708f8affb64f16c22cc63c0/core/vm/evm.go#L431-L466

Authors

@sleepingshell, @benSepanski

[SamWilsn]

Thanks for the report! This certainly looks like a bug.