Module polkadot_runtime::xcm_config
source · Expand description
XCM configuration for Polkadot.
Structs
- The base fee for the message delivery fees.
- The amount of weight an XCM operation takes. This is a safe overestimate.
- The Checking Account, which holds any native assets that have been teleported out and not back in (yet).
- The asset ID for the asset that we use to pay for message delivery fees.
- The Checking Account along with the indication that the local chain is able to mint tokens.
- Maximum number of instructions in a single XCM fragment. A sanity check against weight calculations getting too crazy.
- A call filter for the XCM Transact instruction. This is a temporary measure until we properly account for proof size weights.
- The Polkadot network ID. This is named.
- The location of the DOT token, from the context of this chain. Since this token is native to this chain, we make it synonymous with it and thus it is the
Here
location, which means “equivalent to the context”. - Our location in the universe of consensus systems.
Type Definitions
- The barriers one of which must be passed for an XCM message to be executed.
- Type to convert the
FellowshipAdmin
origin to a PluralityMultiLocation
value. - Type to convert the
GeneralAdmin
origin to a PluralityMultiLocation
value. - Our asset transactor. This is what allows us to interact with the runtime assets from the point of view of XCM-only concepts like
MultiLocation
andMultiAsset
. - Type to convert an
Origin
type value into aMultiLocation
value which represents an interior location of this chain. - Type to convert a pallet
Origin
type value into aMultiLocation
value which represents an interior location of this chain for a destination chain. - The canonical means of converting a
MultiLocation
into anAccountId
, used when we want to determine the sovereign account controlled by a location. - Type to convert the
StakingAdmin
origin to a PluralityMultiLocation
value. - Polkadot Relay recognizes/respects the Statemint chain as a teleporter.
- The XCM router. When we want to send an XCM message, we use this type. It amalgamates all of our individual routers.