Sign in

Where Solana came from

Suggest an edit

Solana started from the idea that the order of events can be proven with a hash chain, so validators do not have to negotiate it. In September 2021 a flood of bot transactions halted the network, and the way it accepts and prices transactions changed afterwards.

A hash chain proves the order of events

In November 2017 Anatoly Yakovenko published the whitepaper that introduced Proof of History. His observation was that the slow part of a blockchain is the back-and-forth between validators trying to agree on the order of events, and that a clock everyone can verify would remove it.

Proof of History is that clock. A single hash function is applied to its own output, over and over, producing a chain of outputs where each one can only have been generated after the previous one. Anyone can verify the chain, and nobody can fake the gap between two points in it. Transactions reference positions in this chain and inherit a strict, verifiable ordering.

Validators still vote on which version of history is the canonical one. That consensus mechanism is called Tower BFT, and it runs on top of the clock, so the votes do not have to settle when each event happened. As a developer you meet the clock in the recent_blockhash field of every transaction, which is a recent point on this chain. The Proof of History lesson covers how the chain is produced and verified.

The September 2021 outage changed how transactions are accepted and priced

Mainnet Beta launched on March 16, 2020. On September 14, 2021, Grape Protocol sold its token on the Raydium exchange (an initial DEX offering), and bots flooded the network with transactions to capture as many token allocations as possible. The network halted, and it took about 17 hours and a coordinated restart by the validators to bring it back.

The network at the time had no way to tell an urgent transaction from one of a million spammed copies. After this outage and the transaction floods of 2022, it changed both how validators accept incoming transactions and how a transaction pays for a place in a block. Outages, lessons, and resilience goes through each incident and the fix that followed.

The change you will use directly is the priority fee. A transaction can pay extra per unit of computation, and when more transactions arrive than fit in a block, the leader (the validator producing the current block) takes the higher bids first. Transaction fees and compute units shows how to set it.