Crate reth_node_builder

Source
Expand description

Standalone crate for Reth configuration and builder types.

§features

  • js-tracer: Enable the JavaScript tracer for the debug_trace endpoints

Re-exports§

Modules§

  • Node add-ons. Depend on core NodeComponents.
  • Helper types that can be used by launchers.
  • Support for configuring the components of a node. Support for configuring the components of a node.
  • Temporarily re-export engine tree config. Engine tree configuration.
  • Support for installing the ExExs (execution extensions) in a node. Types for launching execution extensions (ExEx).
  • Node event hooks.
  • Support for configuring the higher level node types.
  • This crate defines abstractions to create and update payloads (blocks)
  • This crate defines abstractions to create and update payloads (blocks)
  • Builder support for rpc components.
  • Helpers for setting up parts of the node.

Structs§

Enums§

Traits§

  • Abstraction of block data type.
  • Abstraction for block’s body.
  • Represents a built payload type that contains a built [SealedBlock] and can be converted into engine API execution payloads.
  • Trait for configuring the EVM for executing full blocks.
  • This represents the set of methods used to configure the EVM’s environment before block execution.
  • This type defines the versioned types of the engine API.
  • Type that validates the payloads processed by the engine.
  • Helper trait that unifies all behaviour required by block to support full node operations.
  • Encapsulates all types and components of the node.
  • Helper trait that sets trait bounds on NodePrimitives.
  • A helper trait that is downstream of the NodeTypesWithEngine trait and adds stateful components to the node.
  • Helper trait to unify all provider traits for simplicity.
  • Helper trait that unifies all behaviour required by receipt to support full node operations.
  • Helper trait that unifies all behaviour required by block to support full node operations.
  • An invalid block hook.
  • A general purpose trait that launches a new node of any kind.
  • Customizable node add-on types.
  • Configures all the primitive types of the node.
  • The type that configures the essential types of an Ethereum-like node.
  • A helper trait that is downstream of the NodeTypesWithEngine trait and adds database to the node.
  • The type that configures an Ethereum-like node with an engine for consensus.
  • The execution payload attribute type the CL node emits via the engine API. This trait should be implemented by types that could be used to spawn a payload job.
  • A builder that can return the current payload attribute.
  • A type that can request, subscribe to and resolve payloads.
  • This can be implemented by types that describe a currently running payload job.
  • Re-export the core configuration traits. A trait that provides payload builder settings.
  • A helper trait for internal usage to retrieve and resolve payloads.
  • The types that are used by the engine API.
  • Type that validates an [ExecutionPayload].
  • Re-export the core configuration traits. A trait that represents the configured network and can be used to apply additional configuration to the network.
  • Re-export the core configuration traits. A trait that provides all basic config values for the transaction pool and is implemented by the TxPoolArgs type.

Functions§

  • Validate the presence of the parentBeaconBlockRoot field according to the given timestamp. This method is meant to be used with either a payloadAttributes field or a full payload, with the engine_forkchoiceUpdated and engine_newPayload methods respectively.
  • Validates the timestamp depending on the version called:
  • Validates the presence or exclusion of fork-specific fields based on the ethereum execution payload, or payload attributes, and the message version.
  • Validates the presence of the withdrawals field according to the payload timestamp. After Shanghai, withdrawals field must be Some. Before Shanghai, withdrawals field must be None;

Type Aliases§