Expand description
Provider trait implementations.
Re-exports§
pub use consistent::ConsistentProvider;
Structs§
- The main type for interacting with the blockchain.
- The main type for interacting with the blockchain.
- A state provider that resolves to data from either a wrapped
crate::ExecutionOutcome
or an underlying state provider. - A consistent view over state in the database.
- A provider struct that fetches data from the database. Wrapper around [
DbTx
] and [DbTxMut
]. Example:HeaderProvider
BlockHashReader
- A
DatabaseProvider
that holds a read-write database transaction. - State provider for a given block number. For more detailed description, see
HistoricalStateProviderRef
. - State provider for a given block number which takes a tx reference.
- State provider for the latest state.
- State provider over latest state that takes tx reference.
- A common provider that fetches data from a database or static file.
- Provider over a specific
NippyJar
and range. StaticFileProvider
manages all existingStaticFileJarProvider
.- Extends
StaticFileProvider
with writing capabilities - Mutable reference to a
StaticFileProviderRW
behind a [RwLockWriteGuard
].
Enums§
- Consistent database view error.
- Access mode on a static file provider. RO/RW.
Traits§
- Trait that provides access to implementations of
ChainStorage
- Helper trait to bound [
NodeTypes
] so that combined with database they satisfyProviderNodeTypes
. - A helper trait with requirements for
NodeTypesForProvider
to be used within legacy blockchain tree. - Helper trait keeping common requirements of providers for [
NodeTypesWithDB
]. - Helper trait to manage different
StaticFileProviderRW
of anArc<StaticFileProvider
- Helper trait with requirements for
ProviderNodeTypes
to be used within legacy blockchain tree.
Type Aliases§
- A
DatabaseProvider
that holds a read-only database transaction.