feat: Optimism execution changes

[clabby]

Overview

Implements Optimism's execution changes into revm behind the optimism feature flag. These changes enable native Optimism execution changes in op-reth, foundry, anvil, and other projects building on top of revm.

Goal

With the optimism feature flag enabled, a new configuration option is exposed that allows for enabling Optimism's execution changes at runtime. This is so that tools such as Foundry can swap between regular Ethereum execution and Optimism execution as needed (i.e. for multichain fork testing). revm's regular logic should be unaltered if either the optimism cfg option is false or the optimism feature flag is not enabled.

New Hardforks

• Bedrock (Ethereum Base: Merge)
• Regolith (Base: Bedrock)

TODO

• Tests
  • Unit tests
• Implement the spec types + extra TxEnv fields within revm-primitives.
• Ignore transaction field validation and nonce / balance checks on deposit transactions.
• Alter gas accounting for deposit transactions in both the Bedrock and Regolith hardforks.
• Mint ETH at the start of the state transition if the transaction is a deposit with a Some mint field.
• Pay out fees to the fee vaults rather than coinbase in non-deposit transactions when the optimism configuration flag is enabled.
• Implement the L1 fee calculation by reading the storage of the L1Block contract.

Future

• Benchmarks
  • How much overhead does the runtime branching on the optimism cfg option add when the optimism feature flag is enabled but the optimism cfg option is not? For example, in order for foundry to swap between optimism and ethereum execution modes, the regular release build will have to enable the optimism feature flag on revm. Does the runtime branching significantly slow down execution for the majority of tests which are not on OP?

[refcell]

Would really really appreciate another round of review here

[rakita]

lgtm! One nit comment.

[refcell]

Just FYI @rakita neither @clabby nor I have write access so I think it's up to you to hit merge 😄