Add engine API to anvil

[roninjin10]

Component

Anvil

Describe the feature you would like

The Engine API is currently in RETH but not supported in anvil. Adding the engine API to anvil would be generally useful. For example, it would allow Anvil to work seamlessly within a multichain OP-chain devnet running on top of anvil. Without the engine api this must be hacked around.

Additional context

Some links about OP node and engine api:

• https://github.com/ethereum/execution-apis/blob/main/src/engine/README.md

[mattsse]

Adding the engine API to anvil would be generally useful. For example, it would allow Anvil to work seamlessly within a multichain OP-chain devnet running on top of anvil.

you want support for this in anvil so you have a node and still have all the cheat endpoints? otherwise op-reth would be an option

I think we can add this as an opt-in feature, I can see how this could be useful. But could you elaborate on how this would be used?

[Evalir]

Agree here with mattsse—this could be useful, we just need to scope it properly.

[roninjin10]

@mattsse exactly! We want to be able to do everything anvil does like cheat endpoints and state dumps within a multichain devnet. We also are looking to contribute helping add this.

Link to issue: https://github.com/ethereum-optimism/mocktimism/issues/5 Link to product document and eng doc: https://github.com/ethereum-optimism/mocktimism/issues/1

[mattsse]

okay, actually I think this shouldn't be too complex,

basically new_payload buffers received blocks FCU then executes the block(s) and updates the state

there are def some limitations when it comes to full validation etc, but getting the newpayload and fcu endpoints working (optimistically without full validation) should be doable.