Transaction recipient should be warm

[pldespaigne]

TL;DR

Before	After

Problem

The Berlin hardfork introduced EIP-2929 which is now part of the Yellow Paper specification. This EIP states that the transaction recipient address should be part of the initial accessed account set:

The Yellow Paper does enforce this behavior only for contract creation and subsequent xCALL opcodes but not for the initial message call.

Proposed Solution

When the transaction is a message call ($T_t \neq \varnothing$) add the recipient address ($T_t$) to the accessed account set, along with the already present precompiled, sender address, and access list.

---

I would be happy to discuss this further or to make some change to this PR if needed .
Anyway thanks for your time!

[pldespaigne]

Hey @yperbasis 👋
Thanks for the review!

I would be interested in updating the YP to the Shangai fork and next, to the Cancun fork, is anyone already working on this?
Do you think I could ask for a small EF grant?

[yperbasis]

Hey @yperbasis 👋 Thanks for the review!

I would be interested in updating the YP to the Shangai fork and next, to the Cancun fork, is anyone already working on this? Do you think I could ask for a small EF grant?

Thank you for the patch @pldespaigne! I'm not aware of anyone working on the Shanghai/Cancun upgrades – feel free to pick it. Yes, you can probably apply for a EF grant on https://esp.ethereum.foundation/applicants. cc @timbeiko

[pldespaigne]

Thanks!
I already applied, I'm waiting for them to answer now 🙂