## TL: DR
Due to a change introduced in Kusama with v0.9.34 Update, the `UnitsPerSecond` value for xcKSM for the XCM-Transactor Pallet needs to be multiplied by 10.

## Summary
The introduction of V0.9.34 in Kusama [changed the concept of `CENTS`](https://github.com/paritytech/polkadot/pull/6372/files#diff-29b00d2d3967a817d5c82c4dae0a7e8cb10da213b80495f91ed28d3c8ffbf22a). This means that the value set in storage for `UnitsPerSecond` for xcKSM in the XCM-Transactor pallet is insufficient to pay for execution in Kusama.

This value needs to be multiplied by 10x, as `CENTS` is now defined as `10^12/3000` instead of `10^12/30000`. More info can be found on the [Moonbeam Docs site](https://docs.moonbeam.network/builders/xcm/fees/#kusama).

## Proposal

Proposal #XYZ with the following hash: *XYZ*

## Technical details:

The call used is `xcmTransactor.setFeePerSecond(assetLocation, feePerSecond)`, where `assetLocation` is KSM multilocation (`{parents: 1, interior: here}`), and the new `unitsPerSecond` value is `414851773500`.

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:

```
0x6b070101003cb41797600000000000000000000000
```

Big tipper to Paradox for his invaluable contributions and unwavering dedication in both drafting and refining arduous calls aimed at Referendums 73, 112, 113, 114, and 115 rejecting certain Gov1 treasury proposals while facilitating the release of the proponent deposits.

Set the fee per second of an asset on its reserve chain

- There was a change in Kusama called v0.9.34 Update.
- The value for xcKSM in the XCM-Transactor Pallet needs to be multiplied by 10.
- The proposal number is XYZ.
- The technical details include a call to set the new value.
- There is a hex-encoded call data for the proposal.

#123 Update `UnitsPerSecond` for xcKSM in XCM-Transactor Pallet

No Active Proposals