Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allowing to set voteweight higher then 100% (while consuming your SBD balance with each vote) #493

Closed
Gutalean opened this issue Oct 8, 2016 · 3 comments

Comments

@Gutalean
Copy link

Gutalean commented Oct 8, 2016

Full description is given here: https://steemit.com/steemit/@everythink/proposal-allowing-to-range-your-voteweight-higher-then-10000-while-consuming-you-sbd-balance-with-each-vote

@mvandeberg
Copy link
Contributor

This system is inherently game-able. As soon as you can pay X SD and earn X+1 SD in value from doing so, the only logical economic decision is to vote. The n^2 curve for paying out rewards heavily favors whale voters as their SD will provide more rshares per SD than minnows. This will only allow whales to spend their SD to give themselves more SD. It will become a sink for minnows that never pays a return. The only way this could possible work is if there were a flat SD to rshare conversion rate. This would eliminate the skew in favor of whales and even the playing field per SD. However, it would still favor large post payouts and does not solve the problem of earning more than you spend for high payout posts. For low payout posts it does not make sense to boost your vote in this way. You would be better off transferring the SD directly to author.

@theoreticalbts
Copy link
Contributor

My understanding of this is it's a UI proposal for a per-user setting to transform the "upvote" button into an "upvote+tip" button (opt-in).

What would make this gameable is if the tip influenced the post payout (hence a tipper could push a post along the O(n^2) curve) or sort order (hence a tipper could purchase a high-ranked spot on Trending).

There's nothing inherently breaking about a UI action which simply combines a vote and a transfer.

@theoreticalbts
Copy link
Contributor

Closing, let's move the discussion to steemit/condenser#401

On1x pushed a commit to VIZ-Blockchain/viz-cpp-node that referenced this issue May 28, 2018
1. update appbase submodule commit (more fixes there)
2. use filename from cli options instead of hardcoded
3. replace property_tree reader with program_options (so several "plugin" lines don't throw exception)
4. prepare logging options for appbase::write_default_config
On1x pushed a commit to VIZ-Blockchain/viz-cpp-node that referenced this issue May 28, 2018
On1x pushed a commit to VIZ-Blockchain/viz-cpp-node that referenced this issue May 28, 2018
On1x pushed a commit to VIZ-Blockchain/viz-cpp-node that referenced this issue May 28, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants