NIP-57 connects Nostr social actions with Lightning payments through zap requests and zap receipts.
What it standardizes
It allows clients to display payments attached to posts or profiles. This turns support, tipping, rewards, spam deterrence and value-for-value signals into social objects.
- Protocol layer. NIP-57 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 client creates a zap request, sends it through an LNURL payment flow and receives a zap receipt event that can be displayed by clients.
- 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 zaps for creator support, fan proof, campaign signals, venue attention and eventually demand scoring around content and award activity.
- 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
Do not confuse zaps with a full business model. Users still need wallet setup, pricing, legal clarity, refunds where relevant and consumer-safe checkout flows.
- 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.