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

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

Viewing a response to: @holger80/re-chrisrice-qaixkv

proposal · @chrisrice · May 18 '20 (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?

👍 dbuzz

`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`	""

properties (23)vote details (1)

voter	weight	wgt%	rshares	pct	time
dbuzz	0 B		13,050,195,762	3%

@holger80 · May 18 '20

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.

👍 andrepol, anli, holycow2019

`author`	holger80
`permlink`	re-chrisrice-qaiyww
`category`	proposal
`json_metadata`	{"tags":["proposal"],"app":"peakd/2020.05.3"}
`created`	2020-05-18 11:36:33
`last_update`	2020-05-18 11:36:33
`depth`	5
`children`	5
`last_payout`	2020-05-25 11:36:33
`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`	527
`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,444,260
`net_rshares`	43,175,178,550
`author_curate_reward`	""

properties (23)vote details (3)

voter	rshares	pct
anli	5,772,449,017	99%
andrepol	37,120,999,627	99%
holycow2019	281,729,906	100%

@chrisrice · May 18 '20 (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)

`author`	chrisrice
`permlink`	qaj6e6
`category`	proposal
`json_metadata`	{"users":["peakd"],"app":"hiveblog/0.1"}
`created`	2020-05-18 14:18:12
`last_update`	2020-05-18 14:43:57
`depth`	6
`children`	0
`last_payout`	2020-05-25 14:18:12
`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`	940
`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,446,446
`net_rshares`	0

@chrisrice · May 18 '20

> 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)

`author`	chrisrice
`permlink`	qaj7aq
`category`	proposal
`json_metadata`	{"app":"hiveblog/0.1"}
`created`	2020-05-18 14:37:42
`last_update`	2020-05-18 14:37:42
`depth`	6
`children`	3
`last_payout`	2020-05-25 14:37:42
`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`	632
`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,446,749
`net_rshares`	0

@netuoso · May 18 '20

Not sure you are really understanding how the blockchain works though. The frontend doesnt matter. Holger is saying that you should check the max_accepted_payout before considering the post as a valid DBuzz post. You also don't need to use Hive.blog or any other frontend to post to a community.

So if your website shows all posts in your community, that literally just means it is showing all posts with the category `hive-xxxxx` where `xxxxx` is your community number.

properties (22)

`author`	netuoso
`permlink`	re-chrisrice-qaj7my
`category`	proposal
`json_metadata`	{"tags":["proposal"],"app":"peakd/2020.05.3"}
`created`	2020-05-18 14:44:57
`last_update`	2020-05-18 14:44:57
`depth`	7
`children`	2
`last_payout`	2020-05-25 14:44:57
`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`	471
`author_reputation`	151,901,967,807,285
`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,446,874
`net_rshares`	0

2 replies

@holger80 · May 18 '20

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.

👍 andrepol, anli, holycow2019, re2pair

`author`	holger80
`permlink`	re-chrisrice-qaiz8f
`category`	proposal
`json_metadata`	{"tags":["proposal"],"app":"peakd/2020.05.3"}
`created`	2020-05-18 11:43:30
`last_update`	2020-05-18 11:43:30
`depth`	5
`children`	1
`last_payout`	2020-05-25 11:43:30
`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`	239
`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,444,336
`net_rshares`	42,597,545,031
`author_curate_reward`	""

properties (23)vote details (4)

voter	rshares	pct
anli	5,666,069,453	99%
andrepol	36,421,207,653	99%
holycow2019	275,418,383	100%
re2pair	234,849,542	100%

@chrisrice · May 18 '20

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)