diff options
| author | fiatjaf <fiatjaf@gmail.com> | 2025-02-03 22:34:16 -0300 |
|---|---|---|
| committer | fiatjaf <fiatjaf@gmail.com> | 2025-02-03 22:34:29 -0300 |
| commit | f9cba8846facbb8256cf308b0b60a760d5383fd4 (patch) | |
| tree | 0ccfa9eef2148d560ae1096078dbc491401c43e5 | |
| parent | 4ab75f0c3db12c9213b915e5e91041dc892b75ae (diff) | |
nip61: improve confusing final consideration.
| -rw-r--r-- | 61.md | 2 |
1 files changed, 1 insertions, 1 deletions
| @@ -119,4 +119,4 @@ All these checks can be done offline (as long as the observer has the receiver m | |||
| 119 | ## Final Considerations | 119 | ## Final Considerations |
| 120 | 1. Clients SHOULD guide their users to use NUT-11 (P2PK) and NUT-12 (DLEQ proofs) compatible-mints in their `kind:10019` event to avoid receiving nutzaps anyone can spend. | 120 | 1. Clients SHOULD guide their users to use NUT-11 (P2PK) and NUT-12 (DLEQ proofs) compatible-mints in their `kind:10019` event to avoid receiving nutzaps anyone can spend. |
| 121 | 2. Clients SHOULD normalize and deduplicate mint URLs as described in NIP-65. | 121 | 2. Clients SHOULD normalize and deduplicate mint URLs as described in NIP-65. |
| 122 | 3. A nutzap MUST be sent to a mint the recipient has listed in their `kind:10019` event or to the NIP-65 relays of the recipient, failure to do so may result in the recipient donating the tokens to the mint since the recipient might never see the event. | 122 | 3. A nutzap event MUST include proofs in one of the mints the recipient has listed in their `kind:10019` and published to the NIP-65 relays of the recipient, failure to do so may result in the recipient donating the tokens to the mint since the recipient might never see the event. |