RE: 70 $HIVE give-away Hive Archaeology failed; What features would a personal HIVE bot need to have?

[pibara]

Feature 4: CroupierBot features

In the distance past, the author of Hive Archaeology ran the Croupierbot on HIVE as a public service for verifiable random draws.
The idea was that anyone can invoke the bot to ask for a random draw that is based on the blockchain.

This proposed feature aims to ressurect the Croupierbot functionality in a distributed way. It is proposed that every Hive Archaeology bot is always a CroupierBot validator, and running the public service is optional using the following flag:

• --enable-croupierbot

When the croupierbot is running enabled, everyone can ask it one of a number of commands by starting a comment with a mention of the account running the croupierbot followed by a command with command specific arguments. The initial verstion will only support the following command:

• @owner LOTTERY [account]<:[tickets]> [account]<:[tickets]> [account]<:[tickets]>

The first response to this will be the bot creating a custom JSON post meant for itself and peer validators. This custom JSON contains a structured version of the command and a near future block number and a link to the comment for responses.

When the block is published, the all the bots determine the winner of the lottery and post a response with the winner according to the custom JSON and the block used for entropy.