Skip to content

Commit

Permalink
Introduce XcmFeesToAccount fee manager (paritytech#1234)
Browse files Browse the repository at this point in the history
Combination of paritytech/polkadot#7005, its addon PR
paritytech/polkadot#7585 and its companion paritytech/cumulus#2433.

This PR introduces a new XcmFeesToAccount struct which implements the
`FeeManager` trait, and assigns this struct as the `FeeManager` in the
XCM config for all runtimes.

The struct simply deposits all fees handled by the XCM executor to a
specified account. In all runtimes, the specified account is configured
as the treasury account.

XCM __delivery__ fees are now being introduced (unless the root origin
is sending a message to a system parachain on behalf of the originating
chain).

# Note for reviewers

Most file changes are tests that had to be modified to account for the
new fees.
Main changes are in:
- cumulus/pallets/xcmp-queue/src/lib.rs <- To make it track the delivery
fees exponential factor
- polkadot/xcm/xcm-builder/src/fee_handling.rs <- Added. Has the
FeeManager implementation
- All runtime xcm_config files <- To add the FeeManager to the XCM
configuration

# Important note

After this change, instructions that create and send a new XCM (Query*,
Report*, ExportMessage, InitiateReserveWithdraw, InitiateTeleport,
DepositReserveAsset, TransferReserveAsset, LockAsset and RequestUnlock)
will require the corresponding origin account in the origin register to
pay for transport delivery fees, and the onward message will fail to be
sent if the origin account does not have the required amount. This
delivery fee is on top of what we already collect as tx fees in
pallet-xcm and XCM BuyExecution fees!

Wallet UIs that want to expose the new delivery fee can do so using the
formula:

```
delivery_fee_factor * (base_fee + encoded_msg_len * per_byte_fee)
```

where the delivery fee factor can be obtained from the corresponding
pallet based on which transport you are using (UMP, HRMP or bridges),
the base fee is a constant, the encoded message length from the message
itself and the per byte fee is the same as the configured per byte fee
for txs (i.e. `TransactionByteFee`).

---------

Co-authored-by: Branislav Kontur <bkontur@gmail.com>
Co-authored-by: joe petrowski <25483142+joepetrowski@users.noreply.github.com>
Co-authored-by: Giles Cope <gilescope@gmail.com>
Co-authored-by: command-bot <>
Co-authored-by: Francisco Aguirre <franciscoaguirreperez@gmail.com>
Co-authored-by: Liam Aharon <liam.aharon@hotmail.com>
Co-authored-by: Kian Paimani <5588131+kianenigma@users.noreply.github.com>
  • Loading branch information
7 people authored Oct 18, 2023
1 parent cabc74c commit 2cd005f
Showing 1 changed file with 6 additions and 4 deletions.
10 changes: 6 additions & 4 deletions substrate/frame/support/procedural/src/pallet/expand/warnings.rs
Original file line number Diff line number Diff line change
Expand Up @@ -33,8 +33,9 @@ pub(crate) fn weight_witness_warning(
if dev_mode {
return
}

let CallWeightDef::Immediate(w) = &method.weight else { return };
let CallWeightDef::Immediate(w) = &method.weight else {
return
};

let partial_warning = Warning::new_deprecated("UncheckedWeightWitness")
.old("not check weight witness data")
Expand Down Expand Up @@ -65,8 +66,9 @@ pub(crate) fn weight_constant_warning(
if dev_mode {
return
}

let syn::Expr::Lit(lit) = weight else { return };
let syn::Expr::Lit(lit) = weight else {
return
};

let warning = Warning::new_deprecated("ConstantWeight")
.index(warnings.len())
Expand Down

0 comments on commit 2cd005f

Please sign in to comment.