EIP-7685: General Purpose Execution Layer Requests

[refcell]

Description

EIP-7685 introduces a way of sharing execution layer requests with the consensus layer.

Full inclusion of EIP-7685 on L2 requires batch format changes, gossip format changes, and more.

To support EIP-7685 on L2, the following are needed.

• Infer the block content based on fork, and add the missing attributes.
• Sanity-check in the CL that the EL didn't include any requests. (op-node)
• EL requests need to be persisted, or recomputed, somewhere if we do want to have them. Since the batch-submitter has to be aware of them, for other nodes to replicate them from the batch data.
  • The EL requests could be stored in the op-node until the batch-submitter consumes them.
• The engine API engine_newPayloadV4 is required to build prague blocks, but includes a executionRequests attribute. We'll need to pass an empty list as argument.

References

• Pectra Devnet 5 EIP List
• Proto's list of Pectra EIPs
• Pectra support on the OP Stack tracking issue: OP Stack: Support Pectra (Isthmus) optimism#12435

[tynes]

I don't think we will need any EL requests for anything and should assert that they are empty but still check that they are not None or nil