Expand description

The pallet module in each FRAME pallet hosts the most important items needed to construct this pallet.

The main components of this pallet are:

  • Pallet, which implements all of the dispatchable extrinsics of the pallet, among other public functions.
    • The subset of the functions that are dispatchable can be identified either in the dispatchables module or in the Call enum.
  • storage_types, which contains the list of all types that are representing a storage item. Otherwise, all storage items are listed among Type Definitions.
  • Config, which contains the configuration trait of this pallet.
  • Event and Error, which are listed among the Enums.

Re-exports§

  • pub use __tt_error_token_1 as tt_error_token;
  • pub use __tt_default_parts_7 as tt_default_parts;
  • pub use __tt_extra_parts_7 as tt_extra_parts;
  • pub use __tt_default_parts_v2_7 as tt_default_parts_v2;

Modules§

  • Auto-generated docs-only module listing all defined dispatchables for this pallet.
  • Auto-generated docs-only module listing all (public and private) defined storage types for this pallet.

Structs§

Enums§

  • Contains a variant per dispatchable extrinsic that this pallet has.
  • The Error enum of this pallet.
  • The Event enum of this pallet

Traits§

  • Configuration trait of this pallet.

Functions§

Type Aliases§

  • Storage field that keeps track of bandwidth used by the unincluded segment along with the latest HRMP watermark. Used for limiting the acceptance of new blocks with respect to relay chain constraints.
  • The number of HRMP messages we observed in on_initialize and thus used that number for announcing the weight of on_initialize and on_finalize.
  • A custom head data that should be returned as result of validate_block.
  • Were the validation data set to notify the relay chain?
  • The parachain host configuration that was obtained from the relay parent.
  • HRMP messages that were sent in a block.
  • HRMP watermark that was set in a block.
  • The last downward message queue chain head we have observed.
  • The message queue chain heads we have observed per each channel incoming channel.
  • The relay chain block number associated with the last parachain block.
  • ModuleDeprecated
    Type alias to Pallet, to be used by construct_runtime.
  • Validation code that is set by the parachain and is to be communicated to collator and consequently the relay-chain.
  • Upward messages that are still pending and not yet send to the relay chain.
  • In case of a scheduled upgrade, this storage field contains the validation code to be applied.
  • Number of downward messages processed in a block.
  • The state proof for the last relay parent block.
  • The snapshot of some state related to messaging relevant to the current parachain as per the relay parent.
  • The weight we reserve at the beginning of the block for processing DMP messages. This overrides the amount set in the Config trait.
  • The weight we reserve at the beginning of the block for processing XCMP messages. This overrides the amount set in the Config trait.
  • Latest included block descendants the runtime accepted. In other words, these are ancestors of the currently executing block which have not been included in the observed relay-chain state.
  • Optional upgrade go-ahead signal from the relay-chain.
  • An option which indicates if the relay-chain restricts signalling a validation code upgrade. In other words, if this is Some and NewValidationCode is Some then the produced candidate will be invalid.
  • The factor to multiply the base delivery fee by for UMP.
  • Upward messages that were sent in a block.
  • The [PersistedValidationData] set for this block. This value is expected to be set only once per block and it’s never stored in the trie.