Solana validators approved a cut to SOL issuance five days ago. The change could not be scheduled, because the code that calculates inflation still used floating-point arithmetic, and floating point cannot be trusted to produce the same answer on two different validator clients. The proposal that removes it, SIMD-0607, merged at 00:32 UTC this morning. The client release it targets is still in alpha.
This is the step between a governance mandate and anything actually changing, and it is the part that went unreported while the vote was covered everywhere.
What Was Actually Blocking It
SGP-0002 passed on 28 August at 67.00% against a 66.67% bar. It doubles Solana's annual disinflation rate from 15% to 30%, which removes roughly 18.9 million SOL from issuance over six years and brings the 1.5% terminal rate forward from around 2032 to around 2029.
What it does not do is change anything by itself. The implementation lives in SIMD-0550, which activates a feature gate called double_disinflation_rate that sets the inflation taper to 0.30. That gate could not be scheduled until a separate problem was solved.
The Problem in One Sentence
Solana's inflation and rent calculations used floating-point maths, including the platform function powf, and two validator clients running on different hardware or different maths libraries are not guaranteed to get bit-identical answers from it.
The SIMD-0607 document states the stakes plainly:
Inflation rewards and rent parameters affect capitalization, account state, and bank hashes. These values must be computed identically by all validator clients, without relying on IEEE-754 behavior or platform math-library functions such as powf.
Bank hashes are what validators compare to agree on the state of the chain. If two clients compute a reward differently by even one lamport, their bank hashes diverge and the network forks. Solana now runs two independent clients in production, Agave and Firedancer, so this stopped being theoretical.
What SIMD-0607 Does
It replaces the floating-point path with fixed-point integer arithmetic. Rates become a fraction of two integers, multiplication uses a widened 128-bit intermediate, and rounding is specified as always toward zero:
Fraction { numerator: u64, denominator: NonZeroU64 }
mul_fraction_floor(value, fraction) =
floor(value * fraction.numerator / fraction.denominator)Nothing here is clever. That is the point. Every implementation detail that a compiler or a maths library might decide differently is pinned down in the specification, so two clients written by two teams in two languages produce the same integer.
Who Wrote It Matters
The document is authored by Tao Zhu of Anza and Tom Pointon of Firedancer. The two client teams whose implementations must agree wrote the specification for agreement together. For a network whose selling point is multiple independent clients, that is the process working as intended.
The Change Is Real but Economically Nil
Replacing floating point with integers changes the numbers slightly at rounding boundaries. The proposal quantifies exactly how much, across 6,000 epochs and every slot-time regime from 400ms down to 200ms:
| Taper | Largest epoch reward difference | In SOL |
|---|---|---|
| 15% (current) | 31,831,625 lamports | 0.031831625 SOL |
| 30% (after SGP-0002) | 14,181,312 lamports | 0.014181312 SOL |
Measured on a normalised capitalisation of 1 billion SOL with 432,000-slot epochs. Three hundredths of a SOL per epoch, network-wide, is not an economic change. It is a safety change that happens to be measurable, and publishing the bound is how you demonstrate that.
What Still Has to Happen
Merging the specification is one step of several. The chain of dependencies looks like this:
| Step | Status |
|---|---|
| SGP-0002 approved by validators | Done, 28 August, 67.00% For |
| SIMD-0607 specification merged | Done, 00:32 UTC on 1 September |
| Ships in Agave v4.4 | Not yet. Latest tag is v4.4.0-alpha.2, released 28 August. Newest stable release is v4.2.2. |
| Validators adopt the release | Not started |
double_disinflation_rate gate activated at an epoch boundary | Not scheduled |
Agave release tags from anza-xyz/agave, checked 1 September 2026. SIMD-0607 is explicitly consensus-affecting and, in its own words, "requires feature activation at an epoch boundary".
The gap between an alpha tag and a stable release adopted by most of the network is not a formality. Until that happens, nothing in a staker's rewards moves.
Why This Is Worth Following
Coverage of the vote treated approval as the outcome. It was not: it was a mandate to begin, and the first thing the mandate ran into was a decade-old shortcut in the reward maths.
Two things follow. Governance now has a visible dependency chain, and anyone tracking when SOL issuance actually falls should watch Agave release tags rather than governance headlines. And Solana's second client has changed what the protocol can leave undefined. Floating point was tolerable when one implementation defined correctness by existing. With Firedancer in production, "whatever Agave computes" stopped being a specification.
Our coverage of the governance vote result sets out the tallies, including the unresolved question of which rulebook decides SGP-0003.
The Bottom Line
- SIMD-0607 merged at 00:32 UTC on 1 September, removing floating-point arithmetic from Solana's consensus-critical inflation and rent calculations.
- It was blocking the supply cut. The
double_disinflation_rategate from SGP-0002 could not be scheduled until the reward maths was deterministic across clients. - Authored jointly by Anza and Firedancer engineers, which is the point: the two clients that must agree specified the agreement.
- The economic effect is nil. Relative reward drift is below 2.1e-7, at most 0.0318 SOL per epoch on a 1 billion SOL capitalisation.
- Nothing changes yet. Agave v4.4 is at alpha.2, stable is v4.2.2, and the feature gate has no schedule.
Sources and Methodology
How This Was Checked
The proposal text, its authorship, its merge time and its status were read directly from the Solana Foundation's improvement-documents repository through the GitHub API, not from coverage. The reward drift figures and the quoted motivation are from the merged document itself. Agave release tags and dates were read from the repository's releases. Price data came from CoinGecko's public API and is timestamped below.
Sources
- SIMD-0607 pull request - merge time 00:32:59 UTC, 1 September 2026, opened 24 August by tao-stones
- SIMD-0607 proposal text - authors, motivation, fixed-point design, drift figures, backwards-compatibility note
- SIMD-0550 - the disinflation implementation SIMD-0607 extends
- anza-xyz/agave releases - v4.4.0-alpha.2 and v4.2.2 tags (checked 1 September 2026)
- Solana Validator Governance - the SGP-0002 tally
- CoinGecko - price, market capitalisation and volume (retrieved 09:48 UTC, 1 September 2026)
Market Context
SOL traded at $102.10 with a market capitalisation of $59.73 billion and $2.98 billion in 24-hour volume, down 1.10% on the day, as of 09:48 UTC on 1 September 2026. August closed as Solana's first monthly gain in ten months.
Disclosure
This article is news analysis, not investment advice. It contains no price prediction and no recommendation to buy, sell or stake. The yield figures are model outputs published with SIMD-0550, under the assumptions stated, and describe a schedule that has not begun.