The Blast Game that was launched last December 2019,
I believe it to have technical errors because supposedly there was 1000000 gameHashes that was generated and the final hash was staked publicly:
A chain of 1 million SHA512 hashes was generated (starting with a server secret.)
The final hash is:
Bitsler will go through the hashes (in reverse order) and use each hash to determine the crash result. So the hash of our first game's hash is the same as our published final hash.
To ensure we didn't pick a hash chain that has some advantage for us, we will use a future bitcoin block hash as "client seed" to generate the final crash results. We will use the block hash of bitcoin block 608891 (around 4:30 AM GMT on Fri 20 Dec 2019.)
The code to generate each crash result is:
This blog post will be shared on our social media channels and archived by several archive websites. Therefor we cannot edit the final hash (and therefor hash chain) nor the future bitcoin block number anymore. This makes our new game Blast completely provably fair.
Link list:
- Bitsler blog - here
- archive.org - here
- archive.is - here
- archive.vn - here
- reddit.com - here
So I noticed the 1,000,000th round showed a different result on, https://www.bitsler.com/blast/1000000 and if you try to verify it using their built-in verifier.
1.32x and 1.35x , error was that the verifier is using a newer client seed since the game has been relaunched now its v4.
sooo....
I paired the finalHash given on the preseeding event post, with the right bitcoin block hash, 608891;
000000000000000000040a829189c5732460c94bc58926ea49d0e6918e396e31
and I am still not getting 1.32x;
I did it with the url
https://www.bitsler.com/en/provably-fair/verifier?type=blast&serverseed=6792dbfbe918c3533c87ae70d63c03dc287e8ad201733768dacada095d52eb09539cde581c1016e83b1385c675dd7f17e5a9de0a3ba2af8329a0cf39e89c25ba&client=000000000000000000040a829189c5732460c94bc58926ea49d0e6918e396e31
So I asked again, and again. . , no clear explanation I was just told I did it wrong etc., (which I prolly did) but after reading other preseeding events like this (https://bitcointalk.org/index.php?topic=2807542.0) bustabit v2 ,
Also asked somebody which I know to be knowledgeable with this topic in telegram,
I became more certain the finalgame result was not FAIR,
I believe it to have technical errors because supposedly there was 1000000 gameHashes that was generated and the final hash was staked publicly:
We will soon release our new game called Blast!
.....snip...image...snip
To make this game provably fair, we announce our methods here.
.....snip...image...snip
To make this game provably fair, we announce our methods here.
A chain of 1 million SHA512 hashes was generated (starting with a server secret.)
The final hash is:
Code:
d3fc772bf79bf90f74c4cfe63b3534cd007f5956ec5d65a189475a3e5e3d7b635b4f0c86d2d69b67f46292f156bbef6f552c62c0e50710860b51854655235cb6
Bitsler will go through the hashes (in reverse order) and use each hash to determine the crash result. So the hash of our first game's hash is the same as our published final hash.
To ensure we didn't pick a hash chain that has some advantage for us, we will use a future bitcoin block hash as "client seed" to generate the final crash results. We will use the block hash of bitcoin block 608891 (around 4:30 AM GMT on Fri 20 Dec 2019.)
The code to generate each crash result is:
Code:
$hash = hash_hmac('sha512', $gameHash, $blockHash);
$number = hexdec(substr($hash, 0, 13));
$multiplier = 98 / (1 - ($number / (pow(2,52))));
echo max(100, floor($multiplier)) / 100;
$number = hexdec(substr($hash, 0, 13));
$multiplier = 98 / (1 - ($number / (pow(2,52))));
echo max(100, floor($multiplier)) / 100;
This blog post will be shared on our social media channels and archived by several archive websites. Therefor we cannot edit the final hash (and therefor hash chain) nor the future bitcoin block number anymore. This makes our new game Blast completely provably fair.
Link list:
- Bitsler blog - here
- archive.org - here
- archive.is - here
- archive.vn - here
- reddit.com - here
So I noticed the 1,000,000th round showed a different result on, https://www.bitsler.com/blast/1000000 and if you try to verify it using their built-in verifier.
1.32x and 1.35x , error was that the verifier is using a newer client seed since the game has been relaunched now its v4.
sooo....
I paired the finalHash given on the preseeding event post, with the right bitcoin block hash, 608891;
000000000000000000040a829189c5732460c94bc58926ea49d0e6918e396e31
and I am still not getting 1.32x;
I did it with the url
https://www.bitsler.com/en/provably-fair/verifier?type=blast&serverseed=6792dbfbe918c3533c87ae70d63c03dc287e8ad201733768dacada095d52eb09539cde581c1016e83b1385c675dd7f17e5a9de0a3ba2af8329a0cf39e89c25ba&client=000000000000000000040a829189c5732460c94bc58926ea49d0e6918e396e31
So I asked again, and again. . , no clear explanation I was just told I did it wrong etc., (which I prolly did) but after reading other preseeding events like this (https://bitcointalk.org/index.php?topic=2807542.0) bustabit v2 ,
Also asked somebody which I know to be knowledgeable with this topic in telegram,
I became more certain the finalgame result was not FAIR,
Quote
Bitsler will go through the hashes (in reverse order) and use each hash to determine the crash result. So the hash of our first game's hash is the same as our published final hash.