Expand description

Message types for the overseer and subsystems.

These messages are intended to define the protocol by which different subsystems communicate with each other and signals that they receive from an overseer to coordinate their work. This is intended for use with the polkadot-overseer crate.

Subsystems’ APIs are defined separately from their implementation, leading to easier mocking.

Re-exports§

Modules§

  • Network events as transmitted to other subsystems, wrapped in their message types.

Structs§

Enums§

Type Aliases§

  • A collection of ancestor candidates of a parachain.
  • A response channel for the result of a chain API request.
  • Indicates the relay-parents whose fragment chain a candidate is present in or can be added in (right now or in the future).
  • A sender for the result of a runtime API request.