create account

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

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

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

· @ash ·
I think best practice is to use a 2nd account for buzzing any ways. Even comments can clutch up your account, especially when you search for blog comments. So my plan is to use another account, and I think max payout is a good way to progress. No need to interfere with a hardfork imo
properties (22)
authorash
permlinkre-dbuzz-qah6q6
categoryproposal
json_metadata{"tags":["proposal"],"app":"peakd/2020.05.3"}
created2020-05-17 12:30:09
last_update2020-05-17 12:30:09
depth1
children2
last_payout2020-05-24 12:30:09
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_length284
author_reputation286,803,743,324,398
root_title"Proposal to Change $HIVE at the Blockchain Level"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id97,423,718
net_rshares0
@chrisrice ·
$0.13
As it turns out, the max_payout feature won't work.

This should be solved at the blockchain level or it would require a change to all existing front-ends and future existing front-ends.

**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 share the message so that more people can start discussing this. If we solve this, it would likely increase the value of the HIVE blockchain, since as it stands now, it's broken.
👍  
properties (23)
authorchrisrice
permlinkqaixn0
categoryproposal
json_metadata{"users":["nathansenn","holdger08","peakd"],"app":"hiveblog/0.1"}
created2020-05-18 11:09:03
last_update2020-05-18 11:09:03
depth2
children0
last_payout2020-05-25 11:09:03
cashout_time1969-12-31 23:59:59
total_payout_value0.065 HBD
curator_payout_value0.065 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length909
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,443,869
net_rshares412,095,297,326
author_curate_reward""
vote details (1)
@dbuzz · (edited)
Using a 2nd account is one option and I think that could work, but a lot of people value the idea of having one account for all front-ends.

And I think if everyone comes together and the best solutions rise to the top, we can find a way to do that.
👍  , , , ,
👎  
properties (23)
authordbuzz
permlinkqah893
categoryproposal
json_metadata{"app":"hiveblog/0.1"}
created2020-05-17 13:03:06
last_update2020-05-18 11:18:24
depth2
children0
last_payout2020-05-24 13:03:06
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_length249
author_reputation276,817,987,330,091
root_title"Proposal to Change $HIVE at the Blockchain Level"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id97,424,097
net_rshares-8,720,341,457,225
author_curate_reward""
vote details (6)