Solana: A New Architecture for a High Performance Blockchain

Authors Yakovenko, Anatoly
Year 2017
Project Solana
License Public
Official Source https://solana.com/solana-whitepaper.pdf

This page is an educational summary and analysis of an official whitepaper or technical paper, written for reference purposes. It is not a verbatim reproduction. CryptoGloss does not claim authorship of the original work. All intellectual property rights remain with the original author(s). The official document is linked above.

“Solana: A new architecture for a high performance blockchain v0.8.13” is a technical paper published in November 2017 by Anatoly Yakovenko, a former senior staff engineer at Qualcomm. The paper introduces Proof of History (PoH) — a verifiable delay function used as a decentralized clock — and describes eight complementary innovations that together enable Solana’s claimed throughput of 50,000+ transactions per second on a single chain without sharding or Layer 2s.

> PDF hosting: The Solana whitepaper is available at solana.com/solana-whitepaper.pdf. Solana Labs published it as a public technical document with no redistribution restrictions stated.


Publication and Context

In 2017, blockchain throughput was a central research problem. Bitcoin processed ~7 tps. Ethereum ~15 tps. Visa ~24,000 tps. Every proposed solution involved a tradeoff: sharding splits state (Ethereum 2.0), Layer 2s add complexity (Lightning), DAGs avoided total ordering (IOTA, Nano).

Yakovenko’s insight was different: the throughput bottleneck was not computational — it was the time spent reaching consensus on the ordering of events. If nodes could agree on a trustworthy timestamp without messaging each other, block production could be dramatically accelerated.

Key facts:

  • Whitepaper: November 2017
  • Mainnet beta launch: March 2020
  • Mainnet (post-beta): December 2021
  • Co-founders: Yakovenko recruited Greg Fitzgerald (also from Qualcomm) and others before founding Solana Labs in 2018

The Core Problem: Why Blockchains Are Slow

Traditional blockchain consensus (Bitcoin’s Nakamoto consensus, Ethereum’s Casper) requires validators to communicate to agree on the order of transactions before they can be processed. This communication adds latency — the time for a message to travel around the network — as a fundamental bottleneck.

Yakovenko’s starting observation: if every node had a reliable, tamper-proof clock, they could independently agree on the order of events without messaging each other first. The question was how to build such a clock without a trusted authority.


Proof of History (PoH): A Verifiable Clock

Proof of History is a Verifiable Delay Function (VDF) — a cryptographic construction that proves that a certain amount of time has elapsed, in a way that anyone can verify quickly even though producing it requires sequential computation.

How it works:

  1. A validator runs a continuous SHA-256 hash chain: hash(hash(hash(...)))
  2. Each output is the input to the next hash — it is impossible to skip ahead without computing every step
  3. Timestamps and transaction hashes are periodically inserted into the chain: hash(previous_hash + transaction)
  4. The resulting sequence is a cryptographic proof that transactions occurred in a specific order, at specific intervals

Any observer can verify this sequence in parallel (GPU-friendly), but generating it requires sequential computation. This asymmetry creates a trustworthy clock.

Analogy: Like a punch card stamping time in a factory — you can’t fake that a task was done hours before the punch by going back and stamping earlier times, because the stamps are ordered and observed by everyone.


Eight Technical Innovations

The whitepaper presents PoH as one of eight complementary systems:

Innovation Purpose
Proof of History Cryptographic clock; orders transactions without consensus round-trips
Tower BFT PBFT-style consensus optimized for PoH’s pre-established time ordering
Turbine Block propagation protocol; breaks blocks into small packets transmitted to subsets of validators (like BitTorrent)
Gulf Stream Mempool-less transaction forwarding; clients send transactions directly to the expected next leader
Sealevel Parallel smart contract runtime; executes non-overlapping transactions simultaneously across GPUs and SSDs
Pipelining Assigns validation stages to separate hardware units for continuous processing
Cloudbreak Horizontally-scaled accounts database optimized for concurrent reads/writes
Archivers Distributed ledger storage; validators offload historical data to an archiver network

These eight systems work in concert to eliminate every bottleneck individually.


Tower BFT

Traditional BFT (Byzantine Fault Tolerant) consensus requires multiple rounds of all-to-all messaging. With PoH providing a pre-established ordering, Tower BFT can skip most of those rounds — validators already agree on what time it is, so they only need to vote once per block rather than exchange messages to establish ordering.

Votes are also stake-weighted and subject to lockouts: if a validator votes for block A, they cannot vote for a conflicting fork for an exponentially increasing number of slots. This means forks resolve quickly, and validators who try to hedge by voting for multiple forks are eventually penalized.


Sections of the Whitepaper

  1. Introduction — The throughput problem; why existing solutions trade off something
  2. Network Design — Architecture overview; the PoH generator, validator nodes, archiver nodes
  3. Proof of History — VDF construction; SHA-256 hash chain; transaction ordering
  4. Proof of Stake Consensus via Tower BFT — Stake-weighted votes, lockouts, fork resolution
  5. Optimistic Concurrency Control via Gulf Stream — Pre-confirmation, pipelined leaders
  6. High-Performance Memory — Cloudbreak; structured account storage
  7. Replication — How storage is distributed to archiver nodes; proof of replication
  8. Data Availability — Erasure coding for block distribution (Turbine)
  9. Smart Contract Runtime (Sealevel) — Parallel execution of non-conflicting programs
  10. Performance — Theoretical throughput calculations

Key Technical Specifications (from whitepaper)

  • SHA-256 VDF generating ~160 million hashes/second on modern hardware (2017 baseline)
  • Theoretical capacity: 710,000 tps with 1 Gbps network
  • Practical estimate in paper: 50,000–100,000 tps
  • Block time target: ~400ms slots (later implemented as ~400ms)

Reality Check: Whitepaper vs. Actual Performance

The whitepaper’s theoretical numbers require top-tier dedicated hardware. Real-world Solana has:

  • Achieved roughly 3,000–4,000 sustained tps in normal conditions (2023–2024)
  • Suffered multiple network outages (September 2021, May 2022, etc.) often from spam transactions overwhelming the validator set
  • Demonstrated that hardware requirements for validators (high-RAM, high-bandwidth machines) do create centralization pressure — as the paper’s critics predicted

That said, Solana remains the highest-throughput major Layer 1 blockchain in production as of 2026.


Legacy

The Proof of History concept influenced thinking about time in distributed systems broadly. It popularized the idea that a blockchain’s throughput is limited more by its consensus communication overhead than by raw compute capacity. Later projects (Sui, Aptos) tackled similar problems via different means (object-centric storage, parallel execution models), often explicitly citing Solana’s approach as inspiration.


Social Media Sentiment

Last updated: 2026-04

Solana’s whitepaper and technical claims are divisive. SOL supporters (“SOL heads”) point to real-world throughput metrics — Solana consistently processes more daily transactions than any other major L1, including Ethereum — and argue the engineering team successfully delivered on the whitepaper promises. Critics focus on the network outages, high validator hardware requirements, and VC concentration of initial SOL supply as signs that Solana sacrificed decentralization for speed. The “Solana is a centralized piece of garbage” vs. “Solana is the only chain that actually works at scale” debate is perennial on CT.


Related Terms


Research

  • Yakovenko, A. (2017). Solana: A new architecture for a high performance blockchain v0.8.13. solana.com.

— Primary source. Dense but readable; PoH section is essential for understanding Solana’s core innovation.

  • Boneh, D., Bonneau, J., Bünz, B., & Fisch, B. (2018). Verifiable Delay Functions. CRYPTO 2018.

— Formal academic treatment of VDFs; situates PoH within the broader cryptographic literature.

  • Kim, S. K., et al. (2021). Analyzing the Performance of Solana. IEEE Blockchain 2021.

— Empirical analysis of Solana’s real-world throughput vs. whitepaper claims.