RE: Proposal to Change $HIVE 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

Comments

[chrisrice]

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.

[dbuzz]

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.