Meckabit Provably Fair Seeding Event
Welcome to the second provably fair seeding event for rounds 1,000,000 to 2,000,000.
We have hashed (sha256) a secret 100,000 times. We will use these hashes in reverse order to play the rounds. In each round we will combine this hash with a block hash that as of the moment of this publishing is not yet known and will be determined by our chosen block.
In layman's terms the process will be as follows.
- Server secret (private key) is fed into sha256 (open source algorithm to create random seeds) 100,000 times
- Game will play through these in reverse order
- The 100,000 randomly generated hashes will be mixed with the client seed which is the hash from block number 504213
- Thus giving users confidence in the crash point generation through the use of random data from both the sha256 and the client seed from the block which has not yet been mined.
JSFiddle Link which can also be found on our site - https://jsfiddle.net/1L1uqcgv/641/
- The next client seed will be taken from block 532600 (Which has not yet been mined) for round 1m-1.1m
- For round 1.1m - 1.2m the client seed will be taken from block 532601
- For round 1.2m - 1.3m the client seed will be taken from block 532602
- For round 1.3m - 1.4m the client seed will be taken from block 532603
- For round 1.4m - 1.5m the client seed will be taken from block 532604
- For round 1.5m - 1.6m the client seed will be taken from block 532605
- For round 1.6m - 1.7m the client seed will be taken from block 532606
- For round 1.7m - 1.8m the client seed will be taken from block 532607
- For round 1.8m - 1.9m the client seed will be taken from block 532608
- For round 1.9m - 2.0m the client seed will be taken from block 532609
We have hashed (sha256) a secret 100,000 times. We will use these hashes in reverse order to play the rounds. In each round we will combine this hash with a block hash that as of the moment of this publishing is not yet known and will be determined by our chosen block.
In layman's terms the process will be as follows.
- Server secret (private key) is fed into sha256 (open source algorithm to create random seeds) 100,000 times
- Game will play through these in reverse order
- The 100,000 randomly generated hashes will be mixed with the client seed which is the hash from block number 504213
- Thus giving users confidence in the crash point generation through the use of random data from both the sha256 and the client seed from the block which has not yet been mined.
JSFiddle Link which can also be found on our site - https://jsfiddle.net/1L1uqcgv/641/
- The next client seed will be taken from block 532600 (Which has not yet been mined) for round 1m-1.1m
- For round 1.1m - 1.2m the client seed will be taken from block 532601
- For round 1.2m - 1.3m the client seed will be taken from block 532602
- For round 1.3m - 1.4m the client seed will be taken from block 532603
- For round 1.4m - 1.5m the client seed will be taken from block 532604
- For round 1.5m - 1.6m the client seed will be taken from block 532605
- For round 1.6m - 1.7m the client seed will be taken from block 532606
- For round 1.7m - 1.8m the client seed will be taken from block 532607
- For round 1.8m - 1.9m the client seed will be taken from block 532608
- For round 1.9m - 2.0m the client seed will be taken from block 532609