nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-12-22 16:35:52 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

Uncle Bob's Observations from the field

Browse Source
This commit is contained in:
Robert C. Martin 2023-05-20 07:53:39 -05:00
parent 1c916953c1
commit dd8631b81e
1 changed files with 3 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
57.md
View File

@ -181,3 +181,6 @@ When an event includes a `zap` tag, clients SHOULD calculate the lnurl pay reque
## Future Work ## Future Work
Zaps can be extended to be more private by encrypting `zap request` notes to the target user, but for simplicity it has been left out of this initial draft. Zaps can be extended to be more private by encrypting `zap request` notes to the target user, but for simplicity it has been left out of this initial draft.
## Observations from the field.
The 9735 Zap Receipt event contains a tag named `description`. The content of this tag appears to be the 9734 Zap Request event. The `pubkey` of the Zap Request identifies the sender of the zap. This is useful for clients that want to alert their users about who sent them zaps. However the `amount` tag of the Zap Request is not reliably included by the various wallet processors. Some do. Some don't. So clients may not be able to tell users the amount of the incoming zaps.