Expand description
Implementations of stages.
Structs§
- Account hashing stage hashes plain account. This is preparation before generating intermediate hashes and calculating Merkle tree root.
- The body stage downloads block bodies.
- The execution stage executes all transactions and update history indexes.
- The finish stage.
- The headers stage.
- Stage is indexing history the account changesets generated in
ExecutionStage
. For more information on index sharding take a look at [tables::AccountsHistory
] - Stage is indexing history the account changesets generated in
ExecutionStage
. For more information on index sharding take a look at [tables::StoragesHistory
]. - The prune sender recovery stage that runs the pruner with the provided
PruneMode
for theSenderRecovery
segment. - The prune stage that runs the pruner with the provided prune modes.
SeedOpts
provides configuration parameters for callingAccountHashingStage::seed
in unit tests or benchmarks to generate an initial database state for running the stage.- The sender recovery stage iterates over existing transactions, recovers the transaction signer and stores them in [
TransactionSenders
][reth_db::tables::TransactionSenders] table. - Storage hashing stage hashes plain storage. This is preparation before generating intermediate hashes and calculating Merkle tree root.
- The transaction lookup stage.
Enums§
- The merkle hashing stage uses input from
AccountHashingStage
andStorageHashingStage
to calculate intermediate hashes and state roots.
Constants§
- The error message that we include in invalid state root errors to tell users what information they should include in a bug report, since true state root errors can be impossible to debug with just basic logs.
- The default threshold (in number of blocks) for switching from incremental trie building of changes to whole rebuild.