
I never cease to be amazed by the number of people that think protocols should be changed the moment they don't personally like the results.
The existing stake-based voting system is the core design principle of Hive. It perfectly allows for a complete cessation of all DHF spending: voters just need to stop voting for proposals.
But apparently the will of the voters isn't enough. Instead, we should add new rules that overrule the previous rules because someone isn't happy with the spend level.
I understand your concern, but the consequence of this would be the largest holders are disenfranchised of the rights they paid for because you don't like the existing rules any more.
Note, the existing rules do allow you to have more say: buy more Hive and you can vote up the return proposal. This isn't about 1st and 2nd class citizens: it's a stake-weight system "by design". Anyone can buy more stake if they want more influence (or sell it if they want less).
Note: I'm not even that much in favor of stake-weighted systems in general, although its pretty easy to understand why Hive has one (prevention of sybil attacks being one of the reasons). My primary other project is in fact completely reverse in design: equal weighted voting per person. But changing the rules of an existing system is completely different from designing a new one.
Leave to:
Read more #hive-139531 posts
Best Posts From blocktrades
We have not curated any of blocktrades's posts yet. But you can encourage our curation team to review posts by visiting them regularly and by referring other readers. Because we give priority to frequently read content.
More Posts From blocktrades
- Release of new HAF API stack 1.28.6 next week
- HAF API server stack ready to be released 11/3/2025
- Improving Hive’s semantic search performance
- Updates for Hive roadmap from the BlockTrades team
- 2nd update of 2025: Hive API stack v1.27.11 officially released
- 1st update of 2025: Releasing API node software this week
- 10th update of 2024: API node software release in Dec, hardfork tentatively set for Q1 2025
- Benchmarking hivemind API calls after switching to postgREST server
- 8th update of 2024: Work on Hive apps (User Interfaces)
- 7th update of 2024: early "release notes" for Hived and HAF apps