Now before I begin I want to acknowledge that I'm not against tokens, I think some have some value and as long as they encourage people to use Hive in many ways it's great. The current "band-aid" version of how they get distributed, though, leads to certain posts becoming filled with spam comments by bots and people using them making it close to impossible for people to read and find the real comments in. This idea will touch on how this issue could be fixed without removing the idea behind how the tokens work and maybe even improve it, though it might require quite a lot of work from both front-ends and maybe the hive-engine contracts and how they operate. I wouldn't post about it if I didn't think it'd be worth it though and maybe someone could help me out by looking at the idea from a dev perspective to tell me how feasible it is.

The way I understand it, many use a similar contract like the old ENGAGE token created by @abh12345, you like how engaging someone is being in the comment section, you leave them a reply and a command to distribute 1 ENGAGE token to them, the bot replies under your reply that the token was distributed successfully, it's all nice. The issue comes when people are out there farming these, every comment has a command, every reply has a command every next reply has a command, the next person to comment also uses 1 if not many different commands all summoning these bot replies to leave a comment confirming their transaction went through, etc. This makes the post filled with these bot comments, some times up to 80%+ only existing of these bot comments.

Now while not all bot comments are "bad" it makes it hard to get through to the real comments, readers have to sift through many of these bot comments and the author or other readers curating the real comments isn't going to help much when the bots reply with a command underneath genuine comments if they're also using the token distribution commands within them. 

A possible solution: 

The idea here would be to remove the need for these token distributions to have to leave a reply confirming the success of the transaction. We need a way for the distributor to leave a command or in a different way distribute the token he wishes while being able to confirm if it went through or not without a bot responding to the comment. 

My solution would require input and work from both the front-end and the token contract to adjust to the new way.

Token distribution through "award icons" similar to Reddit awards: 


![image.png](https://files.peakd.com/file/peakd-hive/acidyo/23tkjvBAwrgNG366pjBTDH5sAPaVxcEZnfD5jYTZaVmCcTwSP3f3Wo2smQeDko9mZPF7a.png)

@peakd and maybe even hive.blog/@ecency already offers readers to tip posts and comments, these tips go through a certain tipu service that registers them to visibly show a tip has been sent towards this particular post/comment and from who.

Similarly, tokens people are interested in to distribute could sign up to have their icons/logos whitelisted for the front-ends and through a tipping method they could leave a tip towards a post or comment. They could still continue to leave a command for possible marketing/awareness of the token and it would have the same effect. 

You could now instead see posts with 5x pizza rewards from various commenters or readers, so this would also include readers to participate without being forced to leave a comment that just includes the token distribution command. Then there could be other icon's next to the post from different tokens as well similar to the screenshot above, all showing the amount of tokens a post received and mouseover maybe even view the value or info about where to read more about the token. 

This would remove the need for the bots to drop confirmation replies completely as people could just refresh to see if the icon appeared or not if they've depleted the amount of token distributions for that day or don't have any stake to distribute them (however they work exactly) thus removing "spam" comments completely. 

Now all said I haven't thought this through 100%, just presenting an idea and I'd appreciate some more dev perspectives, but I quickly pointed it out to a couple and they believed it could be viable. 

The commands and tip input could instead generate a custom json transaction that the token distributor would be signaled by rather than relying on comments.

Anyhow, I'd appreciate your thoughts on this idea and if it would be worth changing the way things work right now for better user experience and readability. 

https://images.hive.blog/0x0/https://files.peakd.com/file/peakd-hive/acidyo/23xKmtx2stpKP9Z7FKWJm6oDohuHxVtHKHQCUx6Fs8rDT65jB1FfvZ1xKByyeb3N1874c.png