holochain example for "trustable random initiation"n This application demonstrates an algorithmic pattern for "trustable random initiation" in a distributed environment, i.e. how pick white/black for chess, or how we do rock/paper/scissors.
Code Status: This is a demonstration application only.
In a distributed system, we want to be able to begin an interaction in a random fashion, i.e. have a coin toss as to who gets white for a chess game. In a distributed system, we must come up with a solution whereby the randomness available to the two parties is combined in a way that both parties can trust that the other party can't control or predict the outcome ahead of time and thus win the coin toss.
The cointoss app achieves this in the following way:
- Alice requests of Bob to toss a coin by committing a
seedwith the following data:
- salt: a random salt string
- seedValue: a randomly chosen number between 0 and 9 to her private chain, and then sending to Bob a hash of that seed via node-to-node communication.
- When Bob receives the request, Bob similarly commits his own
seedwith the same structure as above, and then commits atosswith the following data:
- initiator: in this case Alice
- initiatorSeedHash: the hash of the seed that Alice sent Bob
- responder: in this case Bob
- responderSeedHash: the hash of Bob's seed
- call: a random 1, or 0 equivalent to choosing heads or tails
after making those two commits Bob responds to Alice's request with the a triple: (responderSeed,tossHash,call)
-
When Alice receives the response from Bob, she now commits a
tosson her chain because she now has all the same information necessary to commit that value. -
At this point the actual coin toss has been completed because both parties have an entry that hashes to the same value on their chains. The winner of the is defined as follows: the responder wins if (initiator.seedValue+responder.seedValue) % 2 == call). This is meant to mimic the way the "initiator" flips a coin, but the responder makes the call.
The trick behind this process is that before step 3 is completed, both parties keep their seed information secret, after the two parties both have received confirmation that the other party has committed the toss to their own chain in the form of the signed toss, then they can make their seeds content public to anybody who asks. This is because after the toss has been independently committed to both chains, the two parties can't go back on their own contribution to the randomness that makes up the toss, nor can they predict the whether the other party choose an odd or even value for their random seed by examining the hash of the seed because that seed contains a long random salt, making it impractical to search the seed space to try and brute force the generation of a seed to match its hash.
GPL 3.0 License.
Prerequiste: Install holochain on your machine. You can install cointoss very simply with this:
hcdev init -cloneExample=cointoss
To do a test run of cointoss simply type
cd cointoss
hcdev webyou should see something like:
Copying chain to: /home/bootstrap/.holochaindev
...
Serving holochain with DNA hash:QmZYxoxcqgCp6Xf6xVe8ptzPkmH8QMzxqp4r49QYpS2fEF on port:4141Then simply point your browser to http://localhost:4141 access the cointoss UI.
To run all the stand alone tests:
hcdev testhcdev scenario playThis test spins up two nodes jane and joe and tests that they can do a cointoss together. To watch the network traffic and details try:
hcdev -debug scenario playThis test is designed to be run a test which spins up a bunch clone nodes that all do a cointoss with jane.
TODO
We welcome pull requests and issue tickets. Find us on gitter to chat.
Contributors to this project are expected to follow our development protocols & practices.
Copyright (C) 2017, The MetaCurrency Project (Eric Harris-Braun, Arthur Brock, et. al.)
This program is free software: you can redistribute it and/or modify it under the terms of the license provided in the LICENSE file (GPLv3). This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Note: We are considering other 'looser' licensing options (like MIT license) but at this stage are using GPL while we're getting the matter sorted out.