nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-09-20 23:05:49 -04:00
Code Issues Actions Packages Projects Releases Wiki Activity

rename poll->zap poll

Browse Source
This commit is contained in:
toadlyBroodle 2023-04-29 13:33:22 +09:00
parent df236f4ab9
commit 5429dce3d5
3 changed files with 3 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
57.md
View File

@ -181,7 +181,7 @@ Example zap receipt:
* The zap note MAY contain a `preimage` to match against the payment hash of the bolt11 invoice. This isn't really a payment proof, there is no real way to prove that the invoice is real or has been paid. You are trusting the author of the zap note for the legitimacy of the payment.
* The zap note MAY contain a `poll_option` tag used for voting on [poll events](69.md).
* The zap note MAY contain a `poll_option` tag used for voting on [zap poll events](69.md).
The zap note is not a proof of payment, all it proves is that some nostr user fetched an invoice. The existence of the zap note implies the invoice as paid, but it could be a lie given a rogue implementation.

6
69.md
View File

@ -118,9 +118,3 @@ Additionally, a tallying client:
* MAY display the counts of zap events received for each option, along with other poll statistics
Strict adherence to these requirements should enable a standardized means of quantitatively assessing the distribution of opinion regarding a poll's content amongst poll participants, determining a winning outcome, and possibly achieving consensus. However, until this protocol is further tested, refined, and proven robust, polls should probably not be considered authoritative nor binding.
## TODO
* refine NIP#69 based on RFC feedback
* implement polls in 1 other client, besides Amethyst
* merge with nostr-protocol/NIPs

4
README.md
View File

@ -58,7 +58,7 @@ They exist to document what may be implemented by [Nostr](https://github.com/fia
- [NIP-57: Lightning Zaps](57.md)
- [NIP-58: Badges](58.md)
- [NIP-65: Relay List Metadata](65.md)
- [NIP-69: Polls](69.md)
- [NIP-69: Zap Polls](69.md)
- [NIP-78: Application-specific data](78.md)
- [NIP-94: File Metadata](94.md)
@ -82,7 +82,7 @@ They exist to document what may be implemented by [Nostr](https://github.com/fia
| `44` | Channel Mute User | [28](28.md) |
| `1063` | File Metadata | [94](94.md) |
| `1984` | Reporting | [56](56.md) |
| `6969` | Poll | [69](69.md) |
| `6969` | Zap Poll | [69](69.md) |
| `9734` | Zap Request | [57](57.md) |
| `9735` | Zap | [57](57.md) |
| `10000` | Mute List | [51](51.md) |