Solana’s plan to cut account deposits by 90% could weaken a reason to hold SOL

Eligible Solana token-account owners can reclaim excess SOL previously needed to keep their token accounts open after the network's first rent reduction went live Sept. 3. For businesses funding new accounts, the same...
Bitcoin 1 Minute
An important story is making waves across the blockchain ecosystem. Eligible Solana token-account owners can reclaim excess SOL previously needed to keep their token accounts open after the network's first rent reduction went live Sept. For businesses funding new accounts, the same change lowers the upfront capital required to create them. The full plan would change how account growth translates into SOL held against storage.
If Solana completes its proposed 90% reduction, total persistent account state, including each account's storage overhead, would have to grow tenfold to require the same minimum SOL reserves as before the rollout. Adoption could expand substantially while the minimum SOL needed for this reserve channel falls. The Solana Foundation's tracker confirms that only the first reduction, approximately 9%, is live on mainnet.
Market Dynamics
The tenfold comparison applies to the conditional final target, while the initial cut already lowers reserve requirements. Related Reading Solana’s Agave 4. 2 activation target arrives with mainnet feature gates still pending Solana rent reduction and the 10× hurdle Solana's “rent” is a balance held against account storage.
It is generally recoverable when an account closes, rather than an ongoing bill paid to validators. Reducing the required balance lets new accounts begin with less SOL and can leave existing accounts holding more than their minimum. At epoch 1028 on Sept.
3, Solana lowered the reserve parameter from 6,960 to 6,333 lamports per byte. The five-stage plan's final target is 696. Under SIMD-0437, the rent-reduction specification, that minimum equals the account's data size plus 128 bytes of overhead, multiplied by the current lamports-per-byte parameter.
Market Impact
A standard token account has 165 data bytes, making its effective size 293 bytes. Applying that formula to one million identical standard token accounts gives the following illustration: Before the rollout 6,960 2,039. 28 SOL Baseline First step, live Sept.
711 SOL Final target, conditional 696 203. 352 SOL These are calculated minimum requirements for a fixed account population, not measured withdrawals. The final row assumes all five reductions activate.
Different account sizes would produce different totals. The million-account example illustrates operating capital, but it cannot establish a network-wide supply effect. Its conditional final reduction of 1,835.
Crypto markets are watching this development closely as investors weigh its potential impact on prices.





