RE: Proposal: Change Up and Downvotes to bids by raycoms

View this thread on: hive.blog | peakd.com | ecency.com

Viewing a response to: @valued-customer/re-raycoms-q0wy7o

steem · @raycoms · Nov 13 '19

Actually, the system I am proposing would not be too different from what we have now, you got votes which are worth a certain quantity of vests depending on the vests and VP you got and the % you vote with.

The difference is that this vote will evolve around a fixed point (the value you set).
Meaning, if the value of the post is under the value you set, your vote will contribute to add more and if the value of the post is above, it will remove from it.

properties (22)

`author`	raycoms
`permlink`	q0wyc1
`category`	steem
`json_metadata`	{"app":"steemit/0.1"}
`created`	2019-11-13 15:14:27
`last_update`	2019-11-13 15:14:27
`depth`	2
`children`	3
`last_payout`	2019-11-20 15:14:27
`cashout_time`	1969-12-31 23:59:59
`total_payout_value`	0.000 HBD
`curator_payout_value`	0.000 HBD
`pending_payout_value`	0.000 HBD
`promoted`	0.000 HBD
`body_length`	457
`author_reputation`	115,046,969,395,583
`root_title`	"Proposal: Change Up and Downvotes to bids"
`beneficiaries`	`[]`
`max_accepted_payout`	1,000,000.000 HBD
`percent_hbd`	10,000
`post_id`	92,466,870
`net_rshares`	0

@valued-customer · Nov 13 '19 (edited)

So, that basically renders the algorithm that will calculate VP deployed per post utterly incalculable, given that you vote on more than one post and others vote on those posts.  The change in payout value will change on each post and change the calculation of how much VP to assign to that post.  It will do this simultaneously on all the posts you vote.  Each assignment of VP will then change how much VP you have available for each vote, and then have to change again on all posts every time someone else votes.

Not even the best quantum computer in the world can do this.  It's basically an insoluble mathematical problem.

properties (22)

`author`	valued-customer
`permlink`	re-raycoms-q0x1hq
`category`	steem
`json_metadata`	{"tags":["steem"],"app":"steempeak/2.0.6"}
`created`	2019-11-13 16:22:51
`last_update`	2019-11-13 16:25:15
`depth`	3
`children`	2
`last_payout`	2019-11-20 16:22:51
`cashout_time`	1969-12-31 23:59:59
`total_payout_value`	0.000 HBD
`curator_payout_value`	0.000 HBD
`pending_payout_value`	0.000 HBD
`promoted`	0.000 HBD
`body_length`	628
`author_reputation`	362,737,313,922,438
`root_title`	"Proposal: Change Up and Downvotes to bids"
`beneficiaries`	`[]`
`max_accepted_payout`	1,000,000.000 HBD
`percent_hbd`	10,000
`post_id`	92,469,130
`net_rshares`	0

@raycoms · Nov 13 '19

Nono, the quantity of % of VP you add to it will stay the same always. The thing that changes is the actual value of the post itself.

properties (22)

`author`	raycoms
`permlink`	q0x41b
`category`	steem
`json_metadata`	{"app":"steemit/0.1"}
`created`	2019-11-13 17:17:36
`last_update`	2019-11-13 17:17:36
`depth`	4
`children`	1
`last_payout`	2019-11-20 17:17:36
`cashout_time`	1969-12-31 23:59:59
`total_payout_value`	0.000 HBD
`curator_payout_value`	0.000 HBD
`pending_payout_value`	0.000 HBD
`promoted`	0.000 HBD
`body_length`	133
`author_reputation`	115,046,969,395,583
`root_title`	"Proposal: Change Up and Downvotes to bids"
`beneficiaries`	`[]`
`max_accepted_payout`	1,000,000.000 HBD
`percent_hbd`	10,000
`post_id`	92,470,584
`net_rshares`	0

@valued-customer · Nov 14 '19

The quantity of VP is not stable.  Every vote I cast at 25% VP changes the value of every other vote I cast, because my VP is depleted as I vote, and recharges when I don't.  It's not possible for VP to remain the same when it is depleted to vote.  

It seems you envision the VP slider eliminated.  Not sure I like the idea of only being able to vote at a level set at the factory.  I settled on 25% because that best fits how I use Steem, allowing my VP to recharge nominally to keep my votes relatively equally valuable.

properties (22)