
How to read a Solana account
Start with the owner, the data length, and the rent exemption threshold. Then look at the discriminator, the program that can mutate it, and the signer relationships.
Read the note
A quiet research library for developers, validators, and analysts who want to understand the network from its ledger upward.
Protocol analyst
Minjun runs validator operations on mainnet-beta and devnet. Hana translates program mechanics into plain language. Together they trace transactions, compare cluster behavior, and prepare reading maps for every briefing.
No account is too small to inspect: rent, data length, owner program, signer seeds, and compute budget are all fair game.
Work begins in a shared online reading room. We send a private link, a curated reading map, and a glossary companion 48 hours before the call.
Calls are held over video during Seoul business hours, with notes and follow-up sent by email. If you are in Seoul, we can meet at the Seongsu study space.
Every session is shaped around your actual question: a failing transaction, an unfamiliar account pattern, or a design choice between Token and Token-2022.

Solana is more than a chain. It is a ledger, a runtime, and a gossip network layered together. Proof-of-history gives every event a verifiable order before consensus even starts. Accounts pay rent, carry data, and keep code separate from state. Programs are stateless bytecode that read and write accounts according to strict rules.
A transaction on Solana is a declaration: which accounts to touch, which instructions to run, who pays for compute, and how many signatures are required. If any piece is misunderstood, the result is a confusing error or an expensive bug.

Our deep dives follow concrete threads: how Turbine propagates blocks, how RPC nodes answer getProgramAccounts, how stake-weighted quality of service shapes leader scheduling, and how Token-2022 extensions change account layout. We ground every explanation in the source material so you can verify it yourself.
The best Solana builders we know read slowly first. This library is for that kind of reading.

Start with the owner, the data length, and the rent exemption threshold. Then look at the discriminator, the program that can mutate it, and the signer relationships.
Read the noteCommissions, warm-up epochs, stake accounts, and quality of service rewards. A guide for treasury analysts who want to compare validators without trusting marketing copy.
See all notesA one-to-one session for anyone who needs Solana explained on their own terms.
Starting at ₩220,000 for a single 60-minute session. Multi-session retainers and team sessions are quoted after a short scope review.
Request a briefing

I came in confused about rent and account ownership. The reading map alone saved me two weeks of guessing.
Jisoo Kim, smart-contract developer
The staking session helped me compare commission structures without the hype. I still think one section could have been shorter, but the follow-up notes made it stick.
Minho Lee, treasury analyst
We used the briefing to clarify why our transactions failed during a priority-fee spike. The team answered with actual block-explorer traces.
Yuna Seo, protocol engineer

Send a short note about what you are trying to understand. We reply within one business day with a scope and a time.
Request a briefing