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:
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.
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:
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.
Threshold
Threshold