33
Cronos POS Chain · Proposal #33
Passed on 19 May 2026 with 99.4% of the votes for yes.
Yes
99.4%
100.0% without abstain
Veto
0.0%
of votes cast
Ended
19 May 2026
99.41%
of votes cast
0.59%
of votes cast
0.00%
of votes cast
0.00%
of votes cast
This proposal initiates a network upgrade for the Cronos POS Chain (crypto-org-chain-mainnet-1) to the v7 release. The upgrade transitions CRO from an emissions-based staking model to a revenue-based model, with three coordinated changes:
Smooth Inflation Decay (new x/inflation module). A monthly compound decay is applied on top of x/mint's base rate, providing a deterministic path from 1% inflation toward zero. Decay rate proposed at 6.8% per month, applied per-block via continuous interpolation. Inflation is clamped at zero and x/mint InflationMin/InflationMax are pinned to 1% (InflationRateChange = 0). MaxSupply is enforced at 100B CRO.
Tiered Time-Locked Staking (new x/tieredrewards module). Delegators may lock CRO into time-committed positions earning a flat bonus APY on top of the base staking rate. Initial tiers: 1y / +2%, 2y / +4%, 4y / +7%, all with a 100 CRO minimum lock. Voting rights, validator redelegation, and reward withdrawal are preserved during the lock. A TargetBaseRewardsRate of 3% is set as the per-block base-rewards floor, topped up from the rewards pool when block fees fall short.
Revenue Bridging. Infrastructure to channel protocol revenue from the broader Cronos ecosystem (including the upcoming Cronos App) to the Cronos POS rewards pool, intended to progressively fund tier bonus rewards as natural emissions decay.
Key parameters proposed: MaxSupply = 100,000,000,000 CRO; DecayRate = 0.0680 (6.8%/month); InflationMin = InflationMax = 0.01; InflationRateChange = 0; TargetBaseRewardsRate = 0.03; tier exit durations 1y / 2y / 4y at +2% / +4% / +7% bonus APY; tier minimum lock 100 CRO. All x/inflation and x/tieredrewards parameters remain governance-adjustable post-upgrade. The 100B CRO supply cap is preserved.
Upgrade height: 29,782,800 (target activation approximately 2026-05-20 15:00 HKT, subject to ~5.06s mean block time). Validators and full nodes are required to upgrade chain-maind at the upgrade height; binaries and checksums will be published on the chain-main releases page. Existing delegations are not migrated and continue at the base tier with no action required.
For the full proposal text, motivation, parameter table, FAQ, technical references, and ADRs, please refer to the discussion post: [Hidden link]