[Tracking] Pectra support / Isthmus

[emhane]

Tracks spec inclusion and implementation of Pectra support in Isthmus. Noop specs are required for not breaking as L1 hardforks. EIPs marked as noop or nodiff are low hanging fruit to write specs for [and to implement].

[refcell]

System Contracts Plan

The complete list of EIPs included in Pectra (as specified by the [EIP-7600](https://eips.ethereum.org/EIPS/eip-7600) hardfork meta) are with notes for predeploys.

• EIP-2537: Precompile for BLS12-381 curve operations
  • Only contains precompiles.
• EIP-2935: Save historical block hashes in state
  • Contains the Block Hashes system contract.
• EIP-6110: Supply validator deposits on chain
  • Contains the deposit contract address that is not expected to work on L2 and is safer to exclude as proto notes.
• EIP-7002: Execution layer triggerable exits
  • Contains a withdrawals request predeploy.
• EIP-7251: Increase the MAX_EFFECTIVE_BALANCE
  • Consolidation requests predeploy.
• EIP-7549: Move committee index outside Attestation
  • N/A - consensus layer changes
• EIP-7623: Increase calldata cost
  • N/A
• EIP-7685: General purpose execution layer requests
  • N/A
• EIP-7691: Blob throughput increase
  • N/A
• EIP-7702: Set EOA account code
  • N/A
• EIP-7840: Add blob schedule to EL config files
  • N/A

EIPs with Predeploys

• EIP-2935: Block Hash System Contract
• EIP-6110: Deposit Contract Address (safer to exclude as proto notes)
• EIP-7002: Withdrawals Request Predeploy
• EIP-7251: Consolidation Requests Predeploy

Concern

If we don't include them and all existing L1 tests assume them, we could have a strange bug someplace.

Therefore, we should heavily consider including them unless there is a good reason not to.

Considerations

Upgrade Path

Can we re-create the deterministically deployed tx with a deposit tx?
If so, this is preferred.

We could also just set code in the EL but that introduces another diff.

Genesis Path

We need to update L2Genesis.s.sol script to set the code at the correct addresses.

From proto:

With the beacon-root history accumulator contract in the previous L1 upgrade, very similar to the new block-hash accumulator contract, we used a trick with deposits to deploy the contract automatically as part of the upgrade, in case it's not already permissionlessly deployed. I would strongly recommend we do the same type of thing this upgrade.

Current State

EIP-2935

Already specified and included as a pre-block contract call in kona.

EIP-6110

Re-uses the deposit contract address.

EIP-7002

Already implemented in kona as a pre-block contract call.

EIP-7251

Already implemented in kona as a pre-block contract call

[emhane]

@refcell 6110 is already nooped in op-reth, see #21

[emhane]

@refcell doesn't 2537 require pre-deploy?

[refcell]

2537 contains precompiles

[emhane]

alright, no op for platform then who have to deploy the contracts, removing platform label from 2537