Politeia Digest Issue 3 — Oct 31-Nov 6 2018
Premium Listing for Decred on Easyrabbit — submitted Oct 30th by easyrabbit — 11 comments
Easyrabbit has already listed DCR and is offering a “premium listing” for 30 DCR — with promotions like no/low trading fees and feature placement on the site and in social media. Comments point out that Decred has never paid for an exchange listing and generally express skepticism about this offer.
Sweepstakes — submitted Nov 5th by geraldoneto — 8 comments
This proposal describes a raffle system and some example configurations, but does not propose a specific plan for building it. Comments criticize the proposal for lack of detail, and express doubt that building such a system is worthwhile.
The votes that concluded this week all had the same start block. The ticket pool held 41,102 tickets when the ticket snapshot for these proposals was taken (block 286972), so the quorum requirement (20%) was 8,220 votes.
Decred Open Source Research — voting closed Nov 5–40 comments (+2)
11,854 Yes votes, 1,287 No votes (90.2% Yes) — voter participation of 32%, support from 28.8% of tickets.
#research channels have been created on Matrix and Slack platforms and they have been bridged. Discussions of how to get this program up and running have started. Another Politeia proposal for collecting and discussing research questions and methods will be submitted soon.
Change language: PoS Mining to PoS Voting, Stakepool to Voting Service Provider — voting closed Nov 5–19 comments (+0)
11,991 Yes votes, 754 No votes (94.1% Yes) — voter participation of 31%, support from 29.2% of tickets.
Next step: The pull request to make this change on the docs site will be rebased and merged around Nov 12.
Ditto Communications Proposal for Decred — voting closed Nov 5–47 comments (+3)
13,206 Yes votes, 7,985 No votes (62.3% Yes) — voter participation of 51.6%, support from 32.1% of tickets.
Next step: @dustorf will have a meeting with Ditto representatives to kick things off and report back about how Ditto will communicate with the project and community going forward.
Wachsman Communications Proposal for Decred — voting closed Nov 5–73 comments (+2)
3,646 Yes votes, 9,556 No votes (27.6% Yes) — voter participation of 32.1%, support from 8.9% of tickets.
Much of the discussion in the #proposals channel this week has been about the ongoing votes. After a few days, the Ditto proposal became the most closely watched, as it bounced above and below the critical 60% threshold.
The details of how Politeia stores data have been discussed. There are no timestamps recorded in the repository for individual ticket votes, but these are journaled and added in hourly commits, so it is possible to know which hour a ticket voted in based on this data. The lack of timestamps in the data is a measure to protect the privacy of people who vote with large blocks of tickets at once without using the vote trickling options CLI offers.
@snr01 produced charts from the ticket voting data showing number of Yes and No votes per commit (hour) for the Ditto and Wachsman proposals. The final version is included below.
The chart indicates that there were short intervals where significant blocks of tickets voted, typically for one proposal and against another. The most significant instance was on the 3rd day of the voting period, when in a single hour 4,713 tickets voted Yes on Ditto and 4,716 voted No on Wachsman. That could be one large Decred holder voting their tickets at once, or several who happened to vote in the same hour.
Analysis of the tickets indicates that almost every ticket that voted on the Wachsman proposal also voted on the Ditto proposal (98%), whereas 39% of the tickets that voted on Ditto did not vote on Wachsman. The divergence in voting rates happened after that big block of votes on day 3. It is likely a reaction to the big block of votes making it seem unlikely that the Wachsman proposal would pass.
The Ditto proposal’s approval rate steadily decreased after this, and was at less than the required 60% for much of the last few days, until a late surge in Yes votes pushed it over the line.
Of the 12,937 tickets that voted on both proposals, 61.2% voted for one and against the other, 22.6% voted Yes on both, and 16.2% voted No on both. There are significant groups within the community who wanted neither firm to be hired, and who were happy with either/both.
Work on a more efficient way of re-formatting the data to make it amenable to analysis was also discussed in the channel.
Documentation for Politeia data
A pull request is open to add a page about navigating Politeia data to the docs site.
Data stored in the repository is attributed to users through their Politeia public key. Each user’s public key(s) can be retrieved through an API call, and used to identify all of their proposals, comments and comment up/down votes. More on this next week.
About this issue
Content for this edition was authored by @richard-red, with feedback from @bee. Chart and data provided by @snr01
Also available on Github.
If you have thoughts on how this format could be developed or would like to contribute, join the Writers channel and let us know.