Solana Slashes Token-Account Rent 90%, Cutting SOL Demand

Solana's SIMD-0437 rent-reduction plan went live on mainnet at epoch 1028 on September 3, cutting the per-byte reserve parameter from 6,960 to 6,333 lamports. The five-stage rollout targets a final rate of 696 lamports per byte, a 90% cut from the original. Under the formula (data size plus 128 bytes of overhead, multiplied by the current parameter), a million standard token accounts of 293 bytes each now require 1,855.569 SOL in minimum reserves versus 2,039.28 SOL before. At the conditional final step, that figure falls to 203.928 SOL, a 1,835.352 SOL reduction per million accounts.

Why it matters

Account reserves are one of SOL's structural demand channels: every new token account posts a refundable SOL deposit to cover its on-chain storage, capital that stays locked until the account closes. Lowering that floor lets payment providers fund dramatically more accounts with the same SOL, even when end users never buy the token. The Foundation's WithdrawExcessLamports instruction, available through both the standard token program and Token-2022, lets holders reclaim balances above the new minimum without closing accounts, releasing previously frozen working capital. Whoever controls withdrawal authority controls that capital: a payments provider that funded a customer's account cannot assume the original deposit comes back to it.

The change reframes SOL's role in onboarding from a meaningful capital sink toward a rounding error. At the million-account scale, the conditional final reduction is roughly 0.000314% of the 585.36 million SOL in circulation as of September 5, a small slice in absolute terms but a directional shift in how token growth translates into SOL held against storage.

Market impact

Fee demand and staking are separate channels and remain untouched by the cut. Under Solana's fee rules, half of every base fee is burned and half goes to the validator, with the full priority fee paid to validators, so higher throughput still recycles SOL into the validator economy. Reclaimed capital can be restaked or redeployed into new accounts, but the cited material does not establish either outcome as a quantifiable offset to lower reserves.

The second reduction, to 5,080 lamports per byte, sits on testnet with mainnet activation expected in mid-September. The final three steps ship with the Agave 4.4 release in November, each subject to review of state growth. A fallback parameter is preserved, so the original 6,960 lamports can be restored if the rollout overshoots.