A reading room for Solana, run from Seoul

Read the chain slowly, understand it properly

Mentisvertex keeps a curated room of Solana writing — patient guides, a glossary of terms, and long-form deep dives — and pairs it with curators who walk the shelves with you.

See the Guided Reading Path Browse the collection
A reader's desk before and after a guided reading path: a pile of printed threads replaced by a single annotated bundle
One reader's desk, week one and week four of the same path.

Two voices at the same desk

Week one. “I had forty tabs open — a validator thread, three Discord pins, a whitepaper I couldn't finish. Everyone online sounded certain, and I couldn't tell a slot from a block. I thought the problem was me.”

Week four. “The curators closed thirty-seven of those tabs and gave me six readings in an order that made sense. Last Tuesday I explained account rent to my team without looking anything up. The problem was never me. It was the pile.”

That gap — between the pile and the path — is the whole reason this room exists.

A single reading lamp over an open Solana guide in a dark library room
The reading room after closing time, lamp left on for the late cohort.

The Guided Reading Path

Our flagship program for developers, analysts, and founders who need Solana to make sense end to end.

Over four weeks, a curator assembles a personal reading bundle from our shelves — core concepts first, then accounts and programs, then the parts of the ecosystem your work actually touches. Each week ends with a small group call where the hard paragraphs get read aloud and argued over.

You keep the annotated bundle, the margin notes, and a map of what to read next. Four weeks, one cohort of eight, ₩180,000 per reader.

Read the full program outline

Who keeps the room

Mentisvertex is run by three curators in Mapo-gu, Seoul. Ha-eun spent six years documenting validator operations and still reads every governance proposal before breakfast. Jun-ho writes the long guides; he came from technical publishing and insists every article survive being read aloud. Mira keeps the glossary — she interviews engineers, then argues with them until a definition fits on an index card.

None of us trades on what we publish. The room holds no token positions, takes no placement fees from projects, and marks every piece of writing with the date it was last re-read. When a guide goes stale, it comes off the shelf until someone revises it.

We answer reader mail ourselves, usually within two working days, in English or Korean.

From the reading notes

Short pieces the curators write between shelves — what we re-read this month and why it held up.

Index cards and annotated printouts spread under a desk lamp

Reading note · 6 min

Why accounts confuse everyone in week one

The account model is the first wall most readers hit. A note on the three metaphors that help — and the one popular metaphor that quietly misleads.

Find it in the collection

Reading note · 9 min

Re-reading the consensus chapter, a year later

We shelved our Tower BFT explainer for a month and rewrote half of it. What changed, what stayed, and what we still simplify on purpose.

Find it in the collection

Reading note · 4 min

Six terms readers mix up before any path begins

Slot and block. Program and account. Cluster and network. The glossary desk keeps a tally of the usual collisions.

Find it in the collection
Two readers comparing annotated guides at a library table at night

What readers leave with

Named outcomes from recent cohorts and commissions — told by the readers themselves.

“I joined the spring path before a hackathon in Busan. I didn't win, but I shipped a working program and — more important — I could explain to the judges exactly why it failed the first three times. That explanation came straight out of the week-two bundle.”

Daniel R., backend developer, Guided Reading Path cohort of March

“We commissioned a deep-dive briefing before integrating Solana payments. The report was slower than we hoped — three weeks instead of two — but it flagged a fee edge case our own research had missed entirely. Finance read it without a single follow-up question.”

Soo-min K., product lead at a Seoul commerce startup, Deep-Dive Briefing

How a path actually proceeds

The same five steps for every reader, whether you join a cohort or commission a briefing.

  1. 1

    The intake letter

    You write to us about what you're trying to understand and why. Two paragraphs is plenty; we reply with honest questions, not a sales call.

  2. 2

    The shelf pull

    A curator pulls six to ten readings from the collection and orders them for your starting point — not for a generic beginner.

  3. 3

    Reading weeks

    You read at your own pace with margin notes from us. Stuck paragraphs go to the glossary desk and come back within two days.

  4. 4

    The table call

    Each week ends around a small group call — eight readers at most — where the hardest page gets read aloud and taken apart together.

  5. 5

    The next-shelf map

    You leave with an annotated bundle and a written map of what to read after us, including the shelves we don't stock.

A curator's worktable with numbered reading bundles tied in string
Bundles for the current cohort, numbered in pull order.

The door is open most evenings

Write to the curators about what you're trying to learn. We'll tell you honestly whether a path, a briefing, or a single afternoon in the glossary fits best.

Write to the curators