Crate polkadot_node_subsystem_types[−][src]
Expand description
Subsystem trait definitions and message types.
Node-side logic for Polkadot is mostly comprised of Subsystems, which are discrete components that communicate via message-passing. They are coordinated by an overseer, provided by a separate crate.
Re-exports
pub use polkadot_node_jaeger as jaeger;Modules
Error types for the subsystem requests.
Message types for the overseer and subsystems.
Structs
Activated leaf.
Changes in the set of active leaves: the parachain heads which we care to work on.
Configuration for the jaeger tracing.
Jaeger configuration builder.
A special “per leaf span”.
Enums
Stateful convenience wrapper around [mick_jaeger].
A description of an error during jaeger initialization.
The status of an activated leaf.
Signals sent by an overseer to a subsystem.
A wrapper type for a span.
A helper to annotate the stage with a numerical value to ease the life of the tooling team creating viable statistical metrics for which stage of the inclusion pipeline drops a significant amount of candidates, statistically speaking.
Type Definitions
The block number type used by Polkadot. 32-bits will allow for 136 years of blocks assuming 1 block per second.
A hash of some data used by the relay chain.