Notice: Polkadot has migrated to AssetHub. Balances, data, referenda, and other on-chain activity has moved to AssetHub.Learn more

View All Treasurer

Set KSM/DOT Asset Rate Locations on Kusama Asset Hub (Post-Migration Restoration)

inTreasurer
2 months ago
Executed

This proposal restores the KSM/DOT asset rate mappings on Kusama Asset Hub, which were not mapped during the migration and therefore need to be redefined. Since the asset IDs (XCM locations) were not re-anchored, they cannot be used correctly in their current form. These rates are required for track validation of future treasury calls that reference KSM/DOT conversions.

The batch call performs the following:

  1. Removes obsolete KSM rate entries from earlier configurations.
  2. Sets new asset rate mappings between Kusama and Polkadot Asset Hubs.
  3. Defines a KSM/DOT rate of 4x, consistent with the pre-migration configuration.

Each rate is represented as a Fixed-Point 128-bit unsigned integer, using a divisor of 10¹⁸.
Internally, the type is a wrapper around u128 and decodes accordingly.

The provided tests can be used to reason about and verify the rate values:

https://github.com/paritytech/polkadot-sdk/compare/muharem-rates-test#diff-6a80cbb1bb6f62b0c40f61614fd0a74f924f721431e7f2c818a2543a739041daR83

Comments (6)

2 months ago

Dear Proposer,

Thank you for your proposal. Our first vote on this proposal is AYE. Below is the evaluation of our voting policy v0.3 on this referendum:

TREASURER
---------
8 available members
🟢 4 • 🔴 0 • ⚪️ 0
✓ ≥50.0% required participation met
▶ Ayes ≥60.0% of all votes
🟢 AYE

Below is a summary of our members' comments:

The update restored the KSM/DOT asset rate mappings on the Kusama Asset Hub after a migration error had removed them. The proposal removed obsolete information, re-established the critical exchange rate of 4:1 consistent with previous configurations, and ensured treasury calls and conversion operations functioned correctly. It was described as essential and well-tested, with voters noting the clear need for its reimplementation. The approach aimed at accuracy by using high-precision fixed-point integers, which contributed confidence in its robustness. Overall, the proposal was unanimously supported, with comments expressing assurance in its importance and functionality. It ultimately demonstrated clear value for effective governance.

The full discussion can be found in our internal voting.

Please feel free to contact us through the links below for further discussion.

Kind regards,
Permanence DAO
Decentralized Voices Cohort V Delegate

📅 Book Office Hours
💬 Public Telegram
🌐️ Web
🐦 Twitter
🗳️ Delegate

41 days ago

It's a technical proposal to set proper parameters. AYE.

PleaseLogin to comment

Proposal Passed