1 files changed, 1 insertions, 1 deletions
diff --git a/61.md b/61.md
index 78ec86c..fdcc2b6 100644
--- a/61.md
+++ b/61.md
@@ -119,4 +119,4 @@ All these checks can be done offline (as long as the observer has the receiver m
 ## Final Considerations
 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.
 2. Clients SHOULD normalize and deduplicate mint URLs as described in NIP-65.
-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.
+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.

diff --git a/61.md b/61.md index 78ec86c..fdcc2b6 100644 --- a/61.md +++ b/61.md
@@ -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.