You are viewing a single comment's thread from:

RE: Proposed Upgrade for Blockchain Incentives

in #steem7 years ago

I think it seems like a good direction to head in, and I applaud the effort to expand the use of the Steem blockchain and currency.

I think the idea of having different reward structures for different types of content is an excellent idea!

I'm not quite sure about the domain and service provider receiving a share of the rewards. I understand companies need to make a profit, and it is a good incentive to encourage adoption - so I am not opposed to it, but I would need to know more details about how it would work before I would be fully on board with the idea.

One question I have which I think is crucial to expanding to more of a distributed implementation across multiple platforms is how will security be handled? Will users have to plug their private keys into third party websites in order to use the Steem functions there? Even if they only need the private posting key, having users sharing this with tons of third party sites could be a huge drawback.

Sort:  

I'm not quite sure about the domain and service provider receiving a share of the rewards. I understand companies need to make a profit, and it is a good incentive to encourage adoption - so I am not opposed to it, but I would need to know more details about how it would work before I would be fully on board with the idea.

The website that a post or comment is created inside of would be able to dictate the % cut that goes to the posters and or commenters. For instance Zerohedge could give a % of STEEM rewards to their authors while taking a percentage for posting the link to the ZH article. As another example, the commenters posting through a Steem-Disqus would be given a % while Steem-'scus could also take a %. And like Steemit exists now, some platforms could always give 100% of Steem rewards to the poster/commenter.

Ok. So basically each interface could define how the rewards for posts/comments in their domain would be allocated. That makes sense. Thanks for the explanation!

This is why most blogs would opt to use a trusted provider like steemit.com and use an iframe to host comments.

It should be easy enough to have a "key per provider" so that you know which provider was hacked.

Revocable delegate keys would enable this, it also helps with curation guilds, per app passwords like Google has. And you could add later secret share keys that enable an x of y override key for such as death, coma and other forms of becoming legally incompetent (Facebook has something like this since so many users had died...).

It may be worth considering updates to the private keys to allow users to place additional restrictions on what individual posting keys are allowed to do. For example restricting the domain that they can interact in. If there was also a way to force the external sites to use a separate key, that would probably be good too. This would greatly reduce the risk of malicious third party sites taking advantage of users private keys.

Exactly!

But I would be against of forcing a user to dealing with all those keys, because for average users those things are already really complicated and new. What do you think about concept of slaves accounts: https://steemit.com/steem/@steemitblog/proposed-upgrade-for-blockchain-incentives#@noisy/re-timcliff-re-noisy-re-steemitblog-proposed-upgrade-for-blockchain-incentives-20161119t122443054z

Coin Marketplace

STEEM 0.24
TRX 0.11
JST 0.032
BTC 62661.87
USDT 1.00
SBD 3.76