Module staging_xcm::v4

source ·
Expand description

Version 4 of the Cross-Consensus Message format data structures.

Re-exports§

Modules§

  • A prelude for importing all types typically used when interacting with XCM messages.

Structs§

  • A unit struct which can be converted into a Location of the inner parents value.
  • A unit struct which can be converted into a Location of the inner parents value and the inner interior.
  • Either an amount of a single fungible asset, or a single well-identified non-fungible asset.
  • Location to identify an asset.
  • A Vec of Assets.
  • A relative path between state-bearing consensus systems.
  • Maximum size of the encoded error code coming from a Dispatch result, used for MaybeErrorCode. This is not (yet) enforced, so it’s just an indication of expectation.
  • A unit struct which can be converted into a Location of parents value 1.
  • A tuple struct which can be converted into a Location of parents value 1 with the inner interior.
  • Information regarding the composition of a query response.
  • Type used to build XCM programs
  • Contextual data pertaining to a specific list of XCM instructions.

Enums§

  • Access to all the instructions
  • Asset collection, defined either by a number of Assets or a single wildcard.
  • A general identifier for an instance of a non-fungible asset class.
  • An identifier of a pluralistic body.
  • A part of a pluralistic body.
  • Error codes used in XCM. The first errors codes have explicit indices and are part of the XCM format. Those trailing are merely part of the XCM implementation; there is no expectation that they will retain the same index over time.
  • Need to explicitly state it won’t pay for fees
  • Classification of whether an asset is fungible or not, along with a mandatory amount or instance.
  • Cross-Consensus Message: A message from one consensus system to another.
  • A single item in a path to describe the relative location of a consensus system.
  • Non-parent junctions that can be constructed, up to the length of 8. This specific Junctions implementation uses a Rust enum in order to make pattern matching easier.
  • The holding register was loaded, now to buy execution
  • A global identifier of a data structure existing within consensus.
  • Outcome of an XCM execution.
  • You need to pay for execution
  • Response data to a query.
  • Error result value when attempting to send an XCM message.
  • A wildcard representing a set of assets.
  • Classification of whether an asset is fungible or not.

Constants§

Traits§

Functions§

  • Convenience function for using a SendXcm implementation. Just interprets the dest and wraps both in Some before passing them as as mutable references into T::send_xcm.
  • Convenience function for using a SendXcm implementation. Just interprets the dest and wraps both in Some before passing them as as mutable references into T::send_xcm.

Type Aliases§

  • A relative location which is constrained to be an interior location of the context.
  • An identifier for a query.
  • Result value when attempting to send an XCM message.
  • A hash type for identifying messages.