Solana’s Rent Reduction Plan Lowers Account Deposit Requirements

Solana’s network has implemented the first phase of its rent‑reduction roadmap, decreasing the minimum SOL balance required to keep token accounts open. The change went live on September 3, lowering the reserve parameter from 6,960 to 6,333 lamports per byte.

How the reduction works

Solana’s rent model holds a refundable balance against each account’s storage. The balance is calculated as the account’s data size plus a 128‑byte overhead, multiplied by the current lamports‑per‑byte rate. A standard token account (165 data bytes) therefore requires a minimum of 293 bytes of effective size.

Illustrative numbers

• Original rate: 6,960 lamports/byte → 2,039.28 SOL per million token accounts.
• First step (live): 6,333 lamports/byte → 1,855.57 SOL per million accounts.
• Final target (conditional): 696 lamports/byte → 203.93 SOL per million accounts.

The final target would represent roughly 0.0003 % of Solana’s circulating supply of about 585 million SOL.

Implications for users and businesses

Existing accounts can reclaim any SOL held above the new minimum without closing the account, using the WithdrawExcessLamports instruction. The authority to withdraw rests with the account owner or the relevant program, meaning the party that funded the original deposit may not automatically have the right to reclaim excess funds.

For businesses that create token accounts for customers, the lower upfront requirement means they can fund more accounts with the same capital, potentially expanding onboarding without requiring customers to purchase SOL.

Potential impact on SOL demand

The rent reduction reduces the amount of SOL locked as a storage reserve. However, the overall demand for SOL also depends on other factors such as transaction fees (half of the base fee is burned, half goes to validators) and staking rewards. The full effect on SOL price or network security cannot be determined from the rent change alone.

Next steps in the roadmap

The second reduction, to 5,080 lamports per byte, is currently on testnet with a mainnet rollout expected in mid‑September. The remaining three steps are planned for the Agave 4.4 upgrade in November, each subject to review and possible rollback if state growth exceeds expectations.