upleb.uk

Public git repos — served from a NIP-34 GRASP relay at git.upleb.uk

summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorjiftechnify <jiftech.stlfy@gmail.com>2023-05-14 11:55:07 +0900
committerjiftechnify <jiftech.stlfy@gmail.com>2023-05-14 11:55:07 +0900
commit64ac0710dea1af432051ef70698979bff106b9c2 (patch)
treefa3133c5ad61697c3c38803076d2df397dd66ff1
parent26194822005836a8ce690009fc636e0fe71802e6 (diff)
zap note -> zap receipt
-rw-r--r--57.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/57.md b/57.md
index 17042ea..538d727 100644
--- a/57.md
+++ b/57.md
@@ -20,7 +20,7 @@ Having lightning receipts on nostr allows clients to display lightning payments
206. If the request is valid, the server should fetch a description hash invoice where the description is this note and this note only. No additional lnurl metadata is included in the description. This will be returned in the response according to [LUD06](https://github.com/lnurl/luds/blob/luds/06.md). 206. If the request is valid, the server should fetch a description hash invoice where the description is this note and this note only. No additional lnurl metadata is included in the description. This will be returned in the response according to [LUD06](https://github.com/lnurl/luds/blob/luds/06.md).
217. On receiving the invoice, the client MAY pay it or pass it to an app that can pay the invoice. 217. On receiving the invoice, the client MAY pay it or pass it to an app that can pay the invoice.
228. Once the invoice is paid, the recipient's lnurl server MUST generate a `zap receipt` as described in Appendix E, and publish it to the `relays` specified in the `zap request`. 228. Once the invoice is paid, the recipient's lnurl server MUST generate a `zap receipt` as described in Appendix E, and publish it to the `relays` specified in the `zap request`.
239. Clients MAY fetch zap notes on posts and profiles, but MUST authorize their validity as described in Appendix F. If the zap request note contains a non-empty `content`, it may display a zap comment. Generally clients should show users the `zap request` note, and use the `zap note` to show "zap authorized by ..." but this is optional. 239. Clients MAY fetch `zap receipt`s on posts and profiles, but MUST authorize their validity as described in Appendix F. If the zap request note contains a non-empty `content`, it may display a zap comment. Generally clients should show users the `zap request` note, and use the `zap receipt` to show "zap authorized by ..." but this is optional.
24 24
25## Reference and examples 25## Reference and examples
26 26
@@ -108,7 +108,7 @@ When a client sends a zap request event to a server's lnurl-pay callback URL, th
1082. It MUST have tags 1082. It MUST have tags
1093. It MUST have only one `p` tag 1093. It MUST have only one `p` tag
1104. It MUST have 0 or 1 `e` tags 1104. It MUST have 0 or 1 `e` tags
1115. There should be a `relays` tag with the relays to send the `zap` note to. 1115. There should be a `relays` tag with the relays to send the `zap receipt` to.
1126. If there is an `amount` tag, it MUST be equal to the `amount` query parameter. 1126. If there is an `amount` tag, it MUST be equal to the `amount` query parameter.
1137. If there is an `a` tag, it MUST be a valid NIP-33 event coordinate 1137. If there is an `a` tag, it MUST be a valid NIP-33 event coordinate
114 114