Now that I have solved the puzzle of how to have our bot generate hot signing links as replies as part of our abuse report approval process, it's time to map out the next steps.
- Implement function for bot to lookup the transaction by tx id for verification purposes.
In lieu of requiring the bot constantly listen to the chain, the more efficient approach imo is to have the user that reported the abuse reply with the transaction ID in the body of the comment. This will minimize our utilization of Hive public RPC nodes and eliminate the need to have another thread or process running.
Once the transaction is confirmed, the abuse report will be submitted under our periodic report post as a comment for the community approval phase with the abuse reporter set as beneficiary. The requirement for community approval is for the comment payout to exceed slightly over minimum payout value.
Votes will be monitored and, once the minimum threshold is achieved, the abuse report is deemed approved for negative curation and entry is written to the internal database. This entry will include the post payout time to be tracked.
- Trigger once reported content reaches payout
Once the reported post reaches payout, the bot will query all downvotes for HDR token rewards.
- Reward Distribution Algorithm
This part will be a bit of a beast as there is a lot to consider and I know we have discussed it a bit. My goal is to design a distribution algorithm that is fair to delegators allowing them to put their free downvotes to good use via community moderation and be rewarded for the activity. Moreover, it should be designed so that we do not overutilize the bot's voting power while also being efficient. In other words, write more checks than we are able to cash.
The general idea will be to slot out a sort of regenerating mana based on the bot's voting power and use that as a factor in the reward calculation which will be tabulated as the reported content pays out.
That is the game plan
Let me know what you think!