StartWalk in easy. No protocol fog.11 pages
PeopleMeet the builders, creators and scene.25 pages
RelaysSee where the network actually lives.50 pages
NIPsThe rules translated into real moves.267 pages
CraysWhere identity, venues and status get real.17 pages
LibraryEvery chapter, mapped without getting lost.724 pagesnostr-sdk gets its own Crays research page because the workbook does not treat it as background noise. It appears in Developer Stack, usually around Rust, and that means a reader should be able to find it without knowing which directory first mentioned it.
Why this belongs in the atlas
nostr-sdk sits in the developer stack research layer. The reader question is simple: What can builders use here to ship safer Nostr behavior faster without hiding important tradeoffs?
The workbook signal says: Rust crate. The Crays version keeps that signal, then turns it into a plain-language map point instead of another cold list entry.
- Route. Developer stack research
- Workbook area. Developer Stack
- Subcategory. Rust
- Importance. High
The Crays read
For Crays this is the tool bench. A library, SDK, command line tool or storage pattern matters when it lowers implementation risk for signers, relays, wallet flows, media, search or event handling.
The writing rule is the same as the rest of the archive: explain the thing like a sharp friend would explain it over coffee, but keep the facts traceable enough that builders can follow up.
Evidence trail
This derived page is connected to 1 audited source URL(s) and 2 workbook row signal(s). Open the source cards when you want the crawl status, checked subpages and raw research trail.