Ecosystem coverage
The library is sorted by where in the stack a subject sits, so a reader can walk from the protocol layer up to a program without losing the thread. Each area links to the entries and reading paths that sit under it.
How a leader is chosen for a slot, what a vote transaction contains, and how vote credits settle. Entries cover Proof of History as a sequencing device rather than a consensus mechanism, and the difference between a fork and a skipped slot.
Open the entries →Transaction structure, account tables, the order of execution, and what a "compute budget" actually buys. Worked examples point at signatures on mainnet that a reader can open and step through.
See the reading path →How the reference client is built, what a fork of the client changes, and how client diversity is measured. Release notes are summarised entry by entry when a release touches the shelf.
See the method →What an RPC node is responsible for, how a request is routed, and what a reader should expect from a public endpoint versus a private one. No endorsement of providers.
Read the questions →The stake program in detail: account layout, the separation of custodial and withdraw authority, and the lifecycle of a delegation from activation to deactivation. Worked examples point at real stake accounts.
Open the article →The original and the newer token programs side by side, what an account stores, and what a transfer actually changes on-chain. Entries are versioned against the program release they describe.
See the article style →