Hash commits to a blockchain for trustless server redundancy and syncronization.

collinalexbell commented 7 years ago

Right now, one of the long term problems I see with the project if it is going to go in a direction like #398 is trust of the server running the bot.

Imagine Chaos is running on several servers and is democratically controlling several resources. These resources could be a github repo (current direction), a few web servers, an army of food producing robots, the lawbooks, etc. These resources should only respond to new code, new commands, new commits if and only if the commands are sent from an authority.

Currently, that authority is GitHub, which is fine, because the only resources it controls is a single server out in the cloud somewhere.

...but what if Chaos is controlling something more significant like money, or a food distribution supply? The Democratic control of anything always has the problem of "who watches the watchers".

A proof of work system fixes this.

Each commit could require n proof of works all strung together on a blockchain, ensuring that the network as a whole is the authority and has made a consensus that a commit had been properly voted on.

Resources could be programmed to only respond when the commit has been verified by the block-chain.