Propose waku voting protocol (#393)

content/docs/rfcs/24/README.md

@@ -0,0 +1,80 @@
+---
+slug: 24
+title: 24/STATUS-CURATION
+name: Status Community Directory Curation Voting using Waku v2
+status: raw
+tags: waku-application
+editor: Szymon Szlachtowicz <szymon.s@ethworks.io>
+---
+
+This spec is a proposition for a voting protocol over Waku V2.
+
+# Motivation
+
+In open p2p protocol there is an issue with voting off-chain as there is much room for malicious peers to only include votes that support their case when submitting votes to chain.
+
+Proposed solution is to aggregate votes over waku and allow users to submit votes to smart contract that aren't already submitted.
+
+# Smart contract
+
+Voting should be finalized on chain so that the finished vote is immutable.
+Because of that, smart contract needs to be deployed.
+When votes are submitted smart contract has to verify what votes are properly signed and that sender has correct amount of SNT.
+When Vote is verified the amount of SNT voted on specific topic by specific sender is saved on chain.
+
+## Double voting
+
+Smart contract should also keep a list of all signatures so that no one can send the same vote twice.
+Another possibility is to allow each sender to only vote once.
+
+## Initializing Vote
+
+When someone wants to initialize vote he has to send a transaction to smart contract that will create a new voting session.
+When initializing a user has to specify type of vote (Addition, Deletion), amount of his initial SNT to submit and public key of community under vote.
+Smart contract will return a ID which is identifier of voting session.
+Also there will be function on Smart Contract that when given community public key it will return voting session ID or undefined if community isn't under vote.
+
+# Voting
+
+## Sending votes
+
+Sending votes is simple every peer is able to send a message to Waku topic specific to given application: 
+```
+/status-community-directory-curation-vote/1/{voting-session-id}/json
+```
+
+vote object that is sent over waku should contain information about: 
+
+```ts
+type Vote = {
+    sender: string // address of the sender
+    vote: string // vote sent eg. 'yes' 'no'
+    sntAmount: BigNumber //number of snt cast on vote
+    sign: string // cryptographic signature of a transaction (signed fields: sender,vote,sntAmount,nonce,sessionID)
+    nonce: number // number of votes cast from this address on current vote (only if we allow multiple votes from the same sender)
+    sessionID: number // ID of voting session
+}
+```
+
+## Aggregating votes
+
+Every peer that is opening specific voting session will listen to votes sent over p2p network, and aggregate them for a single transaction to chain.
+
+## Submitting to chain
+
+Every peer that has aggregated at least one vote will be able to send them to smart contract.
+When someone votes he will aggregate his own vote and will be able to immediately send it.
+
+Peer doesn't need to vote to be able to submit the votes to the chain.
+
+Smart contract needs to verify that all votes are valid (eg. all senders had enough SNT, all votes are correctly signed) and that votes aren't duplicated on smart contract.
+
+## Finalizing 
+
+Once the vote deadline has expired, the smart contract will not accept votes anymore.
+Also directory will be updated according to vote results (community added to directory, removed etc.)
+
+# Copyright
+
+Copyright and related rights waived via
+[CC0](https://creativecommons.org/publicdomain/zero/1.0/).

content/menu/index.md

@@ -10,6 +10,7 @@ bookMenuLevels: 1
   - [20/ETH-DM]({{< relref "/docs/rfcs/20/README.md" >}})
   - [21/WAKU2-FTSTORE]({{< relref "/docs/rfcs/21/README.md" >}})
   - [22/TOY-CHAT]({{< relref "/docs/rfcs/22/README.md" >}})
+  - [24/STATUS-CURATION]({{< relref "/docs/rfcs/24/README.md" >}})
 - Draft
   - [1/COSS]({{< relref "/docs/rfcs/1/README.md" >}})
   - [3/REMOTE-LOG]({{< relref "/docs/rfcs/3/README.md" >}})