NIP-58 describes badge definitions, badge awards, profile badge displays and badge sets.
What it standardizes
It gives Nostr a way to represent status, proof, membership, recognition or achievement without hard-coding badge logic into one app.
- Protocol layer. NIP-58 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
Badge issuers define badges and award them to public keys. Users can choose which awarded badges to display on profiles.
- 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
For Crays, this is status infrastructure. Creators and fans should not be described as selling badges. They can buy status badges where Crays offers them, or earn status through revenue, performance, contribution or community rules.
- 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
Badges need issuer trust, anti-spam controls and plain explanations. A badge is only meaningful if people understand who issued it and why.
- 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.