Journal · 12 February 2026
Read the accounts shelf before you open a program
Programs make more sense after you can point to an owner, a lamport balance, and the data field on a single account without looking down.
The page people skip
Most readers who write to the Geoje desk have already tried to deploy something. They can paste an instruction and watch it fail. What they cannot do is describe the account that was supposed to change: who owns it, how many lamports sit there, and whether the data is empty because the account was never created.
The accounts shelf is short on purpose. It holds the public layout of an account, the difference between the owner program and the address you hold, and the reason rent exists. We keep it in front of the programs shelf so a later error has a place to land.
A path that respects the order
When we write a personal learning path, week one is almost always accounts, even for someone who has shipped a small script. The exercise is modest: pick a public address from the library folder, write the owner, the lamport balance, and one sentence about the data length. No new program. No token mint.
Readers who insist on starting at programs usually return for a checkpoint. The mark-up is predictable. The program notes are detailed, and the account that stores state is described as “the thing the program uses.” That phrase is the signal to walk back a shelf.
What to do this week if you are between sittings
Choose one address. Write four lines: address, owner, lamports, data length. Then write what would make the account disappear. If the answer is only “someone closed it,” add who is allowed to sign that close. That second sentence is the whole point of the shelf.
Bring those four lines to a desk hour if you want them checked. A full path is unnecessary for this exercise, and the circle in October will assume you can already do it.