You are viewing a single comment's thread from:

RE: HF20 Update: Restoring Continuity

in #steem6 years ago (edited)

I like the idea, but I think it would be nicer to implement such a way of dealing with the RC in a built-in method (managed by the network code, or witnesses). And have let's say a flag you could broadcast, to enable/disable others using your RC (and maybe auto-activate for account inactive for more than... X amount of time). In return, a small percentage of the reward will revert to the RC share poolers (users that wish to share their RC). A limit of RC to share should also be implemented, to avoid locking up accounts (let's say, we could say that I am willing to participate with RC up to 50%, and after that, I would need to wait for recharge). This last bit might be very hard to implement, I am guessing.

The reason I believe it to be best as a built-in property of the blockchain code, is to reduce or avoid gaming situations of price manipulation. And it would allow the entire accounting ecosystem of steem to be used as a resource pool. This will greatly create competition for whales and following investors. But most importantly, this will give or greatly increase the opportunity for minnows to participate with very low bandwidth, more often.

To create an incentive for users to NOT use the system as a reward mechanism ONLY (and kill the network interactivity), the above pool would be consumed in a product of the percentage of each RC for the amount of account inactivity. Meaning that for all inactive accounts, the RC share would be much higher and would unfavour whales to become inactive for the exploitation of the RC share (since the reward of using accounts would be much higher than becoming inactive to grab higher RC).

Really nice discussion.