From 90707d555b69ccb11933ad71a07cbac99df69b3e Mon Sep 17 00:00:00 2001 From: Pablo Fernandez Date: Wed, 17 Jul 2024 09:57:27 +0100 Subject: move over p2pk appendix --- 61.md | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) (limited to '61.md') diff --git a/61.md b/61.md index f219f11..2cf27d5 100644 --- a/61.md +++ b/61.md @@ -114,4 +114,14 @@ Events that redeem a nutzap SHOULD be published to the sender's [[NIP-65]] relay 2. Clients SHOULD normalize and deduplicate mint URLs as described in NIP-65. -3. A nut zap 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. \ No newline at end of file +3. A nut zap 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. + +## Appendix 1: Alternative P2PK pubkey +Sometimes clients might not have access to the user's private key (i.e. NIP-07, NIP-46 signing) and, as such, the private key to sign cashu spends might not be available, which would make spending the P2PK incoming nutzaps impossible. + +For this scenarios clients can: + +* add a `pubkey` tag to the `kind:10019` (indicating which pubkey senders should P2PK to) +* store the private key in the `kind:37375` event in the nip44-encrypted `content` field. + +This is to avoid depending on NIP-07/46 adaptations to sign cashu payloads. \ No newline at end of file -- cgit v1.2.3