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

spell check

Browse Source
This commit is contained in:
landonMutch 2023-03-03 13:27:12 +09:00 committed by GitHub
parent cdd6281b1e
commit 510b3d9491
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
69.md
View File

@ -20,7 +20,7 @@ A poll event:
```json
{
"id": <32-bytes lowercase hex-encoded sha256 of the the serialized event data>
"id": <32-bytes lowercase hex-encoded sha256 of the serialized event data>
"pubkey": <32-bytes lowercase hex-encoded public key of the event creator>,
"created_at": <unix timestamp in seconds>,
"kind": 6969,
@ -33,7 +33,7 @@ A poll event:
["n", <poll option n description string>],
],
["tally_method", "value"||"count"],
["consensus_threshold", <integar (0..100)>],
["consensus_threshold", <integer (0..100)>],
["closed_at", <unix timestamp in seconds>],
],
"content": <primary poll description string>,
@ -47,7 +47,7 @@ Poll options are voted on by sending [zap events](57.md) (to the original poll e
Zap vote events (kind `9734` and `9735`):
* MUST include exactly 1 `poll_option` tag
* MUST reference the vote option by its corresponding integar `n`, chosen from the original poll event's list of predefined `polling_options`
* MUST reference the vote option by its corresponding integer `n`, chosen from the original poll event's list of predefined `polling_options`
* MUST transmit the exact `poll_option` between kind `9734` and `9735`
```json
@ -74,8 +74,8 @@ A tallying client:
* MUST NOT count votes from anonymous users
* MUST treat the vote option with the most unique votes as the winning option
* when a `closed_at` time is specified, clients:
* MUST NOT include late votes recieved after `closed_at` time
* SHOULD publicly blind results until after a user's vote has been recieved
* MUST NOT include late votes received after `closed_at` time
* SHOULD publicly blind results until after a user's vote has been received
* SHOULD publicly display results after the `closed_at` time has passed
* when a `closed_at` time is NOT specified (is less than or equal to `created_at`), clients:
* SHOULD include all votes in tallies
@ -87,7 +87,7 @@ After the above rules are applied and clearly rendered, a tallying client:
* MUST indicate the state of consensus by displaying its value relative to the final percentage of the winning vote
* MAY display the secondary tally method result, for statistical purposes, along with other associated poll metrics and comments
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 acheiving consensus. However, until this protocol is further tested, refined, and proven robust, polls should probably not be considered authoritative nor binding.
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