create account

Proposal to Change $HIVE at the Blockchain Level by dbuzz

View this thread on: hive.blogpeakd.comecency.com
· @dbuzz · (edited)
Proposal to Change $HIVE at the Blockchain Level
<center>
![HIveChainMatters_promo.png](https://images.hive.blog/DQmSBeMttYH28s3DskMLtosJxx2N3roPPBkBszQhmggAV6C/HIveChainMatters_promo.png)</center>

<hr>

During our [Pre-Launch announcement of D.Buzz](https://hive.blog/hive/@dbuzz/a-microblogging-platform-is-launching-soon-hive)  it came to our attention that there are members of the HIVE community who are concerned with short-form content being used to abuse the reward pool.

People like @jonsnow1983, @trincowski, @ash, @jocieprosza, @belemo and @joanstewart all expressed concerns about this and @chrisrice *(Coordinator of @dbuzz)* believes their concerns are justified.

He reached out to @hiddenblade, @guiltyparties and @hivewatchers who all made various suggestions and recommendations. The final consensus of a "Hive Keepers" group chat on Discord was that we must redo much of the @dbuzz Dapp in favor of Buzz’s *(our version of Posts)* being published in the Comment section of people’s Profiles instead of the Posts section.

Besides delaying our project launch by a couple weeks at minimum, @nathansenn *(Lead Investor / Blockchain Developer)* had this to say about that idea.

> By making all posts in [D.Buzz](https://d.buzz) comments on a post inside our community, we lose the neatness of having many posts from different users inside our community on other platforms such as [Hive.Blog](https://hive.blog).

> We also lose the Trending features that are built into the communities.

> I am also concerned that opportunists would take advantage of the lack of posts in our community. To try to post garbage or other spammy, scammy types of posts in hopes that it would be seen by someone viewing our community on other platforms due to the lack of posts in the main feed.

> We want people to use our Dapp on [D.Buzz](https://d.buzz) but also want people to be able to interact with it on other platforms such as @peakd and [Hive.Blog](https://hive.blog).

> The mechanics of doing it through the comment route feels a bit like jerry-rigging our Dapp to adhere to some unwritten protocols instead of using the current protocols that are currently the standards for communities.

> I think if the Hive community wants social media Dapps but is concerned about the reward pool abuse, a protocol change needs to be made at the Hive blockchain level where posts made to the chain would be given a type such as Blog, Video, Image, Short-form, etc. The rewards for short-form posts and other types of social media posts of the likes could have adjusted rewards. 

> My last concern is that if we decide to use comments for posts, people will build bots to upvote comments as the Dapp becomes more popular, defeating the entire purpose.

> Our team is open to changing to use comments for the post made on our Dapp but do not feel that this is the best way to do this.

> The community wants a social media platform such as [D.Buzz](https://d.buzz).. the question is, how do we work at making social media Dapps on HIVE and prevent reward pool abuse? 

In light of this, we are proposing that @blocktrades make a change to the HIVE blockchain that separates each post into categories such as but not limited to: 

1. Blog
2. Image
3. Video
4. Short-form

If you are in favor of this proposal please [vote for it here](https://peakd.com/proposal/@dbuzz/proposal-to-change-usdhive-at-the-blockchain-level).. the funds will be sent to @blocktrades if approved.

<hr>

**ABOUT OUR LAUNCH:**

We will be launching [D.Buzz](https://d.buzz) this week w/Rewards set to Decline for all of our users. This temporary status *(one week)* of declined rewards is intended to promote public discourse so that we can eventually activate rewards without risking public backlash and heavy downvotes from curation groups and abuse fighters such as @hivewatchers. Please let us know in the comments if you think:

1. We should extend the Decline Rewards for @dbuzz users for another week after the 1st one expires.

2. We should activate rewards after the 1st week of Declining Rewards is over.

3. Give us feedback w/different ideas.

Again, be sure to vote on our proposal if you think policies should be written at the blockchain level and that @nathansenn’s suggestion would help onboard the masses via additional social media Dapps like [D.Buzz](https://d.buzz) joining the HIVE blockchain.

**P.S.** Contact chrisrice#2989 on [our Discord](https://discord.gg/4UWq5XB) if you want to discuss this with @nathansenn via audio or video. He is open to interviews and can discuss this in a public forum.

<center>**[VOTE FOR THE PROPOSAL HERE | CLICK HERE](https://peakd.com/proposal/@dbuzz/proposal-to-change-usdhive-at-the-blockchain-level)**</center>
πŸ‘  , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , and 260 others
πŸ‘Ž  , ,
properties (23)
authordbuzz
permlinkproposal-to-change-usdhive-at-the-blockchain-level
categoryproposal
json_metadata"{"app":"hiveblog/0.1","description":"Proposal to Change HIVE at the Blockchain Level","format":"markdown","image":["https://images.hive.blog/DQmSBeMttYH28s3DskMLtosJxx2N3roPPBkBszQhmggAV6C/HIveChainMatters_promo.png"],"links":["https://hive.blog/hive/@dbuzz/a-microblogging-platform-is-launching-soon-hive","https://d.buzz","https://hive.blog","https://peakd.com/proposal/@dbuzz/proposal-to-change-usdhive-at-the-blockchain-level","https://discord.gg/4UWq5XB"],"tags":["hive","dapp","dbuzz","news","dev"],"users":["jonsnow1983","trincowski","ash","jocieprosza","belemo","joanstewart","chrisrice","dbuzz","hiddenblade","guiltyparties","hivewatchers","nathansenn","peakd","blocktrades"]}"
created2020-05-17 11:21:09
last_update2020-05-17 13:06:12
depth0
children41
last_payout2020-05-24 11:21: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_length4,699
author_reputation276,817,987,330,091
root_title"Proposal to Change $HIVE at the Blockchain Level"
beneficiaries
0.
accountnull
weight10,000
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id97,422,807
net_rshares-1,311,313,967,626
author_curate_reward""
vote details (327)
@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)
@cryptoctopus ·
$0.14
HECK yeah. I think this is a much better approach than trying to hack it. I want DHive to win and it shouldn't be penalized by the format that you use.
πŸ‘  
properties (23)
authorcryptoctopus
permlinkre-dbuzz-qan28y
categoryproposal
json_metadata{"tags":["proposal"],"app":"peakd/2020.05.4"}
created2020-05-20 16:39:09
last_update2020-05-20 16:39:09
depth1
children1
last_payout2020-05-27 16:39:09
cashout_time1969-12-31 23:59:59
total_payout_value0.070 HBD
curator_payout_value0.070 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length151
author_reputation365,406,972,531,657
root_title"Proposal to Change $HIVE at the Blockchain Level"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id97,488,605
net_rshares465,090,528,730
author_curate_reward""
vote details (1)
@chrisrice ·
> HECK yeah. I think this is a much better approach than trying to hack it.

Thanks @crytpoctopus, I hope other people will see that too!
properties (22)
authorchrisrice
permlinkqao8gl
categoryproposal
json_metadata{"users":["crytpoctopus"],"app":"hiveblog/0.1"}
created2020-05-21 07:50:45
last_update2020-05-21 07:50:45
depth2
children0
last_payout2020-05-28 07:50: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_length137
author_reputation70,462,754,167,857
root_title"Proposal to Change $HIVE at the Blockchain Level"
beneficiaries[]
max_accepted_payout0.000 HBD
percent_hbd10,000
post_id97,499,880
net_rshares0
@enjar ·
Trying to get a change at the blockchain level sounds like it would delay this by quite a few months as who knows how long that would take if it was even accepted by the community to do in the first place. As that sounds like it would require a hardfork so could that even be doing by the end of this year?


I personally would prefer just using a second account.  Regardless if there was a limit on post rewards or not if you are going that route. 


While at first I thought β€œwhy not just make them all comments or give an option to make Tweets comments instead.” I would agree it be limiting the growth of this project if they could only comments. 

I do sometimes wish if I was commenting on a Tweet that had a Hive link that it would auto post it to the blockchain as a comment on that post for me.   
properties (22)
authorenjar
permlinkre-dbuzz-qahdai
categoryproposal
json_metadata{"tags":["proposal"],"app":"peakd/2020.05.3"}
created2020-05-17 14:51:57
last_update2020-05-17 14:51:57
depth1
children1
last_payout2020-05-24 14:51:57
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_length807
author_reputation1,194,215,908,550,676
root_title"Proposal to Change $HIVE at the Blockchain Level"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id97,425,777
net_rshares0
@chrisrice ·
$0.13
Thanks for the support @enjar.

I wanted to add that @nathansenn just pointed out a fatal flaw of @holger08's idea of using the max_payout features to prevent abuse and limit payouts.

> @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 get some people's attention so that this can be solved once and for all.
πŸ‘  
properties (23)
authorchrisrice
permlinkqaixqs
categoryproposal
json_metadata{"users":["enjar","nathansenn","holger08","holdger08","peakd"],"app":"hiveblog/0.1"}
created2020-05-18 11:11:18
last_update2020-05-18 11:11:18
depth2
children0
last_payout2020-05-25 11:11:18
cashout_time1969-12-31 23:59:59
total_payout_value0.064 HBD
curator_payout_value0.064 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length783
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,914
net_rshares403,868,542,092
author_curate_reward""
vote details (1)
@hiddenblade ·
$0.07
The best option that I could think of so far is posting the buzzes as **comments** and not posts. Just like how @anonramblingscom posts a [daily placeholder](https://peakd.com/hive-116328/@anonramblingscom/ramblings-2020-05-16) and all buzzes will be posted as comments. It will pretty much look like a mess while using peakd or hive.blog but the good thing there is that people will use Dbuzz more often.

> I am also concerned that opportunists would take advantage of the lack of posts in our community. To try to post garbage or other spammy, scammy types of posts

There's always gonna be spammers. All you could do is mute them after warnings. 

> I think if the Hive community wants social media Dapps but is concerned about the reward pool abuse, a protocol change needs to be made at the Hive blockchain level

I disagree with this one. There are several short posts that I see that I think deserve the rewards. This could be a one-photo post or a video with less text. Or one-liner text that received a lot of engagements. The *length* of a post doesn't define the *quality* of it. We can't limit the rewards for short-form posts (in general) on a blockchain level just to adjust to a new dapp as it would seem unfair and would sound like it will defeat the purpose of the blockchain.


I could say limiting payouts that are posted on Dbuzz is okay, but there's no need to do it on a blockchain level as still, quality is subjective.


> My last concern is that if we decide to use comments for posts, people will build bots to upvote comments as the Dapp becomes more popular, defeating the entire purpose.

Abusers are always there and they will always make a bot for that. If they want to abuse, they will always do what they can to abuse. My suggestion would be: have something like a section where you could see **trending buzzes based on payouts** and the community can decide to give them downvotes or not.

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

The **trending buzzes based on payouts** could probably solve this. 

Or those adjustments could probably be made specifically in the Dbuzz community? So whether they use hive.blog or peakd it will be applied when it's posted there. I'm not sure if that's possible though.
πŸ‘  ,
properties (23)
authorhiddenblade
permlinkre-dbuzz-qaj4db
categoryproposal
json_metadata{"tags":["proposal"],"app":"peakd/2020.05.3"}
created2020-05-18 13:34:24
last_update2020-05-18 13:34:24
depth1
children0
last_payout2020-05-25 13:34:24
cashout_time1969-12-31 23:59:59
total_payout_value0.034 HBD
curator_payout_value0.034 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length2,402
author_reputation1,166,838,449,645,348
root_title"Proposal to Change $HIVE at the Blockchain Level"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id97,445,714
net_rshares221,492,588,154
author_curate_reward""
vote details (2)
@hivebuzz ·
Congratulations @dbuzz! You have completed the following achievement on the Hive blockchain and have been rewarded with new badge(s) :

<table><tr><td><img src="https://images.hive.blog/60x70/http://hivebuzz.me/@dbuzz/upvotes.png?202005191117"></td><td>You distributed more than 200 upvotes. Your next target is to reach 300 upvotes.</td></tr>
</table>

<sub>_You can view [your badges on your board](https://hivebuzz.me/@dbuzz) and compare to others on the [Ranking](https://hivebuzz.me/ranking)_</sub>
<sub>_If you no longer want to receive notifications, reply to this comment with the word_ `STOP`</sub>



**Do not miss the last post from @hivebuzz:**
<table><tr><td><a href="/hivebuzz/@hivebuzz/proposal-2020"><img src="https://images.hive.blog/64x128/https://i.imgur.com/qYidoDJ.jpg"></a></td><td><a href="/hivebuzz/@hivebuzz/proposal-2020">The Hive Gamification Proposal</a></td></tr></table>

###### Support the HiveBuzz project. [Vote for our proposal](https://hivesigner.com/sign/update_proposal_votes?proposal_ids=%5B%22109%22%5D&approve=true)!
properties (22)
authorhivebuzz
permlinkhivebuzz-notify-dbuzz-20200519t112107000z
categoryproposal
json_metadata{"image":["http://hivebuzz.me/notify.t6.png"]}
created2020-05-19 11:21:06
last_update2020-05-19 11:21:06
depth1
children0
last_payout2020-05-26 11:21: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_length1,056
author_reputation369,400,627,179,138
root_title"Proposal to Change $HIVE at the Blockchain Level"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id97,464,630
net_rshares0
@holger80 ·
$1.18
I think there is no need to modify the Hive at the blockchain level as there is `max_accepted_payout`. This parameter can be set between 0 and  1000000 HBD.

For short-form content, this parameter could be set to 1-5 HBD and the post payout will not exceed this. Everything above this threshold will be returned to the reward pool.

You can see here how it looks when the parameter set to 1 HBD:
https://peakd.com/hive-174578/@abitcoinskeptic/experimenting-with-max-accepted-payout

When auto voters are checking this parameter, it can be used to mark a post as short-form content.
πŸ‘  , , , , , , , , , ,
properties (23)
authorholger80
permlinkre-dbuzz-qah473
categoryproposal
json_metadata{"tags":["proposal"],"app":"peakd/2020.05.3"}
created2020-05-17 11:35:30
last_update2020-05-17 11:35:30
depth1
children19
last_payout2020-05-24 11:35:30
cashout_time1969-12-31 23:59:59
total_payout_value0.592 HBD
curator_payout_value0.589 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length581
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,423,013
net_rshares3,029,385,659,314
author_curate_reward""
vote details (11)
@brianoflondon ·
This sounds excellent. 
properties (22)
authorbrianoflondon
permlinkre-holger80-qah6bj
categoryproposal
json_metadata{"tags":["proposal"],"app":"peakd/2020.05.3"}
created2020-05-17 12:21:21
last_update2020-05-17 12:21:21
depth2
children1
last_payout2020-05-24 12:21:21
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_length23
author_reputation760,626,613,375,672
root_title"Proposal to Change $HIVE at the Blockchain Level"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id97,423,634
net_rshares0
@chrisrice · (edited)
$0.04
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 bring attention to this proposal.. I think it's the only fix and a much needed one at that. Otherwise Dapps like us would also be forced to get involved in politics and in vain when the solution really lies in solving this at the blockchain level @brianoflondon.
πŸ‘  ,
properties (23)
authorchrisrice
permlinkqahesh
categoryproposal
json_metadata{"app":"hiveblog/0.1","users":["nathansenn","holdger08","peakd","brianoflondon"]}
created2020-05-17 15:24:18
last_update2020-05-18 11:22:18
depth3
children0
last_payout2020-05-24 15:24:18
cashout_time1969-12-31 23:59:59
total_payout_value0.018 HBD
curator_payout_value0.018 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length864
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,426,350
net_rshares120,691,512,456
author_curate_reward""
vote details (2)
@chrisrice ·
$0.15
@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 review the proposal above and the issue more in-depth and comment accordingly @holger08.
πŸ‘  ,
properties (23)
authorchrisrice
permlinkqaiwzh
categoryproposal
json_metadata{"users":["nathansenn","holdger08","peakd","holger08"],"app":"hiveblog/0.1"}
created2020-05-18 10:54:57
last_update2020-05-18 10:54:57
depth2
children11
last_payout2020-05-25 10:54:57
cashout_time1969-12-31 23:59:59
total_payout_value0.074 HBD
curator_payout_value0.074 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length600
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,681
net_rshares466,238,844,404
author_curate_reward""
vote details (2)
@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)
@jarvie ·
Communities allow moderation what's the concern?
Check the post see if it has a max_payout if it doesn't ... mute it. 

properties (22)
authorjarvie
permlinkre-chrisrice-qaj87l
categoryproposal
json_metadata{"tags":["proposal"],"app":"peakd/2020.05.3"}
created2020-05-18 14:57:24
last_update2020-05-18 14:57:24
depth3
children0
last_payout2020-05-25 14:57:24
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_length120
author_reputation388,491,264,112,133
root_title"Proposal to Change $HIVE at the Blockchain Level"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id97,447,081
net_rshares0
@markkujantunen ·
Exactly. 
properties (22)
authormarkkujantunen
permlinkre-holger80-qah4fa
categoryproposal
json_metadata{"tags":["proposal"],"app":"peakd/2020.05.3"}
created2020-05-17 11:40:21
last_update2020-05-17 11:40:21
depth2
children1
last_payout2020-05-24 11:40:21
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_length9
author_reputation625,120,192,577,442
root_title"Proposal to Change $HIVE at the Blockchain Level"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id97,423,070
net_rshares0
@chrisrice ·
$0.14
There is a major flaw in trying to use the max_payout to solve this problem.

> 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 review the proposal above and the issue more in-depth and comment accordingly @holger08.
πŸ‘  
properties (23)
authorchrisrice
permlinkqaix7y
categoryproposal
json_metadata{"users":["peakd","holger08"],"app":"hiveblog/0.1"}
created2020-05-18 11:00:12
last_update2020-05-18 11:00:12
depth3
children0
last_payout2020-05-25 11:00:12
cashout_time1969-12-31 23:59:59
total_payout_value0.071 HBD
curator_payout_value0.071 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length602
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,739
net_rshares446,712,632,631
author_curate_reward""
vote details (1)
@vimukthi ·
This is what I was about to type in when I read the proposal.
properties (22)
authorvimukthi
permlinkre-holger80-qahe2m
categoryproposal
json_metadata{"tags":["proposal"],"app":"peakd/2020.05.3"}
created2020-05-17 15:08:48
last_update2020-05-17 15:08:48
depth2
children2
last_payout2020-05-24 15:08:48
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_length61
author_reputation496,987,053,967,294
root_title"Proposal to Change $HIVE at the Blockchain Level"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id97,426,086
net_rshares0
@chrisrice ·
Thank you for also sharing, and for being in favor of using the max_payout feature to prevent abuse.

> Your feedback helps!
πŸ‘  
properties (23)
authorchrisrice
permlinkqahera
categoryproposal
json_metadata{"app":"hiveblog/0.1"}
created2020-05-17 15:23:36
last_update2020-05-17 15:23:36
depth3
children0
last_payout2020-05-24 15:23:36
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_length124
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,426,340
net_rshares41,730,528,035
author_curate_reward""
vote details (1)
@chrisrice ·
$0.14
It seems like the max_payout would work, but it wouldn't and here's why:

> 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 consider the above scenario and comment / share accordingly.
πŸ‘  
properties (23)
authorchrisrice
permlinkqaixbd
categoryproposal
json_metadata{"users":["peakd"],"app":"hiveblog/0.1"}
created2020-05-18 11:02:03
last_update2020-05-18 11:02:03
depth3
children0
last_payout2020-05-25 11:02:03
cashout_time1969-12-31 23:59:59
total_payout_value0.069 HBD
curator_payout_value0.070 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length568
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,769
net_rshares437,799,990,976
author_curate_reward""
vote details (1)
@mytechtrail ·
$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.
πŸ‘  
properties (23)
authormytechtrail
permlinkre-dbuzz-qahr6y
categoryproposal
json_metadata{"tags":["proposal"],"app":"peakd/2020.05.3"}
created2020-05-17 19:52:09
last_update2020-05-17 19:52:09
depth1
children2
last_payout2020-05-24 19:52:09
cashout_time1969-12-31 23:59:59
total_payout_value0.062 HBD
curator_payout_value0.063 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length132
author_reputation19,007,675,085,002
root_title"Proposal to Change $HIVE at the Blockchain Level"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id97,430,725
net_rshares395,799,861,678
author_curate_reward""
vote details (1)
@chrisrice ·
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)
authorchrisrice
permlinkqaixsy
categoryproposal
json_metadata{"users":["nathansenn","holdger08","peakd"],"app":"hiveblog/0.1"}
created2020-05-18 11:12:36
last_update2020-05-18 11:12:36
depth2
children1
last_payout2020-05-25 11:12:36
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_length743
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,932
net_rshares0
@mytechtrail ·
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)
authormytechtrail
permlinkre-chrisrice-qajnq4
categoryproposal
json_metadata{"tags":["proposal"],"app":"peakd/2020.05.3"}
created2020-05-18 20:32:27
last_update2020-05-18 20:32:27
depth3
children0
last_payout2020-05-25 20:32:27
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_length344
author_reputation19,007,675,085,002
root_title"Proposal to Change $HIVE at the Blockchain Level"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id97,452,770
net_rshares0
@nathansenn ·
$0.56
max_payout feature would only be affective if they used in our front-end anyone using other platforms we would not be required to set max_payout. 
πŸ‘  , ,
properties (23)
authornathansenn
permlinkre-dbuzz-qai0l5
categoryproposal
json_metadata{"tags":["proposal"],"app":"peakd/2020.05.3"}
created2020-05-17 23:15:06
last_update2020-05-17 23:15:06
depth1
children0
last_payout2020-05-24 23:15:06
cashout_time1969-12-31 23:59:59
total_payout_value0.378 HBD
curator_payout_value0.186 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length146
author_reputation30,713,653,158,658
root_title"Proposal to Change $HIVE at the Blockchain Level"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id97,434,740
net_rshares2,076,593,069,963
author_curate_reward""
vote details (3)
@rishi556 ·
Will you guys have keychain support as well? I hate giving authority when keychain can do the job.
properties (22)
authorrishi556
permlinkre-dbuzz-qalid1
categoryproposal
json_metadata{"tags":["proposal"],"app":"peakd/2020.05.3"}
created2020-05-19 20:31:48
last_update2020-05-19 20:31:48
depth1
children1
last_payout2020-05-26 20:31:48
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_length98
author_reputation132,754,869,222,673
root_title"Proposal to Change $HIVE at the Blockchain Level"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id97,472,870
net_rshares0
@chrisrice ·
Yes, we will :)
properties (22)
authorchrisrice
permlinkqao8f8
categoryproposal
json_metadata{"app":"hiveblog/0.1"}
created2020-05-21 07:49:57
last_update2020-05-21 07:49:57
depth2
children0
last_payout2020-05-28 07:49:57
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_length15
author_reputation70,462,754,167,857
root_title"Proposal to Change $HIVE at the Blockchain Level"
beneficiaries[]
max_accepted_payout0.000 HBD
percent_hbd10,000
post_id97,499,870
net_rshares0
@shmoogleosukami ·
$0.12
I personally feel that you should be able to do as you please. That being said after reading some comments I would say using max_payout is the most logical solution to mitigate abuse at the moment, just so as you mention it when people post just they know what to expect.

The problem is what is an acceptable payout for shortform content? It's entirely subjective. Personally I feel up to $10-15 seems fine. 
πŸ‘  
properties (23)
authorshmoogleosukami
permlinkre-dbuzz-qahz3f
categoryproposal
json_metadata{"tags":["proposal"],"app":"peakd/2020.05.3"}
created2020-05-17 22:42:51
last_update2020-05-17 22:42:51
depth1
children2
last_payout2020-05-24 22:42:51
cashout_time1969-12-31 23:59:59
total_payout_value0.060 HBD
curator_payout_value0.061 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length410
author_reputation226,056,535,436,402
root_title"Proposal to Change $HIVE at the Blockchain Level"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id97,434,177
net_rshares387,941,007,011
author_curate_reward""
vote details (1)
@chrisrice ·
@nathansenn just pointed out something and he's right . . the max_accepted_payout route would not work as @holger08 intends.

**Here's what would happen:**

> @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 are being asked to play politics when the solution is a change at the blockchain level, not limiting ourselves in ways that are not coded into the blockchain.
πŸ‘  
properties (23)
authorchrisrice
permlinkqaixwi
categoryproposal
json_metadata{"users":["nathansenn","holger08","holdger08","peakd"],"app":"hiveblog/0.1"}
created2020-05-18 11:14:45
last_update2020-05-18 11:14:45
depth2
children1
last_payout2020-05-25 11:14: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_length873
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,957
net_rshares40,010,382,843
author_curate_reward""
vote details (1)
@shmoogleosukami ·
Ahh yeah that's definitely a problem. Looks like the only route at this time is protocal change or people just accept the fact that if they want dapps they have to accept the way they do things or change the blockchain to suit.

I'll vote for the proposal in this case as this'll help more than just this dapp.<div class="pull-right"><a href="/@hive.engage">![](https://i.imgur.com/XsrNmcl.png)</a></div>
properties (22)
authorshmoogleosukami
permlinkre-qaixwi
categoryproposal
json_metadata{"app":"engage"}
created2020-05-18 12:00:24
last_update2020-05-18 12:00:24
depth3
children0
last_payout2020-05-25 12:00:24
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_length404
author_reputation226,056,535,436,402
root_title"Proposal to Change $HIVE at the Blockchain Level"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id97,444,529
net_rshares0
@trincowski ·
$0.13
Thanks for the mention. 

Yes, I fear that such a platform can lead to a lot of unnecessary spam... but posting on the comments? I don't think it's the way to proceed as well. That would be unfair. Freedom should be the main thing in this platform...

Maybe we should simply allow the community to deal with those posts as they see fit. We already have tools like downvotes, limits to maximum rewards per post, declining payouts... 

... and I'm sure it would be simple enough to change Hive Vote to ignore such posts... (@mahdiyari, @steemauto, is this possible?)

Thanks for taking in consideration my concerns.
πŸ‘  
properties (23)
authortrincowski
permlinkre-dbuzz-2020517t124944917z
categoryproposal
json_metadata{"tags":["proposal","hive","dapp","dbuzz","news","dev"],"app":"esteem/2.2.5-mobile","format":"markdown+html","community":"hive-125125"}
created2020-05-17 11:49:45
last_update2020-05-17 11:49:45
depth1
children2
last_payout2020-05-24 11:49:45
cashout_time1969-12-31 23:59:59
total_payout_value0.065 HBD
curator_payout_value0.067 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length613
author_reputation159,418,145,168,851
root_title"Proposal to Change $HIVE at the Blockchain Level"
beneficiaries
0.
accountesteemapp
weight300
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id97,423,209
net_rshares420,486,649,460
author_curate_reward""
vote details (1)
@chrisrice ·
$0.14
I just realized that @nathansenn is right.. the max_payout route won't work, at least as it is now:

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

We are being told to fall in line with a political system when a fix at the blockchain level would fix this once and for all.. with the max_payout code as it is now, the solution mentioned by @holger08 would NOT work.

Hopefully the Community and stakeholders will come together to solve this once and for all, so that other DAPPs like ours can start building on $HIVE.
πŸ‘  
properties (23)
authorchrisrice
permlinkqaixj0
categoryproposal
json_metadata{"users":["nathansenn","peakd","holger08"],"app":"hiveblog/0.1"}
created2020-05-18 11:06:39
last_update2020-05-18 11:06:39
depth2
children0
last_payout2020-05-25 11:06:39
cashout_time1969-12-31 23:59:59
total_payout_value0.068 HBD
curator_payout_value0.068 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length897
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,831
net_rshares429,059,141,870
author_curate_reward""
vote details (1)
@chrisrice ·
> Yes, I fear that such a platform can lead to a lot of unnecessary spam... but posting on the comments? I don't think it's the way to proceed as well. That would be unfair. Freedom should be the main thing in this platform...

Yeah, and in the end, @nathansenn thinks it wouldn't even solve the problem since bots would be created to also upvote comments if our DAPP became successful enough.

> Maybe we should simply allow the community to deal with those posts as they see fit. We already have tools like downvotes, limits to maximum rewards per post, declining payouts...

Yeah, mamximum rewards per post would probably help a lot.. I am glad you are in favor of using that.

> ... and I'm sure it would be simple enough to change Hive Vote to ignore such posts... (@mahdiyari, @steemauto, is this possible?)

I contacted @mahdiyari via Discord and he was against it. Maybe he will change his mind though.

> Thanks for taking in consideration my concerns.

You're welcome.. we are here to create value, not damage the value that is already here.
properties (22)
authorchrisrice
permlinkre-trincowski-qah6cv
categoryproposal
json_metadata{"tags":["proposal"],"app":"peakd/2020.05.3"}
created2020-05-17 12:22:09
last_update2020-05-17 12:22:09
depth2
children0
last_payout2020-05-24 12:22: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_length1,051
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,423,639
net_rshares0