hello, I want to know if there is any program to calculate the game crash on pasino.com.
Thank you for your attention and I look forward to your return.
Topic: New Pasino.com Provably Fair Seeding Event for Crash! (Read 186 times)
MrBit112
Are you official representation from Pasino and why are you always creating new topics with same content?
Better use one main topic for your casino and post any updates you have there.
Are you official representation from Pasino and why are you always creating new topics with same content?
Better use one main topic for your casino and post any updates you have there.
I guess he is just like a paid user to create a thread for a casino.
I say it because he created several Seeding Event thread for 3 different casinos.
The casinos are: Nanogames.io (inaccessible), Faucetpay.io (active) and Pasino.com (he created 2 seeding event thread for this one).
It is said that game crashes claiming to be fair are normal and we have experienced crashes in various casino games. Indeed, at first glance it would be very fair, it's just that we need to cash out faster and take profits around 3x.
What @notblox1 said is true you are hoarding too many of the same threads but you yourself are not giving a serious response to the details you are promoting.
What @notblox1 said is true you are hoarding too many of the same threads but you yourself are not giving a serious response to the details you are promoting.
Bitcoin Block 711779 has been mined! Our The hash of the block and our client seed is: 0000000000000000000273575fdac897ff389aac3e35745220cdae16f7506470
MrBit112Are you official representation from Pasino and why are you always creating new topics with same content?
Better use one main topic for your casino and post any updates you have there.
Bitcoin Block 711779 has been mined! Our The hash of the block and our client seed is: 0000000000000000000273575fdac897ff389aac3e35745220cdae16f7506470
Welcome to the Pasino.com Provably Fair Seeding Event for Crash!
This will reuse the idea posted by Ryan and used for Bustabit v1.
A chain of 10 million (1e7) sha256 hashes was generated, starting with a Server Secret that has been repeatedly fed the output of sha256 hash back into itself 10 million times.
The final hash in the chain is: b066c23ef601659038ad46860677642de5f8541418002b43ef56c406270e78e9, by publicizing it here we are preventing any ability to pick an alternate sha256 chain.
Pasino.com will play through that chain of hashes, in reverse order, and use the hashes to determine the crash point.
To avoid criticism that the Server Secret used in step 1 was carefully chosen to generate lots of "bad" crash points, each hash in the chain will be salted with a client seed, which we have no control of.
The client seed will be the block hash of a Bitcoin block that hasn't yet been mined: block 711779
The reference code (javascript) is as follows:
The method to convert a game hash, mix it with the picked client seed to a money pot multiplier:
The chain could be generated with code such as:
Using our chosen starting serverSeed, the hash terminating the chain is b066c23ef601659038ad46860677642de5f8541418002b43ef56c406270e78e9. That is to say, the first game's hash played under the new provably fair scheme, when hashed will be b066c23ef601659038ad46860677642de5f8541418002b43ef56c406270e78e9.
This will reuse the idea posted by Ryan and used for Bustabit v1.
A chain of 10 million (1e7) sha256 hashes was generated, starting with a Server Secret that has been repeatedly fed the output of sha256 hash back into itself 10 million times.
The final hash in the chain is: b066c23ef601659038ad46860677642de5f8541418002b43ef56c406270e78e9, by publicizing it here we are preventing any ability to pick an alternate sha256 chain.
Pasino.com will play through that chain of hashes, in reverse order, and use the hashes to determine the crash point.
To avoid criticism that the Server Secret used in step 1 was carefully chosen to generate lots of "bad" crash points, each hash in the chain will be salted with a client seed, which we have no control of.
The client seed will be the block hash of a Bitcoin block that hasn't yet been mined: block 711779
The reference code (javascript) is as follows:
Code:
function genGameHash(serverSeed) {
return crypto.createHash('sha256').update(serverSeed).digest('hex');
}The method to convert a game hash, mix it with the picked client seed to a money pot multiplier:
Code:
function toFixed(num, fixed) {
var re = new RegExp('^-?\\d+(?:\.\\d{0,' + (fixed || -1) + '})?');
return num.toString().match(re)[0];
}
function crashPointFromHash(serverSeed, clientSeed) {
var actual_hash = CryptoJS.SHA512(clientSeed + "-" + serverSeed).toString();
var p1 = parseInt((actual_hash.substr(0, 2) + '').replace(/[^a-f0-9]/gi, ''), 16);
var p2 = parseInt((actual_hash.substr(2, 2) + '').replace(/[^a-f0-9]/gi, ''), 16);
var p3 = parseInt((actual_hash.substr(4, 2) + '').replace(/[^a-f0-9]/gi, ''), 16);
var p4 = parseInt((actual_hash.substr(6, 2) + '').replace(/[^a-f0-9]/gi, ''), 16);
var roll = Math.floor(((p1 / Math.pow(256, 1)) + (p2 / Math.pow(256, 2)) + (p3 / Math.pow(256, 3)) + (p4 / Math.pow(256, 4))) * 1000000);
var crash_point = toFixed(parseFloat(1000000 / (roll + 1) * 0.96), 2);
return crash_point;
}
The chain could be generated with code such as:
Code:
var serverSecret = 'If you knew this, you could steal all my money';
var clientSeed = '0000examplehash';
var gamesToGenerate = 1e7;
var serverSeed = serverSecret;
for (var game = gamesToGenerate; game > 0; --game) {
serverSeed = genGameHash(serverSeed);
console.log('Game ' + game + ' has a crash point of ' + (crashPointFromHash(serverSeed, clientSeed) / 100).toFixed(2) +'x', '\t\tHash: ' + serverSeed);
}
var terminatingHash = genGameHash(serverSeed);
console.log('The terminating hash is: ', terminatingHash);
Using our chosen starting serverSeed, the hash terminating the chain is b066c23ef601659038ad46860677642de5f8541418002b43ef56c406270e78e9. That is to say, the first game's hash played under the new provably fair scheme, when hashed will be b066c23ef601659038ad46860677642de5f8541418002b43ef56c406270e78e9.
Jump to: