## TL:DR

This batched proposal updates the `UnitsPerSecond` (XCM token transfer fee data) for all registered XC-20s.

## Summary

We propose to update the relevant XCM fee information (called `UnitsPerSecond`) for all registered XC-20s. For each XC-20, the `UnitsPerSecond` is set the moment it is registered. The value is configured so that, for a given token price, the XCM fee is approximately 0.02$ for a XCM token transfer.  Consequently, this value needs to be changed every so often as the token price fluctuates. 

You can read how XCM can be calculated in the [Moonbeam Documentation Site](https://docs.moonbeam.network/builders/xcm/fees/#fee-calc-external-assets ).

## Proposal

Proposal #27 with the following hash: *0x5a5a0a56600656af1da9655066629ddd9d7257cd3ed9ccbce6f9f5dac3755659*

## Technical details:

The batch call was calculated using the https://github.com/albertov19/xcmTools/blob/main/calculateBatchUnitsPerSeconds.ts , which uses the Coingecko API to fetch for the token price. The script calculates the `UnitsPerSecond` for each registered XC-20. The calculation was done with token price data from Aug 24th.

If you are interested, the hex-encoded call data for this proposal in [Moonriver](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fwss.api.moonriver.moonbeam.network#/extrinsics/decode ) is:

**0x1e02406901000100fdce301577000000000000000000000019000000690100010200411f06080080f92faf2f142d0000000000000000000019000000690100010200411f0608008100901ec4bc160000000000000000000019000000690100010100511f92d1191d14d40000000000000000000019000000690100010200b1200608000c4e00fb71ee0a0000000000000000000019000000690100010200b1200608000b93c9010000000000000000000000000019000000690100010200451f0608000104b5bed076770000000000000000000019000000690100010100711fe7233270a71e0a00000000000000000019000000690100010300a10f043205011f40787d0100000000000000000000000019000000690100010300a10f043205208097b013120000000000000000000000190000006901000102009520060c484b4ffecc9828f5aa00000000000000000000190000006901000102007d1f06105445455219ec556e13210000000000000000000019000000690100010200e5200405ea84f51fef7d29b08e05000000000000190000006901000101009120978b3c56269b30000000000000000000190000006901000101005d1fc2c26aebeb157d6a040000000000000019000000690100010200e920040a023ace9a771d0000000000000000000019000000**

Send a batch of dispatch calls and atomically execute them.
The whole transaction will rollback and fail if any of the calls failed.

May be called from any origin.

- `calls`: The calls to be dispatched from the same origin. The number of call must not
  exceed the constant: `batched_calls_limit` (available in constant metadata).

If origin is root then call are dispatch without checking origin filter. (This includes
bypassing `frame_system::Config::BaseCallFilter`).

# <weight>
- Complexity: O(C) where C is the number of calls to be batched.
# </weight>

- This proposal is about updating the fee information for a type of token called XC-20.
- The fee information needs to be changed because the price of the token can go up or down.
- The proposal has a specific number called a hash: 0x5a5a0a56600656af1da9655066629ddd9d7257cd3ed9ccbce6f9f5dac3755659.
- The fee information was calculated using a special program and data from August 24th.
- If you want to learn more, you can visit the Moonbeam Documentation Site or the Moonriver website.

#106 Update XCM Fee Information for All Registered XC-20s

No Active Proposals