Is Solana rent being reduced in 2026?

Yes. Solana has proposed five independent feature gates that lower the rent constant from 6,960 to 696 lamports per byte, a 90% reduction. The gates activate separately, so check the current mainnet reserve instead of assuming the full reduction is already live.

Does Solana return excess rent automatically?

No. Lowering the rent-exempt minimum does not automatically move SOL out of existing accounts. Eligible Token Program accounts can use WithdrawExcessLamports to transfer only the balance above their current reserve, while closing an empty account returns its entire remaining balance.

How much SOL will a token account need after the rent reduction?

The answer depends on the account's data length and the latest active feature gate. A standard 165-byte token account historically required 0.00203928 SOL; after the final proposed step its calculated reserve would be 0.000203928 SOL, provided the rollout reaches that stage.

Can the same account reclaim excess SOL more than once?

Potentially, yes. A withdrawal leaves the account at the current rent-exempt minimum. If a later feature gate reduces that minimum again, the retained account can develop a new surplus and become eligible for another withdrawal without being closed or changing its token balance.

Solana Rent Reduction 2026: Phases, Costs, and Refunds

Solana's rent system is changing. The network plans to reduce the storage bond for on-chain accounts by 90%, but the change is split across five independently activated steps. That distinction matters: an announced target is not the same as the reserve enforced by mainnet today.

What is changing about Solana rent in 2026?

SIMD-0437 lowers Solana’s storage reserve through five independent feature gates targeting 696 lamports per byte. Our dated mainnet check is consistent with the second step, 5,080. Existing balances do not move automatically; eligible surplus needs an authorized withdrawal. Later steps remain distinct from today’s live reserve.

"Rent" is an awkward name for this balance. It is not a recurring charge that validators slowly consume. It is a refundable storage bond: an account must keep a minimum amount of SOL based on its data size, and that balance normally returns when the account closes.

The Solana Foundation's reduced-rent overview and SIMD-0437 define the minimum as:

minimum balance = (128 + account data bytes) × lamports per byte

The fixed 128 bytes represent storage overhead. A classic mint uses 82 data bytes, a standard token account uses 165, and a token multisig uses 355. Token-2022 accounts can be larger because extensions add data, so their reserves must be calculated from their actual lengths.

What are the five Solana rent-reduction phases?

Stage	Lamports per byte	Effective reduction from 6,960	Activation model
Legacy setting	`6,960`	0%	Historical baseline before the new gates
SIMD-0437-1	`6,333`	9%	Independent feature gate
SIMD-0437-2	`5,080`	27%	Consistent with the dated mainnet RPC check below
SIMD-0437-3	`2,575`	63%	Independent feature gate
SIMD-0437-4	`1,322`	81%	Independent feature gate
SIMD-0437-5	`696`	90%	Final proposed target

Core developers can pause between stages while they study account growth. A separate safeguard can restore the legacy value if needed, which is another reason applications should read the current reserve from RPC rather than embed a permanent number.

Status checked September 16, 2026 at 23:25 UTC: A finalized public mainnet RPC check returned 0.001066800 SOL for an 82-byte mint, 0.001488440 SOL for a 165-byte token account, and 0.002453640 SOL for a 355-byte multisig, consistent with the second step at 5,080 lamports per effective byte. A separate finalized-slot request in the batch returned 447646918; the reserve calls do not return their own context slot. These are dated observations, not permanent constants or evidence that all five steps are active.

How much SOL could become excess?

The gross surplus is the account's actual lamport balance minus the current rent-exempt minimum for its data length. For an older account that still holds exactly the legacy reserve and has never withdrawn surplus, the proposed first and final stages illustrate the range:

Account type	Legacy reserve	Gross surplus after stage 1	Gross surplus after stage 5
82-byte mint	`0.001461600 SOL`	`0.000131670 SOL`	`0.001315440 SOL`
165-byte token account	`0.002039280 SOL`	`0.000183711 SOL`	`0.001835352 SOL`
355-byte multisig	`0.003361680 SOL`	`0.000302841 SOL`	`0.003025512 SOL`

These are arithmetic examples, not payout promises. An account may hold extra SOL sent to it for another reason, use a different data length, or have already withdrawn at an earlier stage. A tool may also charge a protocol fee, and the wallet still pays the normal Solana transaction fee.

Does the rent reduction automatically refund your SOL?

No. The network changes the minimum balance but leaves existing account balances in place. To make the surplus spendable, an eligible Token Program account must execute WithdrawExcessLamports, or an empty account can be closed to return its entire remaining balance.

This creates three distinct actions:

Action	Account stays open?	Token or NFT changes?	SOL moved
Withdraw excess rent	Yes	No	Only lamports above the live reserve
Close an empty token account	No	No token remains	The account's remaining lamports
Burn an asset, then close	No	Asset is destroyed	Reclaimable balances from the supported burn path

The first option is the important new one. The Token Program's WithdrawExcessLamports instruction leaves token balances, mint supply, and account data untouched. It only transfers the surplus lamports.

Which accounts can use WithdrawExcessLamports?

The instruction supports Token Program and Token-2022 token accounts, mints, and multisigs, but authority rules still apply. A token account requires its owner or configured multisig. A mint normally requires its mint authority. A mint with no authority must sign as the source itself, either with its original keypair or through its owning program by CPI.

Native wrapped-SOL token accounts are not supported. Metadata, edition, token-record, and arbitrary program accounts are not Token Program accounts, so this instruction cannot withdraw from them. Compressed NFTs do not have an individual token account at all.

How does Sol Incinerator calculate the amount?

Sol Incinerator asks the backend to inspect the live source balance, actual account data length, and current rent-exempt reserve. The website's excess-rent flow charges a base protocol fee of 200 basis points, or 2%, of the gross surplus. Fee math is floored to whole lamports, and the normal network fee is separate.

The preview immediately before signing is the source of truth. It can account for the active rent stage, previous withdrawals, extensions, and the exact accounts selected in a way that a static article cannot.

An account left open can become eligible again after another rent reduction. Re-scan after later feature gates rather than assuming the first withdrawal captured the full five-stage reduction.

How does SIMD-0437 affect the Solana ecosystem?

For users, a lower active reserve reduces the SOL needed to fund the same amount of new account storage. It can also leave surplus in older accounts. Those are different benefits: new-account funding is lower up front, while existing-account recovery still needs an authorized operation.

For application developers, lower storage funding can make account creation and sponsored onboarding easier to budget. That is an inference from the reserve formula, not a guarantee of adoption or cheaper end-to-end transactions. Developers still need to account for transaction fees, required account sizes, and the programs that control recovery.

For validators and indexers, cheaper account creation can change demand for stored state. The proposal's staged rollout provides observation points before deeper reductions. It is not evidence that storage has become free or that capacity concerns have disappeared. Use measured state growth rather than assuming every announced step must activate on schedule.

For protocols with user-related program accounts, a lower reserve does not grant each user a generic withdrawal right. The owning program must expose an appropriate authorized path. A token-account instruction cannot drain arbitrary PDAs simply because the user helped fund them.

Does SIMD-0437 reduce transaction fees or predict SOL prices?

The rent parameter sets a storage reserve. It is not the same parameter as a transaction's network fee, and reducing it does not establish a proportional reduction in every cost of using Solana. Likewise, released storage balances do not provide a reliable standalone forecast of SOL's market price.

Compare practical outcomes instead: new-account funding, current eligible surplus, and the actual cost of the selected recovery. Keep price predictions and unsupported estimates of total ecosystem refunds out of that calculation.

Sol Incinerator

Scan your wallet and preview eligible excess SOL without closing retained accounts.

Try it now