Snapshot vs. Ledger
Think of the ledger as Solana's ordered history– every block, every transaction, ever since genesis. A snapshot is a compressed version of account state at one particular slot, a picture that freezes everything (balances, token accounts, program data) as it existed at that moment in time. Validators rely on snapshots and consider the deep ledger someone else's archival work– that split is one of Solana's most intentional design choices.
Your bank statement does the same. Your closing balance on this month's statement tells you what you have now. The box of every receipt you've ever kept tells you how you arrived there. The truth is that you rarely ever need the box– the balance is what lets you make decisions. A snapshot is the closing balance; the ledger is the box.
How Validators Use Snapshots
A validator coming online- or coming back up after a crash- does not retrace its steps all the way back to 2020. The validator downloads a full snapshot (typically created every 25,000 slots) plus smaller incremental snapshots that fill the gaps since then. Only the blocks that have appeared since the latest snapshot are replayed to the live tip. This means total bootstrapping is done in hours, even though full snapshots can be tens of gigabytes when holding the state of hundreds of millions of accounts.
The deep history is elsewhere. The part that most surprises Ethereum and Bitcoin people is that Solana validators do not retain the full historical ledger locally. Solana can reach 400ms-per-block, creating over 200,000 blocks a day. The complete history weighs in the hundreds of terabytes. Keeping that history on every validator machine would make economic sense for no one, so the network shares responsibility. Validators keep the current state and recent blocks. The archives are held by archival operators. You see this most clearly in Google Bigtable-based archival storage where RPCs like Helius can query two year-old transactions, and in the Old Faithful project packaging that complete historical ledger for open distribution.
How Solana Compares to Bitcoin and Ethereum
Bitcoin lives at the other extreme. Every full Bitcoin node downloads and verifies the entire chain from its genesis block in 2009 (currently ~600+ GB as of mid-2026), and every full node must replay every transaction ever in that initial sync. That approach can actually be feasible in Bitcoin because it processes such a small amount of data (7 transactions-per-second max). Purists like Bitcoin because every node in the network independently verifies all historical data.
Ethereum occupies the middle. Every full node (depending on client) must maintain roughly 1-2 TB. Most Ethereum operators choose to sync using a snapshot (like a checkpoint rather than a rewind to genesis), and Ethereum has even added the possibility of "history expiry"- meaning the data won't necessarily be stored on default nodes once the network state expands further. Solana has basically reached the same outcome first, though via necessity rather than intentionality.
Why Snapshots and the Ledger Matter
If you are an infrastructure operator, the difference between the snapshot and ledger can be the difference between a rough evening vs. a rough month. Imagine a validator operator who has suffered an Agave upgrade failure at 2 a.m. in the middle of a volatile market where every offline slot means their validator loses a significant portion of delegators' staked interest. This operator can simply wipe their bad state, request a new snapshot from a trusted peer, replay a few thousand recent slots, and begin voting again by dawn. If we operated on a Bitcoin-style complete rewind model at Solana's throughput, that recovery time would be in the range of weeks.
And if you are a user, this difference can help you understand behaviors you've observed. In Phantom, your current balances can be displayed almost instantly, because current state access is low-cost. Retrieving your full 2024 transaction history can take a few seconds longer- because your wallet's RPC provider is querying archival storage. The trade-off: the number of independent actors that hold the full history of Solana is significantly fewer than the number of independent actors that hold the full history of Bitcoin, so if you want access to Solana's full history, you'll have to rely on a handful of archival operators. Old Faithful's open archives is a great attempt at addressing that issue, but there are no easy fixes.
Does skipping old history reduce Solana's security?
Skipping old history does not weaken the network's consensus- validators have complete visibility over and can verify snapshot contents against hashes the network has agreed upon, and every new block is fully live-verified. What the design changes is who has to pay the cost of retaining all that historical data.
