"The account-model guide finally made rent and owner fields click. I now explain them to new hires instead of pointing them at the docs."
Worked through the accounts guide over two evenings.
A reading room for Solana
Slow reading for people who want to understand Solana, not skim it.
Mindkeystone is a small library of long-form guides, a working glossary, and ecosystem deep dives. We write the explanations we wished existed when we were learning \u2014 patient, footnoted, and tested against the chain.
Reader stories
What readers took away from the shelves
Notes from readers who worked through a guide or the study program. Names shortened at their request; the work is theirs.
"I shipped a small program after the study program. The sessions on transactions and compute budget were the part I'd been missing for a year."
Completed the six-week guided program.
"The ecosystem deep dive on stake accounts changed how I read validator disclosures. I keep the glossary open while I work."
Reads the deep dives; subscribes to the reading list.
"Some entries assume more than I knew. The glossary filled the gaps, and the journal pieces are short enough to finish at lunch."
A mild reservation, kept in their words.
How the reading is made
Six steps from a blank page to a guide on the shelf
Every piece on the shelves follows the same path, so the reading stays consistent even as the topics move.
01
Choose a gap
We pick a topic readers ask about but that no current guide explains patiently.
02
Read the source
We read the relevant Solana source, RPC output, and reference docs before writing a line.
03
Draft long
A first draft runs long on purpose, with diagrams and footnotes, then is cut for clarity.
04
Test on chain
Every claim about behavior is checked against a live or local validator before it ships.
05
Glossary pass
Terms used in the piece are added to the glossary with cross-references to older entries.
06
Reader review
Two readers work through the draft cold and mark where they stalled; we fix those spots.
Who tends the shelves
The people who write and check the reading
A small group of researchers and writers in Seoul, each minding a part of the library.
Haneul Yoo
Writes the consensus and runtime deep dives. Previously taught distributed systems at a university in Seoul.
So-yeong Baek
Keeps the terminology glossary consistent and cross-referenced. Trained as a translator, allergic to jargon.
Jihoon Oh
Writes the program and account guides. Ships small Solana programs to test every claim before it reaches a reader.
Eunji Kang
Runs the guided study program and answers reader questions. Holds office hours twice a week for enrolled readers.
From the editor's desk
Why we keep a glossary instead of a glossary page
Most blockchain glossaries are a single page of one-line definitions, written once and forgotten. We started that way too, and stopped, because a definition without context misleads more than it helps. When a reader looks up "rent," they are not really asking what the word means \u2014 they are asking why their account was emptied, whether it will happen again, and what to do about it.
So our glossary is not a page. It is a growing set of entries, each one a short essay that points back to the guide where the term is used in practice. An entry on "compute budget" links to the guide on transaction costs. An entry on "vote account" links to the deep dive on staking. The definitions are written last, after the surrounding reading exists, so the words have somewhere to live.
This is slower. It means we publish fewer terms than a marketing page would. It also means a reader who follows a link from the glossary lands on something that actually explains the thing, instead of a circular definition that uses the word to define itself. We would rather have three hundred terms that hold up than three thousand that do not, and the readers who write to us seem to agree.
If you find a term we have not written yet, that is not an oversight \u2014 it is a gap we have not finished filling. Tell us, and we will move it up the queue.
Flagship offer
The guided study program
For readers who want to move from browsing to building. Six weeks of structured reading, weekly one-hour sessions with a guide, and a small project you finish and ship.
- A reading path picked from the shelves to match what you already know
- Six weekly one-hour video sessions with a study guide
- Written answers to questions between sessions, within two working days
- A small Solana program or audit you finish and keep
- Permanent access to the current library and glossary
From \u20a9490,000 for the six-week program
Request a place Read the full brief
On the shelves now
A few pieces from the library
Guides, glossary entries, and deep dives currently available to read.
Reading the account model
What an account really holds, why rent exists, and how owner fields govern programs.
Open the guide \u2192Proof of history, plainly
A primer on the clock that orders events before consensus, without the hype.
Open the dive \u2192Token extensions
The new token interface, its default extensions, and what each one actually changes.
Open the entry \u2192What the library covers
The subject areas we tend and the ones we are adding next.
See the areas \u2192Send us a note about what you want to understand.
Tell us where you are stuck or what you are building. We will reply with the right guide from the shelves, or a place in the next study program.
Write to the library