Viewing a response to: @dbuzz/proposal-to-change-usdhive-at-the-blockchain-level
I think there is no need to modify the Hive at the blockchain level as there is `max_accepted_payout`. This parameter can be set between 0 and 1000000 HBD. For short-form content, this parameter could be set to 1-5 HBD and the post payout will not exceed this. Everything above this threshold will be returned to the reward pool. You can see here how it looks when the parameter set to 1 HBD: https://peakd.com/hive-174578/@abitcoinskeptic/experimenting-with-max-accepted-payout When auto voters are checking this parameter, it can be used to mark a post as short-form content.
author | holger80 |
---|---|
permlink | re-dbuzz-qah473 |
category | proposal |
json_metadata | {"tags":["proposal"],"app":"peakd/2020.05.3"} |
created | 2020-05-17 11:35:30 |
last_update | 2020-05-17 11:35:30 |
depth | 1 |
children | 19 |
last_payout | 2020-05-24 11:35:30 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.592 HBD |
curator_payout_value | 0.589 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 581 |
author_reputation | 358,857,509,568,825 |
root_title | "Proposal to Change $HIVE at the Blockchain Level" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 97,423,013 |
net_rshares | 3,029,385,659,314 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
rishi556 | 0 | 12,042,961,058 | 100% | ||
markkujantunen | 0 | 117,530,653,586 | 43% | ||
vimukthi | 0 | 220,727,707,751 | 100% | ||
espoem | 0 | 268,985,342,949 | 100% | ||
riyuwe | 0 | 1,172,736,279 | 100% | ||
anli | 0 | 6,298,460,135 | 99% | ||
andrepol | 0 | 37,717,463,272 | 99% | ||
brianoflondon | 0 | 575,684,108,586 | 100% | ||
theycallmedan | 0 | 1,788,664,070,005 | 2% | ||
holycow2019 | 0 | 287,121,509 | 100% | ||
re2pair | 0 | 275,034,184 | 100% |
This sounds excellent.
author | brianoflondon |
---|---|
permlink | re-holger80-qah6bj |
category | proposal |
json_metadata | {"tags":["proposal"],"app":"peakd/2020.05.3"} |
created | 2020-05-17 12:21:21 |
last_update | 2020-05-17 12:21:21 |
depth | 2 |
children | 1 |
last_payout | 2020-05-24 12:21:21 |
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 | 23 |
author_reputation | 760,626,613,375,672 |
root_title | "Proposal to Change $HIVE at the Blockchain Level" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 97,423,634 |
net_rshares | 0 |
As it turns out, the max_accepted_payout route would not work, here's why: > @nathansenn just informed me of a major flaw in the max_payout route @holdger08. > Users would be able to post to our Community & DAPP from 3rd party front-ends like Hive.Blog and @peakd with those Posts (Buzz's) being exempted from the max_payout code that we hardcode into our DAPP. > Users would then be incentivised to post to our DAPP from 3rd party front-ends and our real users would be punished by being restricted by in-house rules that are not applied to Buzz's posted from 3rd party front-ends. Please help us bring attention to this proposal.. I think it's the only fix and a much needed one at that. Otherwise Dapps like us would also be forced to get involved in politics and in vain when the solution really lies in solving this at the blockchain level @brianoflondon.
author | chrisrice |
---|---|
permlink | qahesh |
category | proposal |
json_metadata | {"app":"hiveblog/0.1","users":["nathansenn","holdger08","peakd","brianoflondon"]} |
created | 2020-05-17 15:24:18 |
last_update | 2020-05-18 11:22:18 |
depth | 3 |
children | 0 |
last_payout | 2020-05-24 15:24:18 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.018 HBD |
curator_payout_value | 0.018 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 864 |
author_reputation | 70,462,754,167,857 |
root_title | "Proposal to Change $HIVE at the Blockchain Level" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 97,426,350 |
net_rshares | 120,691,512,456 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
jeffjagoe | 0 | 2,524,091,140 | 1% | ||
brianoflondon | 0 | 118,167,421,316 | 20% |
@nathansenn just informed me of a major flaw in the max_payout route @holdger08. Users would be able to post to our Community & DAPP from 3rd party front-ends like Hive.Blog and @peakd with those Posts (Buzz's) being exempted from the max_payout code that we hardcode into our DAPP. Users would then be incentivised to post to our DAPP from 3rd party front-ends and our real users would be punished by being restricted by in-house rules that are not applied to Buzz's posted from 3rd party front-ends. Please review the proposal above and the issue more in-depth and comment accordingly @holger08.
author | chrisrice |
---|---|
permlink | qaiwzh |
category | proposal |
json_metadata | {"users":["nathansenn","holdger08","peakd","holger08"],"app":"hiveblog/0.1"} |
created | 2020-05-18 10:54:57 |
last_update | 2020-05-18 10:54:57 |
depth | 2 |
children | 11 |
last_payout | 2020-05-25 10:54:57 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.074 HBD |
curator_payout_value | 0.074 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 600 |
author_reputation | 70,462,754,167,857 |
root_title | "Proposal to Change $HIVE at the Blockchain Level" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 97,443,681 |
net_rshares | 466,238,844,404 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
riyuwe | 0 | 1,148,315,674 | 100% | ||
dbuzz | 0 | 465,090,528,730 | 100% |
3rd party front-ends as @peakd and hive.blog could be easily updated so that they allow setting of may_payout during posting. E.g. @peakd could add a new option here to allow D.BUZZ content:  Hive.blog could also be updated and a new option for D.BUZZ content could be added here:  @peakd and hive.blog are already using `max_accepted_payout`, just an option to set a value higher than 0 HBD needs to be added. edit: For implementation at @peakd and hive.blog, there should be an agreement about the value of `max_accepted_payout` for D.BUZZ, so that only a new option in the drop-down menu is needed.
author | holger80 |
---|---|
permlink | re-chrisrice-qaixkv |
category | proposal |
json_metadata | {"tags":["proposal"],"app":"peakd/2020.05.3"} |
created | 2020-05-18 11:07:45 |
last_update | 2020-05-18 11:19:24 |
depth | 3 |
children | 9 |
last_payout | 2020-05-25 11:07:45 |
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 | 768 |
author_reputation | 358,857,509,568,825 |
root_title | "Proposal to Change $HIVE at the Blockchain Level" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 97,443,846 |
net_rshares | 44,094,445,698 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
anli | 0 | 5,852,077,231 | 99% | ||
andrepol | 0 | 37,717,463,272 | 99% | ||
holycow2019 | 0 | 287,121,509 | 100% | ||
re2pair | 0 | 237,783,686 | 100% |
That would be a temporary fix, and would require politics since new Dapps could arise that would launch without that "fix". Then there would have to be a call to action by the community each time a new DAPP launches to pressure the newly launched DAPP to also instate that "fix". Even if we solve this with temporary front-end fixes, don't you think we should also solve it at the blockchain level, once and for all?
author | chrisrice |
---|---|
permlink | qaiyfe |
category | proposal |
json_metadata | {"app":"hiveblog/0.1"} |
created | 2020-05-18 11:26:03 |
last_update | 2020-05-18 11:29:03 |
depth | 4 |
children | 8 |
last_payout | 2020-05-25 11:26:03 |
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 | 418 |
author_reputation | 70,462,754,167,857 |
root_title | "Proposal to Change $HIVE at the Blockchain Level" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 97,444,120 |
net_rshares | 13,050,195,762 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
dbuzz | 0 | 13,050,195,762 | 3% |
Communities allow moderation what's the concern? Check the post see if it has a max_payout if it doesn't ... mute it.
author | jarvie |
---|---|
permlink | re-chrisrice-qaj87l |
category | proposal |
json_metadata | {"tags":["proposal"],"app":"peakd/2020.05.3"} |
created | 2020-05-18 14:57:24 |
last_update | 2020-05-18 14:57:24 |
depth | 3 |
children | 0 |
last_payout | 2020-05-25 14:57:24 |
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 | 120 |
author_reputation | 388,491,264,112,133 |
root_title | "Proposal to Change $HIVE at the Blockchain Level" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 97,447,081 |
net_rshares | 0 |
Exactly.
author | markkujantunen |
---|---|
permlink | re-holger80-qah4fa |
category | proposal |
json_metadata | {"tags":["proposal"],"app":"peakd/2020.05.3"} |
created | 2020-05-17 11:40:21 |
last_update | 2020-05-17 11:40:21 |
depth | 2 |
children | 1 |
last_payout | 2020-05-24 11:40:21 |
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 | 9 |
author_reputation | 625,120,273,925,515 |
root_title | "Proposal to Change $HIVE at the Blockchain Level" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 97,423,070 |
net_rshares | 0 |
There is a major flaw in trying to use the max_payout to solve this problem. > Users would be able to post to our Community & DAPP from 3rd party front-ends like Hive.Blog and @peakd with those Posts (Buzz's) being exempted from the max_payout code that we hardcode into our DAPP. > Users would then be incentivised to post to our DAPP from 3rd party front-ends and our real users would be punished by being restricted by in-house rules that are not applied to Buzz's posted from 3rd party front-ends. > Please review the proposal above and the issue more in-depth and comment accordingly @holger08.
author | chrisrice |
---|---|
permlink | qaix7y |
category | proposal |
json_metadata | {"users":["peakd","holger08"],"app":"hiveblog/0.1"} |
created | 2020-05-18 11:00:12 |
last_update | 2020-05-18 11:00:12 |
depth | 3 |
children | 0 |
last_payout | 2020-05-25 11:00:12 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.071 HBD |
curator_payout_value | 0.071 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 602 |
author_reputation | 70,462,754,167,857 |
root_title | "Proposal to Change $HIVE at the Blockchain Level" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 97,443,739 |
net_rshares | 446,712,632,631 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
dbuzz | 0 | 446,712,632,631 | 100% |
This is what I was about to type in when I read the proposal.
author | vimukthi |
---|---|
permlink | re-holger80-qahe2m |
category | proposal |
json_metadata | {"tags":["proposal"],"app":"peakd/2020.05.3"} |
created | 2020-05-17 15:08:48 |
last_update | 2020-05-17 15:08:48 |
depth | 2 |
children | 2 |
last_payout | 2020-05-24 15:08:48 |
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 | 61 |
author_reputation | 496,988,497,371,644 |
root_title | "Proposal to Change $HIVE at the Blockchain Level" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 97,426,086 |
net_rshares | 0 |
Thank you for also sharing, and for being in favor of using the max_payout feature to prevent abuse. > Your feedback helps!
author | chrisrice |
---|---|
permlink | qahera |
category | proposal |
json_metadata | {"app":"hiveblog/0.1"} |
created | 2020-05-17 15:23:36 |
last_update | 2020-05-17 15:23:36 |
depth | 3 |
children | 0 |
last_payout | 2020-05-24 15:23: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 | 124 |
author_reputation | 70,462,754,167,857 |
root_title | "Proposal to Change $HIVE at the Blockchain Level" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 97,426,340 |
net_rshares | 41,730,528,035 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
vimukthi | 0 | 41,730,528,035 | 21% |
It seems like the max_payout would work, but it wouldn't and here's why: > Users would be able to post to our Community & DAPP from 3rd party front-ends like Hive.Blog and @peakd with those Posts (Buzz's) being exempted from the max_payout code that we hardcode into our DAPP. > Users would then be incentivised to post to our DAPP from 3rd party front-ends and our real users would be punished by being restricted by in-house rules that are not applied to Buzz's posted from 3rd party front-ends. Please consider the above scenario and comment / share accordingly.
author | chrisrice |
---|---|
permlink | qaixbd |
category | proposal |
json_metadata | {"users":["peakd"],"app":"hiveblog/0.1"} |
created | 2020-05-18 11:02:03 |
last_update | 2020-05-18 11:02:03 |
depth | 3 |
children | 0 |
last_payout | 2020-05-25 11:02:03 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.069 HBD |
curator_payout_value | 0.070 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 568 |
author_reputation | 70,462,754,167,857 |
root_title | "Proposal to Change $HIVE at the Blockchain Level" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 97,443,769 |
net_rshares | 437,799,990,976 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
dbuzz | 0 | 437,799,990,976 | 100% |