create account

RE: Proposal to Change $HIVE at the Blockchain Level by holger80

View this thread on: hive.blogpeakd.comecency.com

Viewing a response to: @chrisrice/qaiwzh

· @holger80 · (edited)
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:
![image.png](https://files.peakd.com/file/peakd-hive/holger80/jQwZF3bV-image.png)

Hive.blog could also be updated and a new option for D.BUZZ content could be added here:
![image.png](https://files.peakd.com/file/peakd-hive/holger80/dvu4c41K-image.png)

@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.
👍  , , ,
properties (23)
authorholger80
permlinkre-chrisrice-qaixkv
categoryproposal
json_metadata{"tags":["proposal"],"app":"peakd/2020.05.3"}
created2020-05-18 11:07:45
last_update2020-05-18 11:19:24
depth3
children9
last_payout2020-05-25 11:07:45
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length768
author_reputation358,857,509,568,825
root_title"Proposal to Change $HIVE at the Blockchain Level"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id97,443,846
net_rshares44,094,445,698
author_curate_reward""
vote details (4)
@chrisrice · (edited)
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?
👍  
properties (23)
authorchrisrice
permlinkqaiyfe
categoryproposal
json_metadata{"app":"hiveblog/0.1"}
created2020-05-18 11:26:03
last_update2020-05-18 11:29:03
depth4
children8
last_payout2020-05-25 11:26:03
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length418
author_reputation70,462,754,167,857
root_title"Proposal to Change $HIVE at the Blockchain Level"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id97,444,120
net_rshares13,050,195,762
author_curate_reward""
vote details (1)
@holger80 ·
Assuming a D.BUZZ post needs to have `max_accepted_payout=1 HBD`. This would mean:

* all posts that have `max_accepted_payout` set to 1 HBD are D.BUZZ posts, no matter on which frond-end the post was written
* all posts that do not have max_accepted_payout` equal to 1 HBD are not a D.BUZZ post.

My proposed changes are not temporary frond-end fixes. Agreement if a post is a D.BUZZ post is already defined at blockchain level. There is no way to cheat, either a post has the correct value for `max_accepted_payout` or not.

👍  , ,
properties (23)
authorholger80
permlinkre-chrisrice-qaiyww
categoryproposal
json_metadata{"tags":["proposal"],"app":"peakd/2020.05.3"}
created2020-05-18 11:36:33
last_update2020-05-18 11:36:33
depth5
children5
last_payout2020-05-25 11:36:33
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length527
author_reputation358,857,509,568,825
root_title"Proposal to Change $HIVE at the Blockchain Level"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id97,444,260
net_rshares43,175,178,550
author_curate_reward""
vote details (3)
@chrisrice · (edited)
> all posts that have max_accepted_payout set to 1 HBD are D.BUZZ posts, no matter on which frond-end the post was written

> all posts that do not have max_accepted_payout` equal to 1 HBD are not a D.BUZZ post.

If you or someone else that is more connected in the HIVE community can get Hive.Blog and @peakd to implement this change, of setting the max payout for posts published to the DBuzz Community to $1, please make it happen.

It would still be a temporary and somewhat messy fix since DAPPs could still launch, even tiny ones that are bootstrapped as simple services to game the system. 

I believe if you were us or another DAPP wanting to offer a reliable service without interruption from rogue actors, you'd be interested in code that made it impossible to game the max_accepted_payout as opposed to relying on verbal agreements with others, and the belief that everyone else in the future would agree to those agreements too.
properties (22)
authorchrisrice
permlinkqaj6e6
categoryproposal
json_metadata{"users":["peakd"],"app":"hiveblog/0.1"}
created2020-05-18 14:18:12
last_update2020-05-18 14:43:57
depth6
children0
last_payout2020-05-25 14:18:12
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length940
author_reputation70,462,754,167,857
root_title"Proposal to Change $HIVE at the Blockchain Level"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id97,446,446
net_rshares0
@chrisrice ·
> My proposed changes are not temporary frond-end fixes. Agreement if a post is a D.BUZZ post is already defined at blockchain level. There is no way to cheat, either a post has the correct value for max_accepted_payout or not.

There is a way to cheat.. 

1. Fork Hive.Blog and publish to our community without the max_accepted_payout code included in our community of the forked front-end.

All of the posts published in our D.Buzz Community reflect onto our site so the posts published to that forked front-end would not be constrained to $1.00 payouts and would therefore trend higher than our real users who posted from D.Buzz.
properties (22)
authorchrisrice
permlinkqaj7aq
categoryproposal
json_metadata{"app":"hiveblog/0.1"}
created2020-05-18 14:37:42
last_update2020-05-18 14:37:42
depth6
children3
last_payout2020-05-25 14:37:42
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length632
author_reputation70,462,754,167,857
root_title"Proposal to Change $HIVE at the Blockchain Level"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id97,446,749
net_rshares0
@holger80 ·
I assume you mean there could arise a new service that allows posts without setting `max_accepted_payout` ? That problem will be solved with SMT (smart media token), there is no need to ask now for a different solution at blockchain level.
👍  , , ,
properties (23)
authorholger80
permlinkre-chrisrice-qaiz8f
categoryproposal
json_metadata{"tags":["proposal"],"app":"peakd/2020.05.3"}
created2020-05-18 11:43:30
last_update2020-05-18 11:43:30
depth5
children1
last_payout2020-05-25 11:43:30
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length239
author_reputation358,857,509,568,825
root_title"Proposal to Change $HIVE at the Blockchain Level"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id97,444,336
net_rshares42,597,545,031
author_curate_reward""
vote details (4)
@chrisrice ·
Until our venture produces a sizable profit for a long length of time, we won't even consider issuing an SMT.

It wouldn't be in the interest of the people who'd buy our token, nor would it be in our interest to issue a token as a small business.

<hr>

Some DAPPs like ours are / will be interested in building a HIVE based DAPP without the commitment of issuing their own token / SMT.

For ventures like us, SMTs won't help since we want to focus on using the $HIVE token.

I also think you are under estimating how fast a rogue act could and might launch a bootstrapped service to publish posts in our DBuzz Community without the $1.00 max_accepted_payout measure.
properties (22)
authorchrisrice
permlinkqaj6z2
categoryproposal
json_metadata{"app":"hiveblog/0.1"}
created2020-05-18 14:30:42
last_update2020-05-18 14:30:42
depth6
children0
last_payout2020-05-25 14:30:42
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length667
author_reputation70,462,754,167,857
root_title"Proposal to Change $HIVE at the Blockchain Level"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id97,446,652
net_rshares0