Module moonbeam_runtime::xcm_config
source · Expand description
XCM configuration for Moonbase.
Structs§
- Location of Asset Hub
- Wrapper type around
LocationToAccountId
to convert anAccountId
to typeH160
. - Maximum number of instructions in a single XCM fragment. A sanity check against weight caculations getting too crazy.
- The size of the page; this implies the maximum message size which can be sent.
- The maximum number of stale pages (i.e. of overweight messages) allowed before culling can happen. Once there are more stale pages than this, then historical pages may be dropped, even if they contain unprocessed overweight messages.
- The amount of weight (if any) which should be provided to the message queue for servicing enqueued items.
- Xcm fees will go to the treasury account
Enums§
Type Aliases§
- The transactor for our own chain currency.
- Type for specifying how a
Location
can be converted into anAccountId
. This is used when determining ownership of accounts for asset transacting and when attempting to use XCMTransact
in order to determine the dispatch Origin. - This is the type we use to convert an (incoming) XCM origin into a local
Origin
instance, ready for dispatching a transaction with Xcm’sTransact
. There is anOriginKind
which can biases the kind of localOrigin
it will become. - The means for routing XCM messages which are not for local execution into the right message queues.
- Xcm Weigher shared between multiple Xcm-related configs.