What is the point of $HIVE rewards?
To spread the blockchain's governance token and thus keep the chain decentralised.
There is ZERO link between the value of content and HIVE rewards.
HIVE only has value because the blockchain is decentralised and thus censorship-resistant.
All that matters is that the token goes out far and wide.
Spam is encouraged by the blockchain itself.
To me, it's a no-brainer that $LEO will consistently be worth more than $HIVE.
LEO is tied to revenue, while HIVE is purely speculative.
So once LEO shows that real revenue can be generated by content, and sustainably buy/burn the token they are printing to pay for it, HIVE rewards will become nothing more than what they are intended to be...
The point of rewards is to incentivise quality content. The theory goes that the better your content, the more followers and upvotes and therefore more rewards you get.
What is the point of layer-2 rewards like $LEO?
To incentivise the creation of valuable content.
By monetising content at the domain level, revenue can be used to buy/burn LEO for sustainability.
Thanks to layer-2 tokens, authors are incentivised to create content that makes money and curators to reward it.
Thus fixing the spam problem for HIVE rewards.
Does it work perfectly? No, but nothing does. I think it works more than it doesn't though.
The more stake you have, the more incentive you have to curate to ensure quality content which attracts users and increases value. The downvote is to discourage spam.
The DPoS governance token that keeps the base layer decentralised and therefore censorship-resistant.
Keep blockchain rewards as they are and focus on generating value on layer-2.
@darth-azrael, there is no link between quality content and the value of HIVE.
None at all.
The Hive blockchain does not care about the content itself.
Only that it is there.
The point of blockchain rewards is to spread the blockchain's governance token because decentralisation is what actually gives $HIVE value.
Quality content is not the blockchain's problem at all.
It is the problem of each privately owned front-end.