Crate polkadot_node_subsystem_types

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

• errors
  Error types for the subsystem requests.
• messages
  Message types for the overseer and subsystems.

Structs

• ActivatedLeaf
  Activated leaf.
• ActiveLeavesUpdate
  Changes in the set of active leaves: the parachain heads which we care to work on.
• JaegerConfig
  Configuration for the jaeger tracing.
• JaegerConfigBuilder
  Jaeger configuration builder.
• PerLeafSpan
  A special “per leaf span”.

Enums

• Jaeger
  Stateful convenience wrapper around mick_jaeger.
• JaegerError
  A description of an error during jaeger initialization.
• LeafStatus
  The status of an activated leaf.
• OverseerSignal
  Signals sent by an overseer to a subsystem.
• Span
  A wrapper type for a span.
• Stage
  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.

Traits

• RuntimeApiSubsystemClient
  Exposes all runtime calls that are used by the runtime API subsystem.

Functions

• hash_to_trace_identifier
  A helper to convert the hash to the fixed size representation needed for jaeger.

Type Definitions

• BlockNumber
  The block number type used by Polkadot. 32-bits will allow for 136 years of blocks assuming 1 block per second.
• Hash
  A hash of some data used by the relay chain.