Kind 7376: Nutzap Redemption

Overview

A Nutzap Redemption event (Kind 7376) is created when a user successfully redeems or claims Cashu tokens received from a Nutzap. This event serves as a record that tokens have been claimed, preventing double-redemption attempts, and signals to the sender that their payment has been received and processed.

Specification

Property	Value
Kind Number	7376
Event Range	Regular
Defined in	NIP-61

Content Format

The content field contains NIP-44 encrypted data with metadata about the transaction.

Schema

{
  "content": "<nip-44-encrypted-data>"
}

The encrypted data contains:

[
  ["direction", "in"],  // "in" = received, "out" = sent
  ["amount", "<amount-value>"],
  ["e", "<7375-event-id>", "<relay-hint>", "created"] // new token event created
]

Tags

Tag Name	Description	Format	Required
e	Nutzap event that has been redeemed	["e", "<9321-event-id>", "<relay-hint>", "redeemed"]	Yes
p	Pubkey of the nutzap sender	["p", "<sender-pubkey>"]	Yes

Client Behavior

Clients SHOULD:

1. Create a Kind 7376 event when claiming tokens from a Nutzap
2. Tag the original Nutzap event (Kind 9321) with an e tag
3. Include a p tag with the pubkey of the Nutzap sender
4. Publish this event to the sender's NIP-65 "read" relays
5. Use this event as a marker when filtering for new Nutzaps to prevent processing already-redeemed tokens

Relay Behavior

Relays simply store and serve these events, with no special behavior required.

Use Cases

• Recording Nutzap token redemption history
• Preventing double-redemption of tokens
• Signaling to senders that their payment was received and processed
• Providing a transaction record for accounting purposes

Example

{
  "id": "a845c4c9fa6e58b8a150bc691c71fd658d5176b62fe0c626491326728e219c93",
  "pubkey": "e9fbced3a42dcf551486650cc752ab354347dd413b307484e4fd1818ab53f991",
  "created_at": 1683123789,
  "kind": 7376,
  "content": "8cI2MgJ2nSgpYsFNjmXQ3Wvg2+NYW7tjNVE75TYV8RM4OZvLUHf4kx+NSkvl5WJK+KnFxZZy+F0fPbWi0za3xWJkDNKs5F9iVyOk/NWfPhk2+0JT2aZB8Xe6Tv/0R2lPiRZMYG+eXDztsMnC1A+Vvj15jU5rHG3JgBMwUOUgAFG1kqgcVXNL2VJYELdNEwXYsMbvEVyG+tMX+KHI8tMvSUi9lcVoQm5VzaRXcZdUptPLbSPVubF8lTTh4ixPznq1OscQvXc7ULT9ayGTHhHTWqJLh7LhTuTN3NfyO+f5mUv2Klo=?iv=yjCT0gzTuYbOTFM3EbqxaA==",
  "tags": [
    ["e", "2bf3df19ebb911f6aa29a77aa8e20508d4d379211da4c6018fab23cef288a058", "wss://relay.example.com", "redeemed"],
    ["p", "4e1d0aa792db0e9d07ddf3870d8039de67bd922479302f0d988e0259534c894b"]
  ],
  "sig": "bc0243dcbc6d0cd029ba49b82ea4e29b6c33aee2bb3b8d48cd6af5d0f38fc7b44ea4a2152e9cc9bbd8c0dd85a192aa9b2c11c14e7805d46a2b11f4c8ae8aaefe"
}

References

• NIP-61: Nutzaps
• NIP-44: Encrypted Direct Messages
• NIP-65: Relay List Metadata

Related Kinds

• Kind 10019: Nutzap Informational - Configuration for receiving Nutzaps
• Kind 9321: Nutzap - Event to send a Nutzap

Notes

• Multiple Kind 9321 events can be tagged in the same Kind 7376 event
• Clients use this event type as a marker when filtering for new Nutzaps to process
• The event should be published to the sender's NIP-65 "read" relays to ensure they receive confirmation