Hi,
I wish you good luck with the project.
But until you don't have a clean post (unedited) about this seed event, I will count it as corrupted. Try with other block numbers/height without editing the post where you announce it.
D.
Topic: Meckabit.com║█║Provably Fair║█║Seeding Event (Read 164 times)
Welcome to the provably fair seeding event for Meckabit.com, upon our first beta launch we were provided with excellent feedback from the community, along with comments on how to better optimise the site both from a physical performance perspective along with aesthetic amendments that would better cater to the community, we have taken this feedback on board and will continue to develop and enhance the site through the use of your comments and insight.
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.
The source code used for hash chain creation and random multiplier generation can be found here (will be inserted soon)
JSFiddle Link (This tool will be implemented into our site for convenience) - https://jsfiddle.net/1L1uqcgv/641/
The client seed will be the hash taken from block 504213 which has not yet been mined.
Future Seeding Rounds Listed Below
- The next client seed will be taken from block 507630 (Which has not yet been mined) for round 200-300k
- For round 300k - 400k the client seed will be taken from block 510000
- For round 400k - 500k the client seed will be taken from block 510001
- For round 500k - 600k the client seed will be taken from block 510002
- For round 600k - 700k the client seed will be taken from block 510003
- For round 700k - 800k the client seed will be taken from block 510004
- For round 800k - 900k the client seed will be taken from block 510005
- For round 900k - 1000k the client seed will be taken from block 510006
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.
The source code used for hash chain creation and random multiplier generation can be found here (will be inserted soon)
JSFiddle Link (This tool will be implemented into our site for convenience) - https://jsfiddle.net/1L1uqcgv/641/
The client seed will be the hash taken from block 504213 which has not yet been mined.
Future Seeding Rounds Listed Below
- The next client seed will be taken from block 507630 (Which has not yet been mined) for round 200-300k
- For round 300k - 400k the client seed will be taken from block 510000
- For round 400k - 500k the client seed will be taken from block 510001
- For round 500k - 600k the client seed will be taken from block 510002
- For round 600k - 700k the client seed will be taken from block 510003
- For round 700k - 800k the client seed will be taken from block 510004
- For round 800k - 900k the client seed will be taken from block 510005
- For round 900k - 1000k the client seed will be taken from block 510006
Welcome to the provably fair seeding event for Meckabit.com, upon our first beta launch we were provided with excellent feedback from the community, along with comments on how to better optimise the site both from a physical performance perspective along with aesthetic amendments that would better cater to the community, we have taken this feedback on board and will continue to develop and enhance the site through the use of your comments and insight.
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.
The source code used for hash chain creation and random multiplier generation can be found here (will be inserted soon)
JSFiddle Link (This tool will be implemented into our site for convenience) - https://jsfiddle.net/1L1uqcgv/641/
The client seed will be the hash taken from block 504213 which has not yet been mined.
Termination hash will be (inserted here once the game begins)
Future Seeding Rounds Listed Below
- The next client seed will be taken from block 507630 (Which has not yet been mined) for round 200-300k
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.
The source code used for hash chain creation and random multiplier generation can be found here (will be inserted soon)
JSFiddle Link (This tool will be implemented into our site for convenience) - https://jsfiddle.net/1L1uqcgv/641/
The client seed will be the hash taken from block 504213 which has not yet been mined.
Termination hash will be (inserted here once the game begins)
Future Seeding Rounds Listed Below
- The next client seed will be taken from block 507630 (Which has not yet been mined) for round 200-300k
Welcome to the provably fair seeding event for Meckabit.com, upon our first beta launch we were provided with excellent feedback from the community, along with comments on how to better optimise the site both from a physical performance perspective along with aesthetic amendments that would better cater to the community, we have taken this feedback on board and will continue to develop and enhance the site through the use of your comments and insight.
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.
The source code used for hash chain creation and random multiplier generation can be found here (will be inserted soon)
JSFiddle Link (This tool will be implemented into our site for convenience) - https://jsfiddle.net/1L1uqcgv/641/
The client seed will be the hash taken from block 504213 which has not yet been mined.
Termination hash will be (inserted here once the game begins)
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.
The source code used for hash chain creation and random multiplier generation can be found here (will be inserted soon)
JSFiddle Link (This tool will be implemented into our site for convenience) - https://jsfiddle.net/1L1uqcgv/641/
The client seed will be the hash taken from block 504213 which has not yet been mined.
Termination hash will be (inserted here once the game begins)
Welcome to the provably fair seeding event for Meckabit.com, upon our first beta launch we were provided with excellent feedback from the community, along with comments on how to better optimise the site both from a physical performance perspective along with aesthetic amendments that would better cater to the community, we have taken this feedback on board and will continue to develop and enhance the site through the use of your comments and insight.
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.
The source code used for hash chain creation and random multiplier generation can be found here (will be inserted soon)
JSFiddle Link (This tool will be implemented into our site for convenience) - https://jsfiddle.net/1L1uqcgv/641/
The client seed will be the hash taken from block 504213 which has not yet been mined.
Termination hash will be (inserted here once the game begins)
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.
The source code used for hash chain creation and random multiplier generation can be found here (will be inserted soon)
JSFiddle Link (This tool will be implemented into our site for convenience) - https://jsfiddle.net/1L1uqcgv/641/
The client seed will be the hash taken from block 504213 which has not yet been mined.
Termination hash will be (inserted here once the game begins)
Welcome to the provably fair seeding event for Meckabit.com, upon our first beta launch we were provided with excellent feedback from the community, along with comments on how to better optimise the site both from a physical performance perspective along with aesthetic amendments that would better cater to the community, we have taken this feedback on board and will continue to develop and enhance the site through the use of your comments and insight.
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.
The source code used for hash chain creation and random multiplier generation can be found here (will be inserted soon)
JSFiddle Link (This tool will be implemented into our site for convenience) - https://jsfiddle.net/1L1uqcgv/641/
The client seed will be the hash taken from block 504213 which has not yet been mined.
Future Seeding Rounds Listed Below
- The next client seed will be taken from block 507630 (Which has not yet been mined) for round 200-300k
- For round 300k - 400k the client seed will be taken from block 510000
- For round 400k - 500k the client seed will be taken from block 510001
- For round 500k - 600k the client seed will be taken from block 510002
- For round 600k - 700k the client seed will be taken from block 510003
- For round 700k - 800k the client seed will be taken from block 510004
- For round 800k - 900k the client seed will be taken from block 510005
- For round 900k - 1000k the client seed will be taken from block 510006
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.
The source code used for hash chain creation and random multiplier generation can be found here (will be inserted soon)
JSFiddle Link (This tool will be implemented into our site for convenience) - https://jsfiddle.net/1L1uqcgv/641/
The client seed will be the hash taken from block 504213 which has not yet been mined.
Future Seeding Rounds Listed Below
- The next client seed will be taken from block 507630 (Which has not yet been mined) for round 200-300k
- For round 300k - 400k the client seed will be taken from block 510000
- For round 400k - 500k the client seed will be taken from block 510001
- For round 500k - 600k the client seed will be taken from block 510002
- For round 600k - 700k the client seed will be taken from block 510003
- For round 700k - 800k the client seed will be taken from block 510004
- For round 800k - 900k the client seed will be taken from block 510005
- For round 900k - 1000k the client seed will be taken from block 510006
Jump to: