mirror of
https://github.com/nostr-protocol/nips.git
synced 2025-01-31 10:31:34 +00:00
Zapraiser
This commit is contained in:
parent
3f11c00fb9
commit
9bc2d17a0f
14
57.md
14
57.md
@ -183,6 +183,20 @@ When an event includes one or more `zap` tags, clients wishing to zap it SHOULD
|
|||||||
|
|
||||||
Clients MAY display the zap split configuration in the note.
|
Clients MAY display the zap split configuration in the note.
|
||||||
|
|
||||||
|
### Appendix H: `zapraiser` tag on other events
|
||||||
|
|
||||||
|
Any event can include a `zapraiser` tag with the tag's value equal to the total amount of sats the author wishes to fundraise from zaps to its event.
|
||||||
|
|
||||||
|
```jsonc
|
||||||
|
{
|
||||||
|
"tags": [
|
||||||
|
[ "zapraiser", "1000" ], // 1000 sats
|
||||||
|
]
|
||||||
|
}
|
||||||
|
```
|
||||||
|
|
||||||
|
Clients MAY display fundraising information in any way they see fit.
|
||||||
|
|
||||||
## 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.
|
||||||
|
Loading…
Reference in New Issue
Block a user