Module polkadot_node_subsystem_types::messages
source · 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
pub use network_bridge_event::NetworkBridgeEvent;Modules
Network events as transmitted to other subsystems, wrapped in their message types.
Structs
Describes a relay-chain block by the para-chain candidates
it includes.
Response type to
ApprovalVotingMessage::ApprovedAncestor.Inherent data returned by the provisioner
Blanket error for validation failing for internal reasons.
Enums
The error result type of
ApprovalVotingMessage::CheckAndImportApproval request.The result type of
ApprovalVotingMessage::CheckAndImportApproval request.Message to the Approval Distribution subsystem.
Message to the Approval Voting subsystem.
The error result type of
ApprovalVotingMessage::CheckAndImportAssignment request.The result type of
ApprovalVotingMessage::CheckAndImportAssignment request.Availability Distribution Message.
Availability Recovery Message.
Availability store subsystem message.
Bitfield distribution message.
Bitfield signing message.
Messages received by the Candidate Backing subsystem.
Messages received by the Validation subsystem.
Chain API request subsystem message.
Chain selection subsystem messages
Message to the Collation Generation subsystem.
Messages received by the Collator Protocol subsystem.
Messages received by the dispute coordinator subsystem.
Messages going to the dispute distribution subsystem.
Message to the Gossip Support subsystem.
When sending a request, what to do on a disconnected recipient.
The result of
DisputeCoordinatorMessage::ImportStatements.Messages received from other subsystems.
Messages received from other subsystems by the network bridge subsystem.
The outcome of the candidate-validation’s PVF pre-check request.
This data becomes intrinsics or extrinsics which should be included in a future relay chain block.
Message to the Provisioner.
PVF checker message.
A message to the Runtime API subsystem.
A request to the Runtime API subsystem.
Statement distribution message.
Traits
Subsystem messages where each message is always bound to a relay parent.
Type Definitions
A response channel for the result of a chain API request.
A sender for the result of a runtime API request.