highperfocused/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2025-03-29 03:02:07 +01:00
Code Issues Packages Projects Releases Wiki Activity

zaps: more client behavior notes

Browse Source
This commit is contained in:
William Casarin 2023-02-05 12:02:02 -08:00
parent 681282a401
commit 3b8f89b744
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
57.md
View File

@ -133,10 +133,11 @@ A reference implementation for the zapper is here: [zapper][zapper]
Clients MAY fetch zap notes on posts and profiles:
`{"kinds": [9735], "#p": [...]}`
`{"kinds": [9735], "#e": [...]}`
To authorize these notes, clients MUST fetch the `nostrPubkey` from the users configured lightning address or lnurl and ensure that the zaps to their posts were created by this pubkey. If clients don't do this, anyone could forge unauthorized zaps.
Once authorized, clients MAY tally zaps on posts, and list them on profiles. 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.
## Future Work