.jpg)
Problem :
Thanks to the headsup* by @twinner we came to know that big power dolphins and whales can deplete their power 100% by upvoting their own content and then turn around and delegate 100% of their depleted power to their second account and deplete the power again 100% by upvoting their own content. Then they wait 7 days and do it again at a profit of 150% of what they would get upvoting 10 posts per day at 100% power thus gaming the ecosphere.
Solutions
Proposal 1.
Calendar Approach (Purgatory)
One proposal was to extend the delegated power return time to 11 days from the current 7 day "Purgatory", which solves the financial issue by making it unprofitable, but could undermine usage of delegation by tying up delegated power longer than desired or required. Even 7 days seems like a long time to begin with.
Proposal 2.
There are other ways to curtail this problem that need not negatively impact SP delegation. Here are some possible options.
.jpg)
A. Handcuffs.
Should you be able to delegate power that is drained or should you only be able to delegated unused power? I think we should be able to delegate drained power. Restricting this might come across to lenders as too rigid and inconvenient causing less power to be delegated by even legitimate power sharers.
.jpg)
B. Magic Show.
Should power delegated in a drained state not start to recharge for the lender until it returns back to the lender after 7 days? This sounds better than (A.) but it still doesn't seem fair that drained power magically and instantly recharges for use by the borrower.
C. NiCad Battery.
Should drained delegated power need to be recharged by the borrower before it is usable by the borrower? I call this the NiCad Battery Model and I like this the best as it comes across as the most flexible, fair and logical solution. IRL if you loan me a depleted battery I need to recharge it to use it. It might involve assigning a depletion /recharge state or clock to each unit/block/contract of power that is independent of lender/borrower like the timers on equipment in games like Mobile Strike. Coders need to consider if that is going to be feasibly added to the blockchain.
See our development discussion forum here
https://discord.gg/9SQvxJT
Hope this helps.
P.S. I opened an issue report on Github for this and it is open for comment at https://github.com/steemit/steemit-docs/issues/6
I also like the Ni-Cad battery idea. If someone delegates SP to someone else, the delegated power should only be at the power it was at when the delegator had it until it recharges. So if the delegators voting power is at 1% and he/she delegates it to someone else if will have to recharge 99% before it can be used if the delegators voting power is at 90% it will only have to charge a little bit.
Exactly.
Just make it so you can't upvote your own posts. Easy
Commenting/UpVoting on his own Post is bad sign....
Agreed.
Upvoting for your comments/Post will lead your Rating down.. you need some smart content, like yours to get real visitors and Upvote to get success... if some one with good Reputation Score Upvote for you you will get benefit as will as some earning, But self-Voting will lead your account rating Down my Friend :-)
Thanks @akraees.
Congratulations @cyberspace! You have completed some achievement on Steemit and have been rewarded with new badge(s) :
Click on any badge to view your own Board of Honor on SteemitBoard.
For more information about SteemitBoard, click here
If you no longer want to receive notifications, reply to this comment with the word
STOPGreat suggestion!
Thanks @timcliff. Can you suggest a group, web or entity to follow/join to keep on top of identified real Steemit issues consolidated in one place (like an intel center) other than wading through the randomness of the feed?
Well, not to sound too narcissistic, but I am actually probably one of the better accounts to follow for that type of thing. There are also the GitHub repositories (links in the FAQ) which track the issues that are reported. @steemitblog also posts official announcements, but they don't post about issues much. The tag #steem-dev also has a fair amount of info on glitches. Those are probably your best resouces (at least that I can think of).. Unfortunately there isn't a one-stop-shop that has everything. It is kind of scattered through various sources.
Thanks. I am following you and will add the others. I will look into it, give it some thought and work on this.
Is there any central official marketing plan, budget or director for steemit.com?
Steemit is a privately held company. @ned is their CEO. Here is a link to their roadmap: https://steemit.com/steemit/@steemitblog/steemit-2017-roadmap
Thanks. Excellent.
It might be most simple to not allow SP delegation from any account that has voted in the last 7 days. There's also been an idea floated for averaging each account's voting power when the delegation is made.
Thanks @pfunk!
7 day hiatus on voting - would that will still be a "Magic Show" if the SP is usable by the owner right after it gets used by the borrower and returns to him? If not, and one has to wait 7 more days, then 2 weeks of down time for one week of delegation would likely kill any short term use of SP delegation.
How does the averaging SP prior to delegation work? Interesting.
Congratulations @cyberspace! You have completed some achievement on Steemit and have been rewarded with new badge(s) :
Click on any badge to view your own Board of Honor on SteemitBoard.
For more information about SteemitBoard, click here
If you no longer want to receive notifications, reply to this comment with the word
STOPPlease note that solution can't be too complex.
Also, it seems like [C] wouldn't let me do things like quick power-up for newbies, as they would have to wait for recharge.
Maybe something simple like maximum amount of Steem Power you are able to delegate can't be higher than your Voting Power?
So if you largely exhausted your total 1000 SP by voting and have VP 25%, then you can delegate only 250 SP
Thanks @gtg. You are probably right. That may be the practical solution then. That was my first thought (A) which I called the "Handcuff" approach.
Hey, nice work here!
Have the handcuffs placed yet do you know?
That does sound like the most reasonable solution.