Ohh sorry im dumb

In the Nostr ecosystem, NIP-88 (Nostr Implementation Possibility 88) defines the standard for Polls.

It provides a way for users to create surveys or polls and for other users to vote on them in a decentralized way. Because Nostr is just a protocol for passing messages (events), NIP-88 acts as the "instruction manual" so that different apps (like Amethyst, Damus, or Primal) all know how to display the same poll and count the votes correctly.

How it Works

NIP-88 uses two specific event types (kinds) to manage the process:

* Kind 1018 (The Poll Event): This is the original post created by the author. It contains the question, the different options (choices), and metadata like when the poll ends.

* Kind 1018 (The Response/Vote): When you vote, your client creates a new event that references the original poll's ID and specifies which option you chose.

Key Features

* Single vs. Multiple Choice: The NIP supports both "singlechoice" and "multiplechoice" formats.

* Decentralized Counting: Unlike Twitter, where a central server counts the votes, your Nostr client (the app you use) fetches all the vote events from relays and counts them locally.

* Anti-Spam: To keep things fair, the standard generally recognizes only one vote per public key. If you try to vote twice, the client will usually only count your most recent vote (based on the timestamp).

* Relay Specifics: Poll authors can suggest specific relays for people to send their votes to, ensuring that the results are easier to find and aggregate.

Why is it useful?

Before NIP-88, if you wanted to run a poll on Nostr, you had to just ask a question in a text note and look at the replies. NIP-88 turned polls into a structured feature, allowing for pretty UI buttons and automated charts that look and feel like the polls you see on centralized social media.

Would you like me to show you an example of what the raw JSON for a NIP-88 poll event looks like?

On nostr, only zap Polls make sense. One zap, one vote.