Shelves
The library is five shelves and a rule about order.
A personal learning path borrows from these five shelves. Readers walk them from accounts toward clusters unless an intake shows that an earlier shelf is already steady.
Accounts
The first shelf holds the public shape of an account: address, owner, lamports, and data. The glossary card for rent lives here, in the wooden box, because a balance that keeps an account alive is an account fact before it is a fee fact. Exercises ask you to write four lines about one public address from the library folder.
Minseo will not move a path off this shelf while the word “owner” still means “the person with the wallet.” The owner on this shelf is a program id. That distinction is the price of admission to everything later.
Transactions
Signatures, the list of instructions, the accounts each instruction names, and the recent blockhash. The October circle spends four Thursdays here. A path usually reaches this shelf in week three or four, after rent can be said aloud.
The useful exercise is a single transaction pulled apart on paper: who signed, which account was writable, and what the fee was in lamports. We keep a folder of expired blockhashes so readers can see a signature that no longer lands.
Programs
This shelf explains how an instruction is allowed to touch the accounts it lists. Readers who already write software still start from the account layout the program expects, then the instruction data, then a failure that names the wrong owner.
Paths that include this shelf give it at least two rows. A single week produces confident vocabulary and brittle exercises, which is the pattern we see at checkpoints.
Tokens
Mints, token accounts, and delegates. The shelf keeps returning to the same warning: a token balance is data inside an account, and that account has an owner program of its own. Readers who skip the accounts shelf describe a mint as if it were a wallet. Haru sends those notes back one shelf.
The token shelf is optional inside an eight-week path. When it is required for someone’s work, we usually recommend a second path rather than compressing programs and tokens into the closing fortnight.
Clusters
Devnet is the cluster we use for the first exercise. The sheet asks for a signature and a before-and-after of lamports and data length. Mainnet appears in conversation only when a reader can already explain the fee. Private keys are not written on any sheet in this aisle.
Junho files completed exercise sheets with the path booklet. A cluster afternoon with nothing written down does not count as a finished row.
Choosing where to begin
If you can explain an account, start the conversation at transactions. If you cannot, begin at accounts even if your job title says otherwise. The desk would rather hear that in the first letter than discover it at week four.