Contributors
Credentials matter less than habits. Here is how each contributor actually works — what they read first, how they verify a claim, and how their notes become the pieces on the shelf.
Every contributor keeps a public notebook of corrections — their own included. When a re-review finds that a piece has aged badly, the correction is logged and dated, and the piece is rewritten rather than patched quietly. Readers who follow a byline are following a process they can inspect.
Covers the runtime, the account model, and consensus. Reads client changelogs before breakfast and keeps a devnet sandbox permanently open. Her drafts begin as a list of claims, each with the experiment that would falsify it; the piece is finished only when every experiment has been run twice.
Beat: runtime internals, transaction lifecycle, fee markets.
Runs a small validator and writes the economics shelf. His working notes are spreadsheets of real epoch data, and his rule is that no number appears in a piece unless it can be reproduced from public chain data by a reader with an afternoon to spare.
Beat: staking, issuance, commission, operator costs.
Owns the plain-language pass and the glossary. She reads every draft aloud, cuts any sentence that needs a second pass, and keeps definitions under sixty words with one concrete example each. If a term appears on two pages with two meanings, she is the person who notices.
Beat: terminology, readability, cross-linking between shelves.
Writes the step-by-step guides and maintains the code snippets. Every snippet is short, annotated line by line, and tested against public devnet endpoints the week the guide is reviewed. If a client update breaks an example, his re-review queue is where it surfaces first.
Beat: client SDKs, devnet workflows, program deployment.
Spotted an error, or want to suggest a question the shelves should answer? The contributors read reader mail together once a week.