Expand description
Primitive types which are strictly necessary from a parachain-execution point of view.
Structs§
- Parachain block data.
- Parachain head data included in the chain.
- A type that uniquely identifies an HRMP channel. An HRMP channel is established between two paras. In text, we use the notation
(A, B)to specify a channel between A and B. The channels are unidirectional, meaning that(A, B)and(B, A)refer to different channels. The convention is that we use the first item tuple for the sender and the second for the recipient. Only one channel is allowed between two participants in one direction, i.e. there cannot be 2 different channels identified by(A, B). A channel with the same para id in sender and recipient is invalid. That is, however, not enforced. - Unique identifier of a parachain.
- Parachain validation code.
- Unit type wrapper around [
type@Hash] that represents the blake2-256 hash of validation code in particular. - Validation parameters for evaluating the parachain validity function.
- The result of parachain validation.
Enums§
- The aggregate XCMP message format.
Constants§
- The ID of the first publicly registrable parachain.
- Maximum number of HRMP messages allowed per candidate.
- Maximum number of UMP messages allowed per candidate.
Traits§
- Something that should be called when a downward message is received.
- Determine if a parachain is a system parachain or not.
- Something that should be called for each batch of messages received over XCMP.
Type Aliases§
- Block number type used by the relay chain. The block number type used by Polkadot. 32-bits will allow for 136 years of blocks assuming 1 block per second.
- A message from a parachain to its Relay Chain.