NIP-23 defines addressable long-form article events, often used for Nostr-native writing.
What it standardizes
It lets clients publish and read article-like content in a standard format without locking the author into one blogging platform.
- Protocol layer. NIP-23 is not a consumer product. It is a convention that clients, relays or adjacent services may choose to support.
- Interoperability. The value is not that every app looks the same. The value is that different apps can understand the same signed data.
- Optionality. NIPs are implementation possibilities. Builders should implement the pieces that serve their product, security model and user journey.
Implementation notes
The content is Markdown-oriented and should be structured for readability across clients. Social clients do not need to implement it, but publishing clients can.
- Client responsibility. Clients need to explain the feature clearly because the user sees an experience, not a spec.
- Relay responsibility. Relays may support only the parts that fit their storage, moderation, authentication and business model.
- Indexing responsibility. Search, discovery and context often require extra indexers or opinionated clients on top of the raw protocol.
Crays relevance
Crays can use long-form content for creator posts, venue stories, Association updates, educational explainers and SEO-adjacent distribution.
- Crays.net. Profiles, creator pages and social proof need portable identity rather than a closed account table.
- Crays World. Real venues need local context, member state, reputation and payments that can survive app changes.
- DAO path. Future governance needs signed identity, membership context and auditable participation signals.
Risks and design discipline
Long-form UX needs drafts, editing, media handling, discovery and indexing. The NIP gives format, not a complete publishing product.
- Do not overpromise. A NIP gives a shared format. It does not magically solve onboarding, moderation, UX or custody.
- Keep the private key away. Any feature that increases private-key exposure increases the attack surface.
- Use plain language. Most users need outcomes: login, pay, publish, vote, prove status, access a venue.