Articles
Focused essays on single questions: how rent is calculated, what a recent protocol change actually altered, why a familiar claim is wrong.
An independent study library
No price talk, no hot takes. Every article, guide, glossary entry, and long-form study on these shelves is sourced, versioned, and written to be sat with — not scrolled past.
The old way. A question about how accounts work turns into a forum thread from 2021, a thread of posts arguing about fees, three half-finished documentation pages, and a video that assumes you already know the answer. An hour later you have forty tabs and no footing.
The reading-room way. You open one piece that names its sources, states the reader level it assumes, and shows the date it was last checked against the live network. Unfamiliar terms link straight to a short glossary definition. You finish with a model of the system you can actually defend.
Solana is usually introduced through its speed claims, which teaches a reader almost nothing. The shelves here start from the parts that never make headlines: an account model where programs and data live in separate accounts, a runtime that can execute transactions in parallel because each one declares the accounts it will touch, and a consensus pipeline that orders events before they are executed.
Once those three ideas are in place, the rest of the map becomes legible. Rent stops being a strange fee and becomes a storage deposit. Priority fees stop being a mystery and become a market for ordering. Validator economics stop being a black box and become a set of incentives you can trace from issuance to commission.
This is the order the library teaches in: mechanics first, vocabulary second, applications last. It is slower than a hype cycle and faster than a whitepaper, and it is the only order we have found that survives contact with the real network.
Four kinds of material, one standard of care. Everything shows its reader level, its sources, and the date it was last reviewed.
Focused essays on single questions: how rent is calculated, what a recent protocol change actually altered, why a familiar claim is wrong.
Hands-on walkthroughs that run against public devnet endpoints, with short code snippets annotated line by line.
Definitions under sixty words, each with one concrete example, linked inline the first time a term appears anywhere on the site.
Diagram-led, long-form profiles of how real protocols, validator economics, and tooling behave in practice — the anchor pieces of the room.
A library that cannot be trusted is worse than no library. Each piece on the shelf passes through the same five-stage editorial pipeline, and each carries the date of its most recent pass.
We choose questions readers actually get stuck on — from reader mail, contributor field notes, and changes shipping in validator clients — not whatever is trending this week.
Primary sources only: the protocol's own documentation, client source code, governance records, and reproducible devnet experiments. Every claim in the draft carries a citation.
A second contributor who did not write the piece re-runs every command, checks every number against the live network, and argues with the framing until it holds.
The draft is rewritten for a reader who is new to this chain but not to careful reading: direct sentences, no idioms, glossary links on first use of any term.
Each piece re-enters the pipeline on a fixed cycle. When the network changes, the shelf changes — and the last-reviewed date moves with it.
For readers who want structure rather than a search box. Over six weeks you move through a fixed sequence of articles, guides, and studies — from the account model to validator economics — with a small cohort and a weekly live discussion led by the contributor who wrote the material.
272
Published articles and guides on the shelf
386
Glossary entries, each under sixty words
45
Days in the average re-review cycle
Start with the opening shelf — three pieces that give you the account model, the runtime, and the vocabulary to keep going on your own.