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.
- A request to the candidate backing subsystem to check whether we can second this candidate.
- A checked indirect assignment, the crypto for the cert has been validated and the
candidate_bitfield
is correctly claimed atdelay_tranche
. - A checked indirect signed approval vote.
- Response type to
ApprovalVotingMessage::ApprovedAncestor
. - Request specifying which candidates are either already included or might become included in fragment chain under a given active leaf (or any active leaf if
fragment_chain_relay_parent
isNone
). - Request introduction of a seconded candidate into the prospective parachains subsystem.
- A request for the persisted validation data stored in the prospective parachains subsystem.
- Inherent data returned by the provisioner
- Blanket error for validation failing for internal reasons.
Enums§
- The error result type of
ApprovalVotingMessage::ImportApproval
request. - The result type of
ApprovalVotingMessage::ImportApproval
request. - Message to the Approval Distribution subsystem.
- Message to the Approval Voting subsystem.
- Message to the approval voting parallel subsystem running both approval-distribution and approval-voting logic in parallel. This is a combination of all the messages ApprovalVoting and ApprovalDistribution subsystems can receive.
- The error result type of
ApprovalVotingMessage::ImportAssignment
request. - The result type of
ApprovalVotingMessage::ImportAssignment
request. - Availability Distribution Message.
- Availability Recovery Message.
- Availability store subsystem message.
- Bitfield distribution 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.
- A hypothetical candidate to be evaluated for potential/actual membership in the prospective parachains 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 parent head-data hash with optional data itself.
- The outcome of the candidate-validation’s PVF pre-check request.
- Messages sent to the Prospective Parachains subsystem.
- This data becomes intrinsics or extrinsics which should be included in a future relay chain block.
- Message to the Provisioner.
- Extends primitives::PvfExecKind, which is a runtime parameter we don’t want to change, to separate and prioritize execution jobs by request type.
- Type of peer reporting
- A message to the Runtime API subsystem.
- A request to the Runtime API subsystem.
- Statement distribution message.
- The error result type of a
AvailabilityStoreMessage::StoreAvailableData
request.
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.