gochain / gips

GoChain Improvement Proposals
6 stars 3 forks source link

[GIP] Burn Voting #36

Open treeder opened 2 years ago

treeder commented 2 years ago

Summary

Instead of proving you have X amount of GO to vote with like we've done in the past, voters would vote with GO which would be burned.

Why

Pros

Cons

Specification

Additional Information

You could also potentially have a blind vote so nobody knows what the current tally is. In this case, each voter would choose their answer then get an address to send to. At the cutoff time, all the addresses balances would be summed up then burnt.

QuPsi commented 2 years ago

Would this apply to the node validators as well or only community members?

treeder commented 2 years ago

Good question. I think it should apply to all including validators, but may be hard to get them to agree to that. Perhaps it could apply to both sides in separate voting pools so it would still be separate votes, but burnt for the validator votes and separately for the community votes.

QuPsi commented 2 years ago

Yeah, the only way I'd go for this is if the validators have their Go burned as well. It would be really unfair to the community otherwise. Having the community sacrifice their Go that they paid for while the validators get free Go AND free votes. Definitely not balanced nor fair.

Further, if the concern is users shuffling Go around to vote multiple times from different wallets, could have a locking mechanism where users send their Go to be locked up until the vote is over and then returned afterwards. This is just a thought, not fully fleshed out. Would definitely need more discussion.

I'll be honest, I don't particularly like this idea.

Honestly, I'd completely reverse it. Make it free for community members to vote, but charge the validators Go and burn their fees... they're getting them for free anyway and have amassed quite a substantial amount at this point. I doubt many would go for this, but I don't like the idea of having to sacrifice my investment to vote.

QuPsi commented 2 years ago

Just a thought, if the worry is about shuffling Go around... when the votes are tallied, there could be a function to check the amount of Go in a wallet and compare it to the number of votes that was submitted. This way, a user has to maintain their Go in their wallet at the time votes are tallied up. If they submitted 100 votes and there's only 10 Go left if their wallet at the time of vote counting, only 10 votes count.

Just a thought...

SAClough commented 2 years ago

Could this result in richer people, who can afford to burn a substantial amount of Go, pushing votes through that would skew things in their favour so that they benefit at the expense of those who couldn't afford to lose their Go in the longer term?