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

proposal · @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

@chrisrice · 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. 

1. Ah.. checking to ensure that the max_accepted_payout was $1.00 would block any rogue actors from posting to our DAPP since we would filter those out by checking.

2. It sounds like the only issue now is how to get Hive.Blog and @peakd to set the max payouts in our D.Buzz Community to $1.00, right?

properties (22)

`author`	chrisrice
`permlink`	qaj82g
`category`	proposal
`json_metadata`	{"users":["peakd"],"app":"hiveblog/0.1"}
`created`	2020-05-18 14:54:18
`last_update`	2020-05-18 14:54:18
`depth`	8
`children`	0
`last_payout`	2020-05-25 14:54:18
`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`	518
`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,447,038
`net_rshares`	0

@chrisrice · May 18 '20

> You also don't need to use Hive.blog or any other frontend to post to a community.

People won't need to use Hive.Blog or @peakd to post to our community but we want them to be able to use both to post to our community so that our users will have more options.

properties (22)