nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-11-10 06:09:08 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

added pubkey zap-tag

Browse Source
This commit is contained in:
Egge 2023-04-09 07:34:26 +02:00
parent dee546ed9e
commit d14602cea5
1 changed files with 9 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
57.md
View File

@ -168,7 +168,15 @@ A client can retrieve `zap receipts` on events and pubkeys using a NIP-01 filter
### Appendix G: `zap` tag on zapped event
When an event includes a `zap` tag, clients SHOULD calculate the lnurl pay request based on it's value instead of the profile's field. An optional third argument on the tag specifies the type of value, either `lud06` or `lud16`.
When an event includes a `zap` tag, clients SHOULD calculate the lnurl pay request endpoint based on it's value. A third argument on the tag specifies the type of value, either `pubkey`, `lud06` or `lud16`.
- `lud06` : Calculate lnurl pay request endpoint according to [lud06](https://github.com/lnurl/luds/blob/luds/06.md)
- `lud16` : Calculate lnurl pay request endpoint according to [lud16](https://github.com/lnurl/luds/blob/luds/16.md)
- `pubkey`: Find either a lud06 or lud16 property in this pubkeys metadata and calculate lnurl pay request endpoint accordingly
#### Client best-practices
When creating zap-able events clients SHOULD default to the pubkey-type, as this allows events to stay zap-able for a long time, even if users choose to change their wallet or provider.
```json
{