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

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

Viewing a response to: @dbuzz/proposal-to-change-usdhive-at-the-blockchain-level

proposal · @mytechtrail · May 17 '20

$0.13

 I like the max_accepted_payout feature as mentioned by @holger80. I guess the next big discussion would be where to set it 1-5 HBD.

👍 dbuzz

`author`	mytechtrail
`permlink`	re-dbuzz-qahr6y
`category`	proposal
`json_metadata`	{"tags":["proposal"],"app":"peakd/2020.05.3"}
`created`	2020-05-17 19:52:09
`last_update`	2020-05-17 19:52:09
`depth`	1
`children`	2
`last_payout`	2020-05-24 19:52:09
`cashout_time`	1969-12-31 23:59:59
`total_payout_value`	0.062 HBD
`curator_payout_value`	0.063 HBD
`pending_payout_value`	0.000 HBD
`promoted`	0.000 HBD
`body_length`	132
`author_reputation`	19,007,675,085,002
`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,430,725
`net_rshares`	395,799,861,678
`author_curate_reward`	""

properties (23)vote details (1)

voter	weight	wgt%	rshares	pct	time
dbuzz	0 B		395,799,861,678	100%

@chrisrice · May 18 '20

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 gather attention on this, we were scheduled to launch today but this issue delayed us.. if it delayed us, it will delay other DAPPs too.

properties (22)

`author`	chrisrice
`permlink`	qaixsy
`category`	proposal
`json_metadata`	{"users":["nathansenn","holdger08","peakd"],"app":"hiveblog/0.1"}
`created`	2020-05-18 11:12:36
`last_update`	2020-05-18 11:12:36
`depth`	2
`children`	1
`last_payout`	2020-05-25 11:12: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`	743
`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,932
`net_rshares`	0

@mytechtrail · May 18 '20

Thanks for the reply, Always a way around with code.

I wonder if your DAPP could cryptographicaly sign posts so third party posts could be detected and dealt with by groups like @hivewatchers. When you attach token benefits to users using the DAPP the signed posts would be detectable and therefore properly dealt with.

Just my 2 cents worth

properties (22)