Crate reth_optimism_node

Available on crate feature optimism only.

Standalone crate for Optimism-specific Reth configuration and builder types.

Re-exports

• pub use engine::OpEngineTypes;
• pub use node::OptimismNode;

Modules

• args
  CLI argument parsing for the optimism node. Additional Node command arguments. clap Args for optimism rollup configuration
• engine
  Exports optimism-specific implementations of the EngineTypes trait.
• l1
  Optimism-specific implementation and utilities for the executor
• node
  Optimism Node types config.
• txpool
  OP transaction pool types

Structs

• OpBuiltPayload
  Contains the built payload.
• OpEvmConfig
  Optimism-related EVM configuration.
• OpExecutionStrategy
  Block execution strategy for Optimism.
• OpExecutionStrategyFactory
  Factory for OpExecutionStrategy.
• OpExecutorProvider
  Helper type with backwards compatible methods to obtain executor providers.
• OpPayloadBuilder
  Optimism’s payload builder
• OpPayloadBuilderAttributes
  Optimism Payload Builder Attributes

Enums

• OptimismBlockExecutionError
  Optimism Block Executor Errors

Traits

• RethL1BlockInfo
  An extension trait for [L1BlockInfo] that allows us to calculate the L1 cost of a transaction based off of the [ChainSpec]’s activated hardfork.

Functions

• ensure_create2_deployer
  The Canyon hardfork issues an irregular state transition that force-deploys the create2 deployer contract. This is done by directly setting the code of the create2 deployer account prior to executing any transactions on the timestamp activation of the fork.
• extract_l1_info
  Extracts the [L1BlockInfo] from the L2 block. The L1 info transaction is always the first transaction in the L2 block.
• parse_l1_info
  Parses the input of the first transaction in the L2 block, into [L1BlockInfo].
• parse_l1_info_tx_bedrock
  Parses the calldata of the [L1BlockInfo] transaction pre-Ecotone hardfork.
• parse_l1_info_tx_ecotone
  Updates the L1 block values for an Ecotone upgraded chain. Params are packed and passed in as raw msg.data instead of ABI to reduce calldata size. Params are expected to be in the following order:
• revm_spec
  Map the latest active hardfork at the given block to a revm SpecId.
• revm_spec_by_timestamp_after_bedrock
  Returns the revm SpecId at the given timestamp.