`devnet-5` readiness

[tersec]

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

• engine: exclude empty requests in requests list / Update EIP-7685: exclude empty requests data in commitment
• Update EIP-7702: Remove delegation behavior of EXTCODE*
• Update EIP-7691: add update fraction specification
• Update EIP-7251: fix CONSOLIDATION_REQUEST_PREDEPLOY_ADDRES
• Update EIP-7002: fix WITHDRAWAL_REQUEST_PREDEPLOY_ADDRESS
• Update EIP-7251: Set MAX_CONSOLIDATIONS=2
• Update EIP-2537: Gas pricing MAP, MUL and ADD operations
• Update EIP-2537: MSM gas repricing
• Update EIP-2537: Gas pricing pairing operations
• Update EIP-2537: Remove redundant MUL precompiles #8945
• Update EIP-2935: bring up to date with sys contract impl
• Add EIP: Add blob schedule to EL config files #9129

Deprioritized:

• Update EIP-7702: Update chainid to uint256

[jangko]

The idea behind Update EIP-7702: Update chainid to uint256 is this
https://ethereum-magicians.org/t/eip-7702-set-eoa-account-code/19923/326?u=matt.

This have greater implication to our codebase, because we still use 64 bit ChainId and NetworkId.

Of course we can limit the changes to AuthorizationList only, but when they start to test it against network chainid using value greater than 64 bit, that can be problematic.

[tersec]

The idea behind Update EIP-7702: Update chainid to uint256 is this https://ethereum-magicians.org/t/eip-7702-set-eoa-account-code/19923/326?u=matt.

This have greater implication to our codebase, because we still use 64 bit ChainId and NetworkId.

Of course we can limit the changes to AuthorizationList only, but when they start to test it against network chainid using value greater than 64 bit, that can be problematic.

Ok, it can be split out from this and prioritized to after this happens, and hopefully devnet-5 won't have a chain ID which triggers this, in which case it won't matter yet, or for the other supported networks (mainnet, Holesky, or Sepolia).