transfer_votepower - solution to whale voting power concentration

jl777(62)
Published in
#steemit
Words
305
Reading
2 min
Listen
Play
10y

I wont rehash the issues that come from whales having so much voting power. There are technical security reasons for there being whales.

So it is a bit of unstoppable force vs immovable object...

However, a few whales have started farming out their voting as they cant be online 24/7 for more than 1 week at a time. My idea is to allow the voting power to be given to another account for a specific amount of time but also only a specific percentage of the power.

Internally, each vote has 100 increments, so this naturally creates 100 possible divisions. A $100 whale vote becomes 100x $1 dolphin votes. The security aspect can still be maintained by the whale's management of the 100 dolphins.

This would require a bit of technical work, but really compared to what has already been done it is a pretty small change with a new API:

transfer_votepower (1 to 100%) numdays revshare.

This updates the table of voting power and I think all the rest stays much the same. So whatever voting power the receiving account has is enhanced with a percentage of the whale's power. A bit more complicated to unravel the revshare allocation, but I know the devs can do this.

Being time, limited the new dolphin has to do good work to keep getting the transfer_votepower renewed. With 100 whales, this is 10,000 jobs that can be created!

Now we just need to convince the devs and whales to do this. The result at the extreme would be 10,000 paid curators smoothly allocating the curation rewards to a lot larger number of posts. Of course some whales will continue to be online all the time, others to use bots, but this method can be done with any subset and for just a trial period for each whale.

https://github.com/steemit/steem/issues/276

transfer_votepower - solution to whale voting power concentration | Ecency