reth

Module api

Source
Expand description

Re-exported from reth_node_api.

Modules§

  • Traits, validation methods, and helper types used to abstract over engine types.
  • Traits for configuring a node.
  • This crate defines abstractions to create and update payloads (blocks)
  • This crate defines abstractions to create and update payloads (blocks)

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 sent to 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.
  • 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.
  • A helper trait for internal usage to retrieve and resolve payloads.
  • The types that are used by the engine API.

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§