What is Solana?
๐ New to this? Just start reading at the top โ it begins in plain English and gets more detailed as you scroll. Jump to any level:
๐ข The simple version
Plain English โ no jargon. Start here.
Solana is a blockchain built to be fast and cheap โ like Ethereum, but designed to handle huge numbers of transactions for tiny fees.
The "fast and cheap" chain
Solana does many of the same things as Ethereum โ it runs apps, supports digital art, lets people trade โ but it was designed from the start for speed. It can handle a lot of activity at once, and the fees are usually a fraction of a cent. That makes it feel snappy, more like a normal app.
What it's known for
Because it's quick and cheap, Solana attracts a lot of fast-moving activity: trading, games, and a famously lively scene of "meme coins" (fun, hype-driven tokens โ often very risky). It has a young, energetic community and a slick, modern feel.
The trade-off to know
That speed comes with a catch. Solana relies on fewer, more powerful computers than Ethereum, which makes it a bit more centralised, and in its earlier years the network occasionally went down for a while (it's become more reliable since). It's an exciting, fast network โ just go in knowing it's newer and its coin, SOL, is volatile like the rest of crypto.
๐ก A bit more detail
For when you want to go a little deeper.
Proof of History: how the clock works
Proof of History (PoH) is not a consensus mechanism by itself โ it is a timekeeping mechanism that works alongside Solana's consensus layer. It uses a Verifiable Delay Function (VDF): a computation that takes a predictable, irreducible amount of time to run, but whose output can be quickly verified by others.
A PoH generator continuously runs SHA-256 in a loop, hashing its own previous output. Each hash output โ with its count โ serves as a cryptographic timestamp. Because SHA-256 is sequential (each hash requires the previous one), and because the count is verifiable, the sequence proves that a specific amount of time elapsed between any two events in the chain. Transactions are inserted into this hash sequence, timestamping them cryptographically without requiring any external agreement.
This means validators do not need to communicate with each other to agree on transaction order โ the PoH sequence already establishes it. They can validate transactions in parallel, dramatically increasing throughput.
Solana's real-world use cases as of 2026: Visa USDC settlement pilot (cross-border payments), Jupiter DEX aggregator (largest by Solana DeFi volume), Dialect and Blink social payment tools, Tensor NFT marketplace, and consumer apps like Drip (digital collectibles). The Firedancer upgrade is expected to enable Solana to serve as infrastructure for high-frequency trading systems and large-scale payment networks.
Solana's architecture: eight innovations
The Solana whitepaper describes eight technical innovations that together enable its performance. The most significant beyond PoH are: Tower BFT (a PoH-optimised version of PBFT consensus that leverages the PoH clock to reduce messaging overhead), Turbine (a block propagation protocol that breaks data into small packets and uses a tree structure for efficient dissemination across validators), Gulf Stream (a mempool-less transaction forwarding protocol that pushes transactions to validators before the current block is finalised), and Sealevel (a parallel smart contract runtime that executes non-overlapping transactions simultaneously on all available cores).
Sealevel is particularly important for DeFi: because Solana contracts declare which accounts they will read or write in advance, the runtime can determine which transactions are independent and execute them in parallel โ something Ethereum's EVM cannot do natively.
Key metrics for Solana: TPS (transactions per second โ live at solscan.io), validator count and stake distribution (decentralisation indicator), Total Value Locked in Solana DeFi, network uptime history, and active monthly developers (a long-term health indicator). As of April 2026, Solana has over 23,500 monthly active developers โ second only to Ethereum. Live data: CoinGecko ยท Solscan.
SOL tokenomics
SOL has no hard cap โ new SOL is continuously issued as staking rewards. The initial inflation rate at mainnet launch was 8% annually, with a planned 15% reduction each year until reaching a long-term target of 1.5% annually. As of 2026, inflation is approximately 4โ5% annually. A portion of transaction fees is burned, partially offsetting issuance.
Validators and delegators who stake SOL earn rewards from this inflation. The Solana staking system uses a delegated proof-of-stake model: SOL holders can delegate their stake to validators without giving up custody of their tokens, earning a proportional share of validator rewards.
The Firedancer client โ technical significance
Prior to Firedancer, Solana had one validator client โ the Agave client (originally called Solana Labs client). A single client implementation is a significant risk: a bug in that one codebase can take down the entire network, as happened during Solana's 2022 outages. Firedancer is a fully independent rewrite in C by Jump Crypto, providing client diversity for the first time. With two independent clients, a bug in one does not halt the network โ the other continues operating. This is the same reason Ethereum has multiple client implementations (Geth, Nethermind, Besu, Erigon).
๐ฃ The full technical picture
For the technically curious.
The whitepaper: Yakovenko's original design
Anatoly Yakovenko published the Solana whitepaper in November 2017, titled "Solana: A new architecture for a high performance blockchain." The paper's central contribution is Proof of History: using a sequential, verifiable computation (specifically SHA-256) as a cryptographic clock to establish the passage of time between events without requiring network-wide consensus on timestamps.
The paper argues that existing blockchains conflate two distinct problems โ ordering events and achieving consensus โ and that separating them enables dramatic performance improvements. PoH handles ordering; Tower BFT handles consensus on the ordered sequence.
Source: Yakovenko, A. (2017). Solana: A new architecture for a high performance blockchain v0.8.13. solana.com/solana-whitepaper.pdf
Tower BFT: PoH-optimised consensus
Tower BFT is Solana's consensus protocol, derived from Practical Byzantine Fault Tolerance (PBFT). In standard PBFT, nodes exchange O(nยฒ) messages to reach consensus โ impractical at scale. Tower BFT leverages the PoH clock to reduce this communication overhead: validators use the PoH sequence as a shared source of truth for timing, allowing them to make voting decisions based on local state rather than round-trip message exchanges.
Each validator maintains a vote tower โ a stack of votes on the PoH sequence. Validators lock their votes with exponentially increasing timeouts: a vote cast 32 slots ago has a lockout of 2^32 slots before it can be reverted. This creates economic finality โ the cost of reverting a confirmed slot grows exponentially with depth, making reorganisations increasingly impractical.
Solana's account model differs from Ethereum's. All data on Solana โ including program (smart contract) code and program state โ is stored in accounts. Programs are stateless: they contain only executable code. State is stored in separate data accounts owned by programs. This separation enables Sealevel's parallel execution: the runtime can determine account access patterns before execution and schedule non-conflicting transactions on separate CPU cores simultaneously. Accounts have a fixed rent-exempt minimum balance in SOL; accounts that fall below this minimum are garbage-collected.
Turbine: block propagation at scale
A fundamental challenge for high-throughput blockchains is block propagation โ getting a new block to all validators quickly. If blocks are large and must be sent to every validator, bandwidth becomes the bottleneck. Turbine solves this with a protocol inspired by BitTorrent: the leader (block producer) breaks the block into erasure-coded packets and sends different shreds to different validators arranged in a tree structure. Each validator retransmits shreds to a subset of others. The erasure coding allows any validator to reconstruct the full block from a subset of shreds, tolerating up to one-third packet loss.
Source: Solana documentation โ Turbine Block Propagation. docs.solana.com/cluster/turbine-block-propagation
Key protocol parameters
- Consensus: Tower BFT (PoH + PBFT-derived)
- Slot time: 400 milliseconds
- Epoch length: ~2 days (432,000 slots)
- Practical TPS (2026): 50,000โ65,000 (Firedancer theoretical: 1M+)
- Transaction fee: ~0.000005 SOL base (~0.04 paise)
- Smart contract language: Rust (primary), C, C++
- VM: Berkeley Packet Filter (eBPF) โ not EVM-compatible natively
- Hash function: SHA-256 (PoH), SHA3-256 (accounts)
- Inflation: ~4โ5% annually (targeting 1.5% long-term)
- Validator clients: Agave (Solana Labs), Firedancer (Jump Crypto)
Source: Solana Foundation documentation. docs.solana.com ยท github.com/solana-labs/solana