Solana account deposits (rent-exempt minimums), read live
The SOL an account must hold to exist on Solana, by account size, read from the network, with each 2026 reduction step dated from its feature account.
On 2026-11-16 Solana's deposit for a new token account was 1,488,440 lamports (0.00148844 SOL), down from 2,039,280 before the 2026 cuts; 2 of the 5 reduction steps are active on-chain, the last on 2026-09-11.
- Token account (USDC, USDT)
- 1,488,440 lamports
- 0.00148844 SOL
- Minimum SOL in a wallet that holds any
- 650,240 lamports
- 0.00065024 SOL
- Rate now
- 5,080 lamports a byte
- was 6,960
- Reduction steps active
- 2 of 5
The table
6 rows, 9 columns. Click a column heading to sort. The plain-English explanation is on its page.
| Account | Data size (bytes) | Deposit now (lamports) | Deposit now (SOL) | In dollars (USD) | Before the 2026 cuts (lamports) | Change (%) | If all five steps activate (lamports) | Who can get it back |
|---|---|---|---|---|---|---|---|---|
| A wallet holding only SOL (no data) | 0 | 650,240 | 0.00065024 | 0.0455 | 890,880 | -27 | 89,088 | The wallet itself. A SOL balance must be zero or at least this much. |
| Token account, classic token program (USDC, USDT) | 165 | 1,488,440 | 0.00148844 | 0.1041 | 2,039,280 | -27 | 203,928 | The token account's owner, when the account is closed (or its close authority, if one is set). |
| Token-2022 account with no extra features | 170 | 1,513,840 | 0.00151384 | 0.1058 | 2,074,080 | -27 | 207,408 | The token account's owner, when it is closed. |
| Token-2022 account for PYUSD or USDG | 187 | 1,600,200 | 0.0016002 | 0.1119 | 2,192,400 | -27 | 219,240 | The token account's owner, when it is closed. |
| Stake account | 200 | 1,666,240 | 0.00166624 | 0.1165 | 2,282,880 | -27 | 228,288 | Whoever holds the withdraw authority, after the stake is deactivated and withdrawn. |
| Durable nonce account | 80 | 1,056,640 | 0.00105664 | 0.0739 | 1,447,680 | -27 | 144,768 | The nonce authority, when the account is withdrawn. |
Showing all 6 rows. Full table as CSV
History
7 readings kept in the file, newest first.
| Date (UTC) | Lamports a byte | Token account (lamports) | SOL-only wallet (lamports) | Steps active |
|---|---|---|---|---|
| 2026-11-16 | 5,080 | 1,488,440 | 650,240 | 2 |
| 2026-11-15 | 5,080 | 1,488,440 | 650,240 | 2 |
| 2026-11-14 | 5,080 | 1,488,440 | 650,240 | 2 |
| 2026-11-13 | 5,080 | 1,488,440 | 650,240 | 2 |
| 2026-11-12 | 5,080 | 1,488,440 | 650,240 | 2 |
| 2026-11-11 | 5,080 | 1,488,440 | 650,240 | 2 |
| 2026-11-10 | 5,080 | 1,488,440 | 650,240 | 2 |
Showing all 7 readings. Full history in the JSON
How this is measured
Deposit = getMinimumBalanceForRentExemption(bytes) at finalized commitment, read on every run; the token-account figure is read from every public endpoint and must agree. Agave computes it as (128 + data bytes) x lamports per byte, so each figure is also recomputed from the rate the active feature accounts imply and from the rent sysvar, and all three must match. A feature account's data starts with 1 and the activation slot (u64, little endian) once it is active; the date is getBlockTime of the first produced block at or after that slot. The "before 2026" column uses the legacy 6,960 lamports a byte; the "after all five steps" column uses 696 and is arithmetic, not a reading.
What would make it wrong
- getMinimumBalanceForRentExemption has no historical parameter. An account opened before a cut still holds the larger deposit it was opened with, and gets all of it back when closed; today's figure applies only to new accounts.
- The deposit is not a fee. It stays in the account and belongs to whoever can close it (usually the owner), not to whoever paid it.
- Token-2022 accounts are larger when the token uses extensions, so their deposit is larger. Our Token-2022 sizes were read from live accounts on 2026-11-10; other tokens can differ.
- Steps 3 to 5 are planned, not live. Core developers can pause them, and SIMD-0438 can reset the rate to 6,960.
- A wallet can also go to exactly zero SOL; the minimum applies only while it holds any SOL.
Sources
- solana.com /docs/rpc/http/getminimumbalanceforrentexemption
- solana.com /upgrades/reduced-rent
- github.com /solana-foundation/solana-improvement-documents/blob/main/proposals/0437-incremental-rent-reduction.md
- raw.githubusercontent.com /anza-xyz/agave/master/feature-set/src/lib.rs
Every number here is read (from the network or a public API, at the time shown), computed from reads by the formula above, or stated by its source; the methodology page explains the three. SolPilled is independent and unofficial, not the Solana Foundation. Nothing here is financial advice.
Cite or reuse this data
Free to reuse with attribution under CC BY 4.0. Machine-readable: /data/costs-deposits.json (everything, including history and the method) and /data/costs-deposits.csv (the table). Agents can also read it through our MCP server.
Suggested citation:
SolPilled, "Solana account deposits (rent-exempt minimums), read live", https://solpilled.com/data/costs-deposits/ (data as of 2026-11-16T00:42:46.855Z). CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/), attribute SolPilled (solpilled.com). More Solana data
- Exit cost of Solana staking tokens by size
- The SOL holder ledger: what each way of holding SOL pays
- Bridging USDC to Solana: what $100, $1,000 and $10,000 land as
- Solana transaction fees, sampled from recent blocks
- Where Solana fees go: apps, the chain itself and Jito tips, 30 days
- Solana epoch length, measured
- Solana incidents: the official status page record, and what we measure
- Solana protocol changes, 2025 to 2026, dated from the chain
- Solana speed, measured: slot time and real transactions per second
- Solana supply, inflation and staked share
- Solana validators: stake concentration and client mix
- The Solana ecosystem by category
- Solana's headline numbers, one reading a day