Runtime and clients
Agave release notes and the feature-gate lists that travel with them. Each annotation separates “merged” from “active,” so an operator can see which epoch still has to pass.
Solana learning library · Jeongeup-si
A small library in North Jeolla. A reader sits with you for ninety minutes and walks one public change — from the release text to a binder you take home.
Agave release notes and the feature-gate lists that travel with them. Each annotation separates “merged” from “active,” so an operator can see which epoch still has to pass.
Token-program and Token-2022 tabs for transfer fees, metadata pointers, freeze authority, and the extensions a given program actually calls.
Compute-budget and priority-fee notes, filed beside the default flags readers ask about before they change a client setting.
SIMD texts currently in the Thursday circle, with a board list of words the draft itself never defines.
Seated briefing or scheduled call
Ninety minutes with a reader who walks one Solana change from the public note into a binder you keep.
You name the document. The desk sends a reading list the day before. You leave with margin notes and seven days of questions on those same pages.
A small evening circle that reads one Solana proposal or release aloud and stops on every undefined word.
A written note on one Solana change, prepared for your role and handed over as a booklet or a file.
A reserved hour at the open shelves with a librarian nearby for short questions about the binders.
Seong-min Park still keeps the epoch checklist from his briefing on the inside of a cabinet door in Gwangju. He also asked for the glossary the evening before, rather than the morning of the sitting. The desk now sends it with the reading list.
04
The first Thursday evening of the month, after the daytime desk has closed. Eight seats, one document, definitions before opinions.
1 October 2026 · 19:00–20:15
Reading a feature-gate list beside a client release