reth
reth copied to clipboard
Tracking issue: Prague Hardfork
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
- [x] [EIP-2537](https://eips.ethereum.org/EIPS/eip-2537): Precompile for BLS12-381 curve operations (https://github.com/bluealloy/revm/pull/1389)
- [ ] [EIP-6110](https://eips.ethereum.org/EIPS/eip-6110): Supply validator deposits on chain
- [ ] [EIP-7002](https://eips.ethereum.org/EIPS/eip-7002): Execution layer triggerable exits
- [x] [EIP-7251](https://eips.ethereum.org/EIPS/eip-7251): Increase the MAX_EFFECTIVE_BALANCE (requires no EL changes)
- [x] [EIP-7549](https://eips.ethereum.org/EIPS/eip-7549): Move committee index outside Attestation (requires no EL changes)
- [x] [EIP-3074](https://eips.ethereum.org/EIPS/eip-3074): AUTH/AUTHCALL
- [ ] [EIP-2935](https://eips.ethereum.org/EIPS/eip-2935): Save historical block hashes https://github.com/paradigmxyz/reth/pull/7818
- [ ] [EIP-7685](https://eips.ethereum.org/EIPS/eip-7685): General purpose execution layer requests
- [ ] Prague `Hardfork` addition to Chainspec
- [ ] https://github.com/paradigmxyz/reth/issues/7820
Revm tracking issue: https://github.com/bluealloy/revm/issues/1268
I vote we use devnet-0 branch https://github.com/paradigmxyz/reth/compare/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.
Going to close this as we're planning for devnet-1 now: https://github.com/paradigmxyz/reth/issues/8788