NIP-47 describes how Nostr clients can interact with Lightning wallets through a standardized protocol.
What it standardizes
It lets apps request wallet operations without embedding every wallet directly into every client. This matters for zaps, payments, invoices and creator monetization.
- Protocol layer. NIP-47 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
A wallet service exposes capabilities through Nostr messages. Clients request operations and the wallet service responds according to permissions and limits.
- 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 connect content access, venue payments, zaps, fan actions and concierge flows to Lightning wallets without making every app a full wallet.
- 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
Wallet permissions need strict spending limits, clear approvals and safe defaults. Payment UX must be boringly reliable.
- 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.