Pasino.com Provably Fair Seeding Event for Crash!

[MrBit112]

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: 96bd217bd55f07aba2980b59210eaa27a9b302e17617092be7fea3e232132f41, 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 678978

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 96bd217bd55f07aba2980b59210eaa27a9b302e17617092be7fea3e232132f41. That is to say, the first game's hash played under the new provably fair scheme, when hashed will be 96bd217bd55f07aba2980b59210eaa27a9b302e17617092be7fea3e232132f41.

[1714555637]

1714555637

[1714555637]

1714555637

[TimeTeller]

Once your site is live, you can make a clickable link of your site in your ANN.
And also, you already have copper membership, why not put some snapshots of your site once it is ready?
So at a glance, we already know what to expect on your site.

[Saint-loup]

Once your site is live, you can make a clickable link of your site in your ANN.
And also, you already have copper membership, why not put some snapshots of your site once it is ready?
So at a glance, we already know what to expect on your site.

I agree with you, there are still too few casinos posting snapshots of their site and the games they are offering. I don't know why but it's a big mistake in my opinion. People are usually reluctant to register on casinos just to be able to watch how the casinos are, since gambling is a risky activity they generally prefer to stick to platforms they already know.

[LoyceV]

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: 96bd217bd55f07aba2980b59210eaa27a9b302e17617092be7fea3e232132f41, 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 678978

Quoting for eternity
I confirm block 678978 wasn't mined yet (and OP's post wasn't edited) when this was posted. The block hash: 0000000000000000000aa2dfb666783e6f5e100eefab4cd8756a359e7c247d1e.

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 96bd217bd55f07aba2980b59210eaa27a9b302e17617092be7fea3e232132f41. That is to say, the first game's hash played under the new provably fair scheme, when hashed will be 96bd217bd55f07aba2980b59210eaa27a9b302e17617092be7fea3e232132f41.

why not put some snapshots of your site once it is ready?

OP shouldn't edit his post.

Additional archives:
https://loyce.club/archive/details/topic_5330085.html
https://ninjastic.space/post/56765148
https://archive.is/wip/cwImK

[MrBit112]

Thank you very much for archive and quote the thread! 
I confirm Block 678978 is mined and our client seed will be: 0000000000000000000aa2dfb666783e6f5e100eefab4cd8756a359e7c247d1e

We have also updated the our verifier page: https://pasinocom.github.io/pasino-verify/crash.html

Pasino.com will be available to play in less than 24H.

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: 96bd217bd55f07aba2980b59210eaa27a9b302e17617092be7fea3e232132f41, 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 678978

Quoting for eternity
I confirm block 678978 wasn't mined yet (and OP's post wasn't edited) when this was posted. The block hash: 0000000000000000000aa2dfb666783e6f5e100eefab4cd8756a359e7c247d1e.

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 96bd217bd55f07aba2980b59210eaa27a9b302e17617092be7fea3e232132f41. That is to say, the first game's hash played under the new provably fair scheme, when hashed will be 96bd217bd55f07aba2980b59210eaa27a9b302e17617092be7fea3e232132f41.

why not put some snapshots of your site once it is ready?

OP shouldn't edit his post.

Additional archives:
https://loyce.club/archive/details/topic_5330085.html
https://ninjastic.space/post/56765148
https://archive.is/wip/cwImK