 Show Posts
|
|
Pages: [1]
|
Welcome to our seeding event for Strongman launching next week. We have generated a chain of 10 million SHA256 hashes, starting with a server secret that has been repeatedly fed the output of SHA256 back into itself 10 million times. The SHA256 of the final hash in the chain is: d0d99b3450ab0631ac2ef485f694829182bf410bf59377262db496fbcdb4da81, by publicising it here we are preventing any ability to pick an alternate SHA256 chain. Strongman game will play through that chain of hashes, in reverse order, and use the hashes to determine the game outcome in a probably fair manner. const nBits = 52; // number of most significant bits to use
// 1. HMAC_SHA256(key=salt, message=seed)
const hmac = crypto.createHmac("sha256", salt);
hmac.update(seed);
seed = hmac.digest("hex");
// 2. r = 52 most significant bits
seed = seed.slice(0, nBits/4);
const r = parseInt(seed, 16);
// 3. X = r / 2^52
let X = r / Math.pow(2, nBits); // uniformly distributed in [0; 1)
// 4. X = 99 / (1-X)
X = X*100 + 1;
// 5. return max(trunc(X), 100)
const result = Math.floor(X);
return Math.max(1, Math.min(100, result)); Before being used to calculate the corresponding result, each game hash is salted with the lowercase, hexadecimal string representation of the hash of bitcoin block 667000. This block has not been mined yet, proving that we have not deliberately picked a chain that is unfavourable for players. Excited to show you the Strongman game very soon! The hash of block 667000 is 0000000000000000000bfc4add1faa645bed3add5486882966c13b29b0e82cdd |
|
|
|
Quoting. And saved to archive.is: https://archive.is/gTffQAlso confirming that the current best bitcoin block is: 666592 and thus 667000 has not yet been mined. What is the guarantee of quoted the OP using the same newbie account here from bitcointalk? I'm also quoting below. But in any case, the topic can also be verified by ninjastic.space here. The current block of the Bitcoin blockchain is 666623 Welcome to our seeding event for Strongman launching next week. We have generated a chain of 10 million SHA256 hashes, starting with a server secret that has been repeatedly fed the output of SHA256 back into itself 10 million times. The SHA256 of the final hash in the chain is: d0d99b3450ab0631ac2ef485f694829182bf410bf59377262db496fbcdb4da81, by publicising it here we are preventing any ability to pick an alternate SHA256 chain. Strongman game will play through that chain of hashes, in reverse order, and use the hashes to determine the game outcome in a probably fair manner. const nBits = 52; // number of most significant bits to use
// 1. HMAC_SHA256(key=salt, message=seed)
const hmac = crypto.createHmac("sha256", salt);
hmac.update(seed);
seed = hmac.digest("hex");
// 2. r = 52 most significant bits
seed = seed.slice(0, nBits/4);
const r = parseInt(seed, 16);
// 3. X = r / 2^52
let X = r / Math.pow(2, nBits); // uniformly distributed in [0; 1)
// 4. X = 99 / (1-X)
X = X*100 + 1;
// 5. return max(trunc(X), 100)
const result = Math.floor(X);
return Math.max(1, Math.min(100, result)); Before being used to calculate the corresponding result, each game hash is salted with the lowercase, hexadecimal string representation of the hash of bitcoin block 667000. This block has not been mined yet, proving that we have not deliberately picked a chain that is unfavourable for players. Excited to show you the Strongman game very soon! Thank you for confirming the current block. |
|
|
|
Welcome to our seeding event for Strongman launching next week. We have generated a chain of 10 million SHA256 hashes, starting with a server secret that has been repeatedly fed the output of SHA256 back into itself 10 million times. The SHA256 of the final hash in the chain is: d0d99b3450ab0631ac2ef485f694829182bf410bf59377262db496fbcdb4da81, by publicising it here we are preventing any ability to pick an alternate SHA256 chain. Strongman game will play through that chain of hashes, in reverse order, and use the hashes to determine the game outcome in a probably fair manner. const nBits = 52; // number of most significant bits to use
// 1. HMAC_SHA256(key=salt, message=seed)
const hmac = crypto.createHmac("sha256", salt);
hmac.update(seed);
seed = hmac.digest("hex");
// 2. r = 52 most significant bits
seed = seed.slice(0, nBits/4);
const r = parseInt(seed, 16);
// 3. X = r / 2^52
let X = r / Math.pow(2, nBits); // uniformly distributed in [0; 1)
// 4. X = 99 / (1-X)
X = X*100 + 1;
// 5. return max(trunc(X), 100)
const result = Math.floor(X);
return Math.max(1, Math.min(100, result)); Before being used to calculate the corresponding result, each game hash is salted with the lowercase, hexadecimal string representation of the hash of bitcoin block 667000. This block has not been mined yet, proving that we have not deliberately picked a chain that is unfavourable for players. Excited to show you the Strongman game very soon! Quoting. And saved to archive.is: https://archive.is/gTffQAlso confirming that the current best bitcoin block is: 666592 and thus 667000 has not yet been mined. |
|
|
|
Welcome to our seeding event for Strongman launching next week. We have generated a chain of 10 million SHA256 hashes, starting with a server secret that has been repeatedly fed the output of SHA256 back into itself 10 million times. The SHA256 of the final hash in the chain is: d0d99b3450ab0631ac2ef485f694829182bf410bf59377262db496fbcdb4da81, by publicising it here we are preventing any ability to pick an alternate SHA256 chain. Strongman game will play through that chain of hashes, in reverse order, and use the hashes to determine the game outcome in a probably fair manner. const nBits = 52; // number of most significant bits to use
// 1. HMAC_SHA256(key=salt, message=seed)
const hmac = crypto.createHmac("sha256", salt);
hmac.update(seed);
seed = hmac.digest("hex");
// 2. r = 52 most significant bits
seed = seed.slice(0, nBits/4);
const r = parseInt(seed, 16);
// 3. X = r / 2^52
let X = r / Math.pow(2, nBits); // uniformly distributed in [0; 1)
// 4. X = 99 / (1-X)
X = X*100 + 1;
// 5. return max(trunc(X), 100)
const result = Math.floor(X);
return Math.max(1, Math.min(100, result)); Before being used to calculate the corresponding result, each game hash is salted with the lowercase, hexadecimal string representation of the hash of bitcoin block 667000. This block has not been mined yet, proving that we have not deliberately picked a chain that is unfavourable for players. Excited to show you the Strongman game very soon! |
|
|
|
We have generated a chain of 10 million SHA256 hashes, starting with a server secret that has been repeatedly fed the output of SHA256 back into itself 10 million times. The SHA256 of the final hash in the chain is: 44ec050ec43cc6e7f579f66d8d9750f083243d307bf859e61c1a5e41d91387ed, by publicising it here we are preventing any ability to pick an alternate SHA256 chain.
I have not seen any houses showing up such information well in advance to the launch of their operation; seeming like too good for the gamblers who value and prioritize fairness at first hand. I understand that you are trying to be complete fair to your gamblers on top of provably fair mechanism, right? Usually, rocket crash games uses same server seed for all participating gamblers and no need of client seed, right? And also, there cannot be any option to change the upcoming seed as that will not be an individual based but common for all gamblers. So, pre-generating server seeds for up to 10 million games is an usual practice for all rocket crash game providers? Also confirming that the current best bitcoin block is: 632783 and thus 632900 has not yet been mined.
You mean the most recent block? I also confirm the current block around the time of this post is: 632866 Also, you may ask any reputed forum members to quote your open-post for future references. Thank you for confirming the current block the time of your post. We are not the first house, I believe bustabit.com was the first one. In this type of game for each round there is only one RNG which broadcast to the players. So using the client seed here is not relevant because you cannot use client seed of all players in a same time. Yes this is a very normal practice to have a seeding event for this kind of games before launching the game. |
|
|
|
Welcome to our seeding event for Rocket Crash launching this week. We have generated a chain of 10 million SHA256 hashes, starting with a server secret that has been repeatedly fed the output of SHA256 back into itself 10 million times. The SHA256 of the final hash in the chain is: 44ec050ec43cc6e7f579f66d8d9750f083243d307bf859e61c1a5e41d91387ed, by publicising it here we are preventing any ability to pick an alternate SHA256 chain. Rocket Crash will play through that chain of hashes, in reverse order, and use the hashes to determine the crash point in a probably fair manner. const crypto = require("crypto")
function gameResult(seed, salt) {
const nBits = 52 // number of most significant bits to use
// 1. HMAC_SHA256(key=salt, message=seed)
const hmac = crypto.createHmac("sha256", salt)
hmac.update(seed)
seed = hmac.digest("hex")
// 2. r = 52 most significant bits
seed = seed.slice(0, nBits/4)
const r = parseInt(seed, 16)
// 3. X = r / 2^52
let X = r / Math.pow(2, nBits) // uniformly distributed in [0; 1)
// 4. X = 99 / (1-X)
X = 99 / (1 - X)
// 5. return max(trunc(X), 100)
const result = Math.floor(X)
return Math.max(1, result / 100)
}
Before being used to calculate the corresponding result, each game hash is salted with the lowercase, hexadecimal string representation of the hash of bitcoin block 632900. This block has not been mined yet, proving that we have not deliberately picked a chain that is unfavourable for players. Excited to show you the Rocket Crash game very soon! Quoting. And saved to archive.is: http://archive.is/ljKcoAlso confirming that the current best bitcoin block is: 632783 and thus 632900 has not yet been mined. |
|
|
|
Welcome to our seeding event for Rocket Crash launching this week. We have generated a chain of 10 million SHA256 hashes, starting with a server secret that has been repeatedly fed the output of SHA256 back into itself 10 million times. The SHA256 of the final hash in the chain is: 44ec050ec43cc6e7f579f66d8d9750f083243d307bf859e61c1a5e41d91387ed, by publicising it here we are preventing any ability to pick an alternate SHA256 chain. Rocket Crash will play through that chain of hashes, in reverse order, and use the hashes to determine the crash point in a probably fair manner. const crypto = require("crypto")
function gameResult(seed, salt) {
const nBits = 52 // number of most significant bits to use
// 1. HMAC_SHA256(key=salt, message=seed)
const hmac = crypto.createHmac("sha256", salt)
hmac.update(seed)
seed = hmac.digest("hex")
// 2. r = 52 most significant bits
seed = seed.slice(0, nBits/4)
const r = parseInt(seed, 16)
// 3. X = r / 2^52
let X = r / Math.pow(2, nBits) // uniformly distributed in [0; 1)
// 4. X = 99 / (1-X)
X = 99 / (1 - X)
// 5. return max(trunc(X), 100)
const result = Math.floor(X)
return Math.max(1, result / 100)
}
Before being used to calculate the corresponding result, each game hash is salted with the lowercase, hexadecimal string representation of the hash of bitcoin block 632900. This block has not been mined yet, proving that we have not deliberately picked a chain that is unfavourable for players. Excited to show you the Rocket Crash game very soon! |
|
|
|
|
