Solana double disinflation: SIMD-0550 / SGP-0002 explained
What “double disinflation” means on Solana: inflation schedule parameters, -15% vs -30% disinflation, path to 1.5% terminal rate, emissions impact, staking/validator trade-offs, and the SIMD vs SGP process.
devrels.xyz/a/206short linkDouble disinflation is Solana community shorthand for proposals (notably SIMD-0550, discussed with governance docs such as SGP-0002) that double the annual disinflation rate on SOL issuance — from roughly 15% per year to 30% per year — so the network reaches its long-run 1.5% terminal inflation sooner. It is not “deflation,” not a burn of existing balances, and not a one-shot halving of supply.
This is a builder/operator map: parameters, what changes, who feels it, and how the docs process fits together. Figures below follow public mid-2026 modeling (e.g. Helius write-ups around a ~3.82% then-current rate); always re-check live stake and proposal status before acting.
Inflation vocabulary (precise)
| Term | Meaning on Solana |
|---|---|
| Inflation rate | Annualized pace of new SOL minted (protocol issuance), currently on a declining path toward a terminal floor |
| Disinflation | The scheduled percentage reduction of that inflation rate each year (e.g. rate becomes 15% lower than last year’s rate) |
| Double disinflation | Raise that yearly reduction from ~15% to ~30% — steeper slope down the same terminal |
| Deflation | Falling price level or net supply shrink — not what this proposal alone guarantees |
| Terminal inflation | Long-run floor of the schedule (1.5% in the classic design) |
Each year (simplified):
next_inflation ≈ current_inflation × (1 + disinflation_rate)
disinflation_rate = -0.15 // status quo schedule
disinflation_rate = -0.30 // “double disinflation”
Until next_inflation hits the long-term floor (1.5%), then it stays there.The three knobs (only one turns)
| Parameter | Typical value | Double disinflation? |
|---|---|---|
| Initial inflation rate | 8% | Unchanged |
| Disinflation rate | −15% / yr → −30% / yr | This is the change |
| Long-term (terminal) inflation | 1.5% | Unchanged |
That single-parameter story is why proponents call it the simplest emissions cut that still uses the existing schedule — compare prior attempts that redesigned issuance more aggressively (community memory of SIMD-0228-era debates).
What the modeling claims (order of magnitude)
| Current-style (−15%) | Double (−30%) | |
|---|---|---|
| Example starting inflation (then) | ~3.82% (snapshot cited in proposals) | |
| Time to 1.5% terminal | ~5.7 years (e.g. H1 2032) | ~2.8 years (e.g. H1 2029) |
| Future emissions (multi-year window) | Baseline | Materially lower (public write-ups cite ~18–22M SOL less over ~6 years depending on model) |
| Activation lag | Governance + feature-gate lag assumed in models (months), not instant | |
Numbers move with activation date, stake dynamics, and exact feature-gate timing. Treat Helius/forum figures as scenario analysis, not consensus oracle.
Who feels it
| Actor | Can / benefit side | Can’t ignore / risk side |
|---|---|---|
| Holders (non-staked) | Lower long-run dilution path if schedule activates | No automatic price floor; market is separate |
| Stakers | Same terminal design; faster glide to lower issuance | Nominal staking yields tied to inflation compress earlier — real yield still depends on fees/MEV share |
| Validators | Clearer long-run monetary story; simpler than novel issuance mechanisms | Margin pressure if inflation drop outruns fee revenue growth; set already sensitive |
| App builders | Protocol economics narrative; no app-code change required for the parameter itself | Don’t hardcode “APY forever” in product UX; read stake pool / LST docs after any activation |
| LSTs / stake pools | Same SOL mechanics underneath | Revisit fee models and marketing that quote sticky inflation APY |
SIMD vs SGP (process)
| SIMD-0550 (technical) | SGP-style vote (social/governance) | |
|---|---|---|
| Job | Specify the protocol parameter change and implementation path (feature gate) | Ask validators/delegators to endorse the policy before/while shipping |
| Outcome if accepted | Code + activation path | Stake-weighted signal; not a substitute for client releases |
| Outcome if rejected | Schedule stays on −15% path | No endorsement; technical work may still iterate |
Exact thresholds (support phase stake %, discussion epochs, supermajority of For vs Against) live in the active SGP/SIMD text — read the live PR and forum thread; drafts have iterated. Related: Solana on-chain governance / SGP.
What double disinflation is not
- Not a burn of your wallet balance — it changes future mint rate, not past balances.
- Not guaranteed “ultrasound SOL” — net supply path still depends on issuance minus burns/fees; other SIMs (fee markets) may interact later.
- Not free lunch for validators — inflation was part of the security budget story; fee growth has to carry more weight sooner.
- Not automatic the day the tweet drops — governance + implementation + feature gate lag.
Builder checklist
| # | Action |
|---|---|
| 1 | Link “APY” UIs to a data source that can update after activation — no hard-coded 7% forever |
| 2 | Stake pool / LST docs: note inflation component vs fee/MEV component |
| 3 | Treasury / runway models: scenario both −15% and −30% paths |
| 4 | Watch feature-gate notes in Agave/client release blogs if the SIMD lands |
| 5 | Separately track fee-burn / resource-fee SIMs — monetary story is multi-proposal |
Resources
- Forum: SIMD-0550 discussion
- Explainer (proponent deep dive): Helius — Why Solana Should Double Disinflation
- Interactive modeling (community): solburnrate.xyz
- Related DevRels: SGP governance · Stake program
Bottom line
Double disinflation = steeper scheduled decline of Solana’s inflation rate (−15% → −30% per year), same 1.5% terminal, shorter path to that floor, fewer SOL minted along the way. Simple parameter; non-simple politics and validator economics. Builders rarely change a line of program code for it — they change assumptions in yield UX, treasuries, and stake-product copy once the feature gate is real.
Keep reading
Solana's protocol votes used to be ad hoc SPL-token ballots coordinated off chain. As of July 2026 there is standing machinery: two mainnet programs, a fixed 11-epoch lifecycle, Merkle-proof-verified stake weights, and a staker sovereignty mechanism that lets delegators overrule their validator's vote with their own stake. Here is how the SGP system works end to end, how it differs from SIMDs, and what is already queued to vote.
Native Solana stake UX without an LST: stake, unstake, and merge — plus split when you need a second validator.
Stake accounts, the warmup/cooldown math, the four states, and the actual instruction shapes for delegate, deactivate, split, merge, and withdraw. The technical reference.
Get new articles in your inbox
Technical deep-dives on Solana tooling, infrastructure, and ecosystem. No noise.
