The most basic operational form of our token distribution bot is a discourse theme component which
- scrapes posts tagged ‘done’ every two weeks and records which users were assigned to that post
- collects users stats for their contributions to our ecosystem. This means posts and comments made. Hearts received. (fortunately Discourse already does this out of the box, so its just a slight modification to what’s already happening)
- collects users trust level and uses that as a multiplier of their final score
If the tasks listed ‘done’ have no-one assigned it auto-messages beneath requesting they assign the task to themselves in order to receive their tokens.
After the token claiming message has been sent the bot then deletes the ‘done’ tag and adds a ‘legacy’ tag.
Every 2 weeks the bot sends users a message containing a link to a faucet where they can claim their tokens.
The faucet is set up to release tokens every two weeks (like a standard faucet), but then refers to the users score in our database/spreadsheet to determine how much to give them as a percentage of the overall score of all users.
For example, if we release 10,000 tokens and the user has a score for the past 2 weeks of 200, while all users that week have an accumulated score of 10,000. The user would receive 2% of the total tokens released
If you have experience in, or want to set up a link to Metamask then please let me know as that would take the bot to the next stage.
Security isn’t too important at this point as the account the tokens are sent from will not be the main vault and will only contain enough for that period, which means any hack would not be catastrophic and the incentive fairly small given the tokens likely nominal value at this point in the road-map. Improving security will be a high priority task in later versions of the bot.