mirror of
https://github.com/nostr-protocol/nips.git
synced 2024-11-10 22:29:07 -05:00
rename to Zap Polls
This commit is contained in:
parent
cd8ed5ed7d
commit
4d22b2d41b
12
69.md
12
69.md
|
@ -1,8 +1,8 @@
|
||||||
# Poll event
|
# Zap Poll event
|
||||||
|
|
||||||
`draft` `optional` `author:toadlyBroodle`
|
`draft` `optional` `author:toadlyBroodle`
|
||||||
|
|
||||||
A poll note is a [nostr event](01.md) (kind `6969`) for conducting paid polls. A poll presents two or more voting options, which participants my vote on by sending regular [zap events](57.md) which include an additional `poll_option` vote tag. Polls may include multiple recipients which participants may choose from when zapping their votes. Polls may specify `value_maximum` and `value_minimum` satoshi valuations for determining which zaps are included in the tally. Polls may specify a `consensus_threshold` for assessing the state of consensus. Polls should specify a `closed_at` time, after which results be unblinded, closed to new votes, and the tally considered final.
|
A zap poll note is a [nostr event](01.md) (kind `6969`) for conducting paid polls—herein referred to simply as 'polls'. A poll presents two or more voting options, which participants my vote on by sending regular [zap events](57.md) which include an additional `poll_option` vote tag. Polls may include multiple recipients which participants may choose from when zapping their votes. Polls may specify `value_maximum` and `value_minimum` satoshi valuations for determining which zaps are included in the tally. Polls may specify a `consensus_threshold` for assessing the state of consensus. Polls should specify a `closed_at` time, after which results be unblinded, closed to new votes, and the tally considered final.
|
||||||
|
|
||||||
## Purpose
|
## Purpose
|
||||||
|
|
||||||
|
@ -18,7 +18,7 @@ The optional `consensus_threshold` is intended as a simple 'measuring bar', defi
|
||||||
|
|
||||||
A careful balancing of all poll attributes should enable pollers to conduct tailored polls that deliver meaningful and valuable outcomes.
|
A careful balancing of all poll attributes should enable pollers to conduct tailored polls that deliver meaningful and valuable outcomes.
|
||||||
|
|
||||||
## Poll format
|
## Zap poll format
|
||||||
|
|
||||||
A poll event:
|
A poll event:
|
||||||
* MUST specify 1 or more `p` tags, each including the same primary hosting relay
|
* MUST specify 1 or more `p` tags, each including the same primary hosting relay
|
||||||
|
@ -90,7 +90,7 @@ The zap request event (kind `9734`):
|
||||||
...
|
...
|
||||||
```
|
```
|
||||||
|
|
||||||
## Poll outcome
|
## Zap poll outcome
|
||||||
|
|
||||||
Polls results are tallied by summing the exact satoshi values from all eligible zaps for each `poll_option`. The total tally is the sum of all individual `poll_option` tallies, and `poll_option` results are calculated by their percentage of the total tally value.
|
Polls results are tallied by summing the exact satoshi values from all eligible zaps for each `poll_option`. The total tally is the sum of all individual `poll_option` tallies, and `poll_option` results are calculated by their percentage of the total tally value.
|
||||||
|
|
||||||
|
@ -119,6 +119,6 @@ Strict adherence to these requirements should enable a standardized means of qua
|
||||||
|
|
||||||
## TODO
|
## TODO
|
||||||
|
|
||||||
* refine NIP#69 based RFC feedback
|
* refine NIP#69 based on RFC feedback
|
||||||
* implement polls in 2 clients
|
* implement polls in 1 other client, besides Amethyst
|
||||||
* merge with nostr-protocol/NIPs
|
* merge with nostr-protocol/NIPs
|
||||||
|
|
Loading…
Reference in New Issue
Block a user