d0932d19-3
Solana token account deposits could fall 86% under staged rent cuts
Solana’s staged rent cuts could reduce standard token-account deposits by about 86%, lowering the requirement from 0.001488 SOL to 0.000204 for apps and wallets.

Outputs
SIMD-0437’s last three stages would cut storage rent from 5,080 to 696 lamports per byte, a reduction of about 86%.
A 293-byte standard SPL token account would require 203,928 lamports, or about 0.000204 SOL, versus 1,488,440 lamports at the current rate.
Funding 100,000 new standard token accounts would require about 128.45 SOL less in upfront deposits, before transaction fees.
Solana’s Nov. 18 recap put the expected reduction around early December after Anza CEO Brennan Watt’s Nov. 17 Breakpoint remarks.
Each remaining cut has a separate activation switch, while a fallback can restore the original 6,960-lamport rate.
By Nathan Brooks
Solana expects the deposit required to open a standard SPL token account to fall about 86% to roughly 0.000204 SOL once the final three stages of SIMD-0437 activate, according to the project’s Nov. 18 recap of Anza CEO Brennan Watt’s Nov. 17 Breakpoint remarks.
That would be a roughly sevenfold reduction from the current storage rate of 5,080 lamports per byte to 696 lamports per byte.
Watt gave a two-week window, putting the expected reduction around the start of December. Solana’s recap presents one window for the expected drop, while the proposal gives each remaining cut its own activation switch. Operators therefore cannot treat the early-December estimate as a single simultaneous rate change.
Solana calls the required minimum balance “rent.” The amount scales with account size, and the network’s rent guide provides the calculation. A standard SPL token account contains 165 bytes, plus 128 bytes of overhead:
- At the current 5,080-lamport rate, a 293-byte account requires 1,488,440 lamports, or about 0.001488 SOL.
- At the proposed final rate of 696 lamports per byte, the same account requires 203,928 lamports, or about 0.000204 SOL.
- The difference frees about 0.001285 SOL of upfront funding for each new standard token account.
An operator creating 100,000 standard token accounts would post about 128.45 SOL less in deposits, before transaction fees.
The Solana Foundation’s dollar comparison uses an earlier starting point: about $0.16 for a token account before any of the five cuts and roughly $0.016 after all five. At the same SOL price, the deposit at today’s rate would be closer to $0.12. The protocol sets the deposit in SOL, so its dollar cost changes as the token’s price changes.
Rent and transaction costs remain separate. Transactions carry their own fees.
What does the rent cut change for apps and wallets?
Whoever funds an account posts the minimum balance at creation. The balance stays with the account until its program permits withdrawal or the account closes. The same requirement applies when developers create accounts to store information an on-chain program needs.
Whether an app saves depends on its account-creation pattern. A service that opens a fresh token account for each customer receives the lower requirement every time it creates one. A service whose customers already have the required accounts makes fewer new deposits. Existing accounts do not reprice retroactively because Solana applies the rate in force when an account opens.
A wallet may need to create a token account when a user first receives a token under a given mint. Later transfers can reuse that account, so the savings arise when new accounts open rather than on every transfer.
The owner or an authorized party can close a standard token account after its token balance reaches zero. The closing instruction sends the lamports to a designated destination. Solana returns the storage deposit when an eligible account closes.
The full reduction originated in SIMD-0437, a proposal from Anza’s Igor Durovic. It called for five sequential reductions from an original rate of 6,960 lamports per byte:
- The first two cuts set the rate at 6,333 and then 5,080 lamports per byte.
- The remaining cuts would set it at 2,575, 1,322 and finally 696 lamports per byte.
The second step reached mainnet in September at epoch 1033, according to the active feature entry reproduced in the Surfpool issue tracker. Anza’s feature tracker lists the 2,575 and 1,322 settings as separate entries.
The first two cuts lowered the original rate by about 27%. The last three would lower the current rate by about 86%, while the full rollout would reduce the deposit to one-tenth of its original size for an account storing the same amount of data.
Solana applies the applicable rate when an account opens. An account created between two cuts therefore requires a different deposit from one created after the final switch.
Lower deposits reduce the cost of opening accounts that validators must maintain. The proposal asks developers to review how much on-chain data accumulates after each reduction before advancing to the next one. A separate fallback switch can restore the original 6,960-lamport rate if storage growth or other problems warrant reversing the cuts.
The next operational checkpoint is activation of the 2,575-lamport stage; the 696-lamport rate becomes applicable only after the final switch, preserving a staged change to account funding rather than one immediate repricing.
via crypto.news (Source)
More from Nathan Brooks
Show full bio
Market editor covering money, funding and market shifts around crypto and web3 industry at Mempool Brief.
1,574 articles