Expand description

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

§Warning: Doc-Only

Members of this module cannot be used directly and are only provided for documentation purposes.

To see the actual storage type, find a struct with the same name at the root of the pallet, in the list of Type Definitions.

Structs§

  • The actions to perform during the start of a specific session index.
  • Validation code stored by its hash.
  • The number of reference on the validation code in CodeByHash storage.
  • The validation code hash of every live para.
  • The actual future code hash of a para.
  • The block number at which the planned code change is expected for a parachain.
  • The list of upcoming future code upgrades.
  • The head-data of every registered para.
  • The context (relay-chain block number) of the most recent parachain head.
  • The current lifecycle of a all known Para IDs.
  • All lease holding parachains. Ordered ascending by ParaId. On demand parachains are not included.
  • Actual past code hash, indicated by the para id as well as the block number at which it became outdated.
  • Past code of parachains. The parachains themselves may not be registered anymore, but we also keep their code on-chain for the same amount of time as outdated code to keep it available for approval checkers.
  • Which paras have past code that needs pruning and the relay-chain block at which the code was replaced. Note that this is the actual height of the included block, not the expected height at which the code upgrade would be applied, although they may be equal. This is to ensure the entire acceptance period is covered, not an offset acceptance period starting from the time at which the parachain perceives a code upgrade as having occurred. Multiple entries for a single para are permitted. Ordered ascending by block number.
  • The list of all currently active PVF votes. Auxiliary to PvfActiveVoteMap.
  • All currently active PVF pre-checking votes.
  • Upcoming paras instantiation arguments.
  • The list of upcoming code upgrades.
  • The list of parachains that are awaiting for their upgrade restriction to cooldown.
  • This is used by the relay-chain to communicate to a parachain a go-ahead with in the upgrade procedure.
  • This is used by the relay-chain to communicate that there are restrictions for performing an upgrade for this parachain.