Currently, the Whitepaper of Hive defines Delegated Proof of Stake as:
Delegated Proof of Stake (DPoS) is the consensus algorithm behind Hive. In a DPoS algorithm, the selection of block producers (called ’witnesses’ on Hive) and all other consensus-based functions are decided based on the weight of staked funds supporting them. Stakeholders hold the highest prominence in DPoS.
- Page 5 of https://hive.io/whitepaper.pdf
Currently, there is only one option for downvote/downwards voting for the Three protocols involving DPoS voting consensus on the Hive blockchain and that is only for Community social media posts. There is no option to downvote witnesses or proposals. This presents a situation that disproportionally applies the ability to take away consensus from others staked voting to only one of the three consensus voting protocols. From what I can tell the main purpose of DPoS was to vote for witnesses and proposals. If downvoting is to be used in a specific way that should only apply to one of three protocols for consensus voting then the Whitepaper should either be amended to address the issue of downvoting or explain why this is the case.
I propose in an attempt to strengthen our community relationship with large stake holders, encourage further use of Hive and investment into our ecosystem through either post creation, becoming a witness or not afraid of retaliation for opinions expressed on a DPoS Blockchain meant to be a:
...dedicated proponent of free speech and transparency.
- Section V.; Sub Section V.2
Page 8 of https://hive.io/whitepaper.pdf
V.5. Content Monetization
Hive is by design intended to store vast amounts of content and to make it available for time-based monetization. Content may be submitted in the form of a ’post’ (parent post) or ’comment’ (child post). Once submitted, a piece of content will be monetizable for a period of 7 days. During that time it may be curated upwards or downwards through upvotes and downvotes until its final value is determined at the end of the 7 day timer.
- Page 5 of https://hive.io/whitepaper.pdf
...That the Hive Whitepaper be amended to remove the downvoting function, that only applies to one of three staked voting protocols for DPoS consensus voting that only applies to community social media posts by amending the following two sentences in the Hive Whitepaper:
As worded currently
V.5. Content Monetization pg.8
During that time it may be curated upwards or downwards through upvotes and downvotes until its final value is determined at the end of the 7 day timer.
V.6. Distributing Rewards Pg.9
When a user submits a post it initiates a 7 day curation window during which it may be upvoted or downvoted until its final evaluation is reached at the end of 7 days.
Proposed DPoS protocol Changes
V.5. Content Monetization pg.8
During that time it may be curated upwards through upvotes until its final value is determined at the end of the 7 day timer.
V.6. Distributing Rewards Pg.9
When a user submits a post it initiates a 7 day curation window during which it may be upvoted until its final evaluation is reached at the end of 7 days.
This change in the Hive Whitepaper's wording is intended to remove the downvoting function on Hive's first layer.
III.2. Protocol Changes
Hardforks and key protocol changes are accepted by 17 out of 20 consensus witnesses. Witnesses accept protocol changes by updating their nodes or reject them by continuing to run the present version. Protocol changes will not be applied and take effect until consensus is reached. All protocol changes are proposed, developed, prepared for and implemented through a transparent and collaborative team-working environment. They are entirely open source from initiation to their final release.
- Page 5 of https://hive.io/whitepaper.pdf