Polkassembly Logo

Create Pencil IconCreate
Chat with KlaraComing Soon
OpenGov
View All Root

Please vote NAY - [Root] Kusama Inflation Parameters for Asset Hub Migration

inRoot
26 days ago
Rejected

Kusama Inflation Parameters for Asset Hub Migration
Root (signal now, enact-ready for post-migration)

Summary:

This referendum pre-commits the post-Asset Hub staking inflation settings: keep 10% annual inflation and 75% ideal stake, and turn off the parachain-slot adjustments by setting “UseAuctionsSlots = false”. It contains a short on-chain remark stating that this is a pre-migration signal whose parameters will apply after the migration (and the canary community can revisit them afterward).

Why a vote if numbers don’t change?
Because the execution path changes after the Asset Hub migration. The auctions-dependent branch becomes irrelevant; without an explicit update, the chain could fall back to behavior not explicitly approved for post-AH. This proposal:

  • Disables the auctions path by setting (UseAuctionSlots = false)
  • Locks in the same headline numbers (10%, 75%) under the right path for AH.
  • Voting now blesses the exact post-AH settings (10%, 75%), reduces ambiguity for operators/stakers, and records intent on-chain (remark).
  • Signals now (via an on-chain remark) to reduce ambiguity for operators and stakers, and commits to re-evaluate the model after migration.

Why 10% and 75% now?
We’re prioritizing stability through the migration: keeping incentives familiar for validators/nominators and maintaining predictable Treasury dynamics. Changing rates today adds unnecessary risk; we’ll reassess after AH with live data (including options like alternative reward curves or gradual issuance schedules, or decreased inflation …. etc)

What exactly changes on chain?
A batched Root call that:
1- system.remark(...) – documents scope: post-AH signal, no immediate change, revisit after migration.
2- sets Inflation::UseAuctionSlots = false
3- sets Inflation::MaxInflation = Perbill(100_000_000) (10%) & IdealStake remains 75% as is.

Comments (6)

26 days ago

26 days ago

Would it be possible to have a verified id please Karam ? :)

22 days ago

@EhmW...1L7K been working with PA on fixing this bug/issue, ill ping them.

Load more comments
PleaseLogin to comment

Proposal Failed

Summary

0%

Aye

AyeNay

0%

Nay

Aye (10)0.0 DOT

Support0.0 DOT

Nay (33)0.0 DOT

Help Center

Report an Issue
Feedback
Terms and Conditions
Github

Our Services

Docs
Terms of Website
Privacy Policy

A House of Commons Initiative.

Polka Labs Private Limited 2025

All rights reserved.

Terms and ConditionsTerms of Website
Privacy Policy