Understanding Proof of History Without the Jargon
Proof of History (PoH) is the term most likely to send new Solana readers down a rabbit hole of clock metaphors. This article states what PoH actually does in the validator pipeline, without claiming it replaces consensus or acts as a wall-clock synchronized across the planet.
What problem it addresses
Validators must agree on the order of transactions. Traditional approaches run consensus on batches of transactions, which can be slow when the batch is large. PoH generates a continuous sequence of hashes — each hash incorporates the previous one — creating a verifiable record that time has passed and events were ordered in a specific sequence before validators vote.
What it is not
- Not a replacement for Proof of Stake consensus — Tower BFT still finalizes blocks
- Not a synchronized atomic clock across data centers
- Not a guarantee of transaction fairness by itself — fee markets and scheduling policies handle that separately
How to read PoH in release notes
When client updates mention PoH tick duration or hash rate changes, they are discussing how quickly the sequence generator produces entries under load. Slower ticks can affect how many transactions fit in a slot, which is why performance discussions often cross-reference PoH settings and compute budget limits together.
Common workshop misreadings
We frequently hear "PoH proves when a transaction happened in real time." More precisely, it proves relative ordering within the sequence before consensus stamps the block. Real-world timestamps in block explorers come from validator wall clocks and slot numbers, not from PoH alone.
Bring your confusing document to a Glossary Workshop and we will map every PoH reference to the spec section.