nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2025-01-04 13:45:50 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

add clarifying requirements for voting- tallying-clients

Browse Source
This commit is contained in:
toadlyBroodle 2023-03-25 12:49:56 +09:00
parent b61e25cccc
commit c2e82696d1
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
69.md
View File

@ -65,6 +65,7 @@ A voting client:
* SHOULD NOT allow submission of zap events with amounts greater than `value_maximum` (when specified) * SHOULD NOT allow submission of zap events with amounts greater than `value_maximum` (when specified)
* SHOULD NOT allow submission of zap events with amounts less than `value_minimum` (when specified) * SHOULD NOT allow submission of zap events with amounts less than `value_minimum` (when specified)
* SHOULD NOT allow submission of zap events after `closed_at` time (when specified) * SHOULD NOT allow submission of zap events after `closed_at` time (when specified)
* SHOULD hide tally results, until after a user has zapped the note
## Zap vote format ## Zap vote format
@ -109,8 +110,8 @@ A tallying client:
Additionally, a tallying client: Additionally, a tallying client:
* MUST display the distribution percentages, from the tally total, for each vote option tally * MUST display the distribution percentages, from the tally total, for each vote option tally
* MUST display the `consensus_threshold` (if specified) relative to the winning vote percentage * MUST display the `consensus_threshold` (if specified) relative to the winning vote percentage
* SHOULD publicly blind results until after a user's vote has been received * SHOULD show tally results to all note zappers, even if they haven't voted on an option
* SHOULD publicly display results after the `closed_at` time has passed (if specified) * SHOULD publicly show results after the `closed_at` time has passed (if specified)
* MAY display the counts of zap events received for each option, along with other poll statistics * 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. 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.