meta: Foundry Cancun readiness

[Evalir]

Motivation

Foundry Cancun tracking issue for readiness.

Items needed

• revm foundry upgrade feat(evm): Use latest revm main commit #5669
• revm EIP-4844 support: Waylon/eip4844 bluealloy/revm#536
• revm alloy migration: Ethereum hardfork: Cancun bluealloy/revm#527
• alloy EIP-4844 support.

Anvil

• EIP-4844 type support on Anvil & corresponding revm config: feat(anvil): add support for EIP4844 types #7202
• Ensure send/send_raw_transaction methods can properly decode 4844 txs. feat(consensus): add extra EIP-4844 types needed alloy-rs/alloy#229
• Change TransactionExecutor to validate 4844 txs iff cancun spec is active feat: Anvil Cancun support #7242
• Adjust new / changed RPC methods accordingly: feat: Anvil Cancun support #7242

Forge

• vm.blobhashes: feat: vm.blobhashes #7001

Cast

• cast send 4844 support feat(cast): send 4844 support #7823

[rakita]

Here is meta issue for revm: bluealloy/revm#527

[Evalir]

Thank you @rakita! Was wondering, do you have any ETAs for when will revm be ready for cancun? Anything I can do to help drive it to completion?

[Rjected]

bump on this, everything should be fine on the revm side, but rpc types might need to be adjusted? In particular anvil would need blob support for eth_sendTransaction and raw tx + blob decoding, which are currently implemented in reth. Not sure what the best way is to share, for example, the RLP decoding if anvil were to accept blob transactions with a sidecar on a forked network

also wondering how relevant #5782 is

[Thegaram]

Hi @Evalir, do you have an estimate as to when forge and anvil will support blob transactions? Currently there's no good tool to unit test features that rely on blobs.

[Evalir]

Almost @Thegaram — the last missing piece is #7823

[zerosnacks]

Closing as #7823 has been merged