Tracking issue: Prague Hardfork

[Rjected]

This is a tracking issue for the changes we need to make for the prague hardfork.

The current meta EIP: https://eips.ethereum.org/EIPS/eip-7600
The discussion thread: https://ethereum-magicians.org/t/pectra-network-upgrade-meta-thread/16809

Devnet-0: https://notes.ethereum.org/@ethpandaops/pectra-devnet-0

Tasks

Beta Give feedback

1. EIP-2537: Precompile for BLS12-381 curve operations (feat(precompile): BLS12-381 bluealloy/revm#1389)
2. EIP-6110: Supply validator deposits on chain
3. EIP-7002: Execution layer triggerable exits
4. EIP-7251: Increase the MAX_EFFECTIVE_BALANCE (requires no EL changes)
5. EIP-7549: Move committee index outside Attestation (requires no EL changes)
6. EIP-3074: AUTH/AUTHCALL
7. EIP-2935: Save historical block hashes feat: implement EIP-2935 #7818
8. EIP-7685: General purpose execution layer requests
9. Prague Hardfork addition to Chainspec
10. Add Header fields while maintaining backwards compatibility #7820
    A-db E-prague M-prevent-stale S-needs-investigation +4

[rakita]

Revm tracking issue: bluealloy/revm#1268

[gakonst]

I vote we use devnet-0 branch main...devnet-0 given EIP-3074 integration and I don't want to pull in that EIP into Revm (cc @rakita) given it's likely we'll go with EIP-7702.