Module staging_xcm::v3
source · Expand description
Version 3 of the Cross-Consensus Message format data structures.
Modules§
- A prelude for importing all types typically used when interacting with XCM messages.
Structs§
- A unit struct which can be converted into a
MultiLocation
of the innerparents
value. - A unit struct which can be converted into a
MultiLocation
of the innerparents
value and the inner interior. - Maximum size of the encoded error code coming from a
Dispatch
result, used forMaybeErrorCode
. This is not (yet) enforced, so it’s just an indication of expectation. - Either an amount of a single fungible asset, or a single well-identified non-fungible asset.
- A
Vec
ofMultiAsset
s. - A relative path between state-bearing consensus systems.
- A unit struct which can be converted into a
MultiLocation
ofparents
value 1. - A tuple struct which can be converted into a
MultiLocation
ofparents
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
- Classification of an asset being concrete or abstract.
- 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 Rustenum
in order to make pattern matching easier. - The holding register was loaded, now to buy execution
MultiAsset
collection, defined either by a number ofMultiAssets
or a single wildcard.- A global identifier of a data structure existing within consensus.
- Basically just the XCM (more general) version of
ParachainDispatchOrigin
. - 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.
- An optional weight limit.
- Classification of whether an asset is fungible or not.
- A wildcard representing a set of assets.
Constants§
- The maximal number of instructions in an XCM before decoding fails.
- Maximum number of items in a single
MultiAssets
value that can be decoded. - This module’s XCM version.
Traits§
- Type of XCM message executor.
- Utility for sending an XCM message to a given location.
- A trait for types that track state inside the XcmBuilder
Functions§
- Convenience function for using a
SendXcm
implementation. Just interprets thedest
and wraps both inSome
before passing them as as mutable references intoT::send_xcm
. - Convenience function for using a
SendXcm
implementation. Just interprets thedest
and wraps both inSome
before passing them as as mutable references intoT::send_xcm
.
Type Aliases§
- A relative location which is constrained to be an interior location of the context.
- Type alias for a better transition to V4.
- An identifier for a query.
- Result value when attempting to send an XCM message.
- A hash type for identifying messages.