Read a Transaction End to End
Learn to parse signatures, accounts, instructions, and compute limits from a single explorer link.
Solana Field Notes
A Quiet Place to Learn the Chain
Clear, hype-free explanations of consensus, programs, accounts, and transactions — written for developers who want to build with confidence.
Curated Paths & Primers
Programs & Accounts
See why Solana stores state in accounts and how programs own logic without holding data.
Proof of History in Plain Language
Understand how the ledger orders events before consensus votes ever take place.
Validator Economics
Explore stake-weighted rewards, leader rotation, and why finality feels fast on a busy network.
Inside the Ledger
At first glance a Solana transaction can look like a dense packet of bytes. Beneath the surface it is a set of instructions that borrow accounts, mutate state, and pay for compute. The ledger itself is a database of accounts, each one tagged with an owner program, a lamport balance, and a data layout.
Programs are compiled code. They do not store data; they point to accounts that store data. This separation changes how you design an application. Instead of sending a transaction to a contract that keeps your balance, you pass the account that holds your balance into the program for the duration of the call. The program checks ownership, signatures, and constraints, then updates the account and returns.
Signed transaction
→
Program
→
Account state
Accounts must also pay rent, a small deposit that keeps them alive. Rent is measured in lamports and can be waived when an account holds more than two years of the exemption threshold. State is not free, which pushes developers toward compact data layouts and careful account reuse.
Every transaction carries a recent blockhash, a list of signatures, and a list of instructions. The runtime processes instructions in order, each one declaring the accounts it needs and whether it intends to read or write. If any instruction fails, the entire transaction is rolled back, so partial state changes do not leak.
The Focused Reader Pass
The Focused Reader Pass is for teams and solo builders who need a curated path through the protocol rather than another scattered tutorial. It includes a private 45-minute reading session, a tailored article sequence selected from the archive, a one-page glossary quick-reference for the terms you encounter, and written follow-up notes with links to official documentation.
- Who it is for: developers, researchers, and product builders who are new to Solana and want precise, hype-free explanations they can apply immediately.
- What is included: one live session, a custom reading plan, a glossary reference, and follow-up notes.
- What is not included: code implementation, production security audits, or token-trading advice.
- Price: ₩120,000 per session, paid after the call by invoice.
- Next step: send your background and question through the contact form and we will propose a time within two business days.
Common Reader Questions
Do I need to own tokens to use the archive?
No. The articles and glossary are free to read. Only the private reading sessions are paid.
Are the guides written for beginners?
Yes. Each piece links technical terms to the glossary on first use and builds from first principles.
How often is the weekly dispatch sent?
Every Tuesday morning, Korea Standard Time. One field note, one glossary term, and one project observation.
Can I request a topic?
Yes. Use the contact form to suggest a mechanism, project, or transaction you would like explained.
Is the private session live or recorded?
It is a live video call. A short written summary is shared afterwards, but the call is not recorded by default.
Do you cover program security?
We explain common patterns and point to audit resources, but we do not perform security audits.
Can my team book a group session?
Yes, up to six people. Larger groups can arrange a custom workshop by email.
Where the Archive Lives
Lucid Pavilion is an online archive. There is no public reading desk to visit; the library lives on a fast static host with every route delivered as a real page. Articles are drafted in Seoul and edited against the latest validator documentation and main-net examples, then published as field notes you can read on any device.
Each reference links back to the official Solana documentation, the source code of the programs we discuss, and a public explorer for the transactions we walk through. That way you can verify the details yourself rather than trust a single summary.
For correspondence, our editorial office is at 4F Lucid Pavilion, 27 Seongsu-ro 7-gil, Seongdong-gu, Seoul 04768, Republic of Korea. Reach us by phone at +82 2 3456 7890 or by email at [email protected].
Open One Field Note
Every week we publish one focused field note. Add it to your reading list or reply with a question. The first dispatch is free.
Subscribe to the dispatch