From 05fc0bca376daceff74716ef9b0a65e05b81746f Mon Sep 17 00:00:00 2001
From: xray-acid <101130721+xray-acid@users.noreply.github.com>
Date: Fri, 20 May 2022 16:49:05 +0200
Subject: [PATCH] Update and rename User help to User help.md

---
 Support/User help    |  1 -
 Support/User help.md | 37 +++++++++++++++++++++++++++++++++++++
 2 files changed, 37 insertions(+), 1 deletion(-)
 delete mode 100644 Support/User help
 create mode 100644 Support/User help.md

diff --git a/Support/User help b/Support/User help
deleted file mode 100644
index 8b13789..0000000
--- a/Support/User help	
+++ /dev/null
@@ -1 +0,0 @@
-
diff --git a/Support/User help.md b/Support/User help.md
new file mode 100644
index 0000000..f7111b8
--- /dev/null
+++ b/Support/User help.md	
@@ -0,0 +1,37 @@
+
+Status community featuring using waku v2
+
+    Status: raw
+    Editor: Szymon Szlachtowicz szymon.s@ethworks.io
+
+This spec is a proposition of voting on community featuring over waku v2.
+Overview #
+
+When there is a active community that is seeking new members, current users of community should be able to feature their community so that it will be accessible to larger audience. Status community curation DApp should provide such a tool.
+
+Rules of featuring: - Given community can’t be featured twice in a row. - Only one vote per user per community (single user can vote on multiple communities) - Voting will be done off-chain - If community hasn’t been featured votes for given community are still valid for the next 4 weeks
+
+Since voting for featuring is similar to polling solutions proposed in this spec could be also used for different applications.
+Voting #
+
+Voting for featuring will be done through waku v2.
+
+Payload of waku message will be :
+
+type FeatureVote = {
+    voter: string // address of a voter
+    sntAmount: BigNumber // amount of snt voted on featuring
+    communityPK: string // public key of community
+    timestamp: number // timestamp of message, must match timestamp of wakuMessage
+    sign: string // cryptographic signature of a transaction (signed fields: voterAddress,sntAmount,communityPK,timestamp)
+}
+
+timestamp is necessary so that votes can’t be reused after 4 week period
+Counting Votes #
+
+Votes will be counted by the DApp itself. DApp will aggregate all the votes in the last 4 weeks and calculate which communities should be displayed in the Featured tab of DApp.
+
+Rules of counting: - When multiple votes from the same address on the same community are encountered only the vote with highest timestamp is considered valid. - If a community has been featured in a previous week it can’t be featured in current week. - In a current week top 5 (or 10) communities with highest amount of SNT votes up to previous Sunday 23:59:59 UTC are considered featured.
+Copyright #
+
+Copyright and related rights waived via CC0.