 Show Posts
|
|
Pages: [1] 2 3
|
|
2
|
Economy / Gambling / Re: FaucetPay.io Provably Fair Seeding Event for Crash!
|
on: January 16, 2023, 07:15:45 AM
|
Welcome to the new FaucetPay.io V2 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: 6f2860fd02aaa414a5e9bd518801bed060fb8baa20243c0fc37b96ecde9d449c, by publicizing it here we are preventing any ability to pick an alternate sha256 chain. FaucetPay.io 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 772214The reference code (javascript) is as follows: 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: 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: 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 6f2860fd02aaa414a5e9bd518801bed060fb8baa20243c0fc37b96ecde9d449c. That is to say, the first game's hash played under the new provably fair scheme, when hashed will be 6f2860fd02aaa414a5e9bd518801bed060fb8baa20243c0fc37b96ecde9d449c. |
|
|
|
|
5
|
Economy / Scam Accusations / Re: Nanogames.io - Millions of not provably fair Roulette Multiplayer rounds
|
on: June 03, 2022, 09:38:42 AM
|
 Dear Dennis from Nanogames, If I was making false accusations before, according to you, it is safe to say you're just playing dumb now. If you're that expert at using the verifier (I've probably used it more times than you, and know better than you how it works, and you work here.), show me the proof that game #884,335, for example, had the same hash both in the verifier and on the website. Oh, let me simplify the work for you. I have fed the verifier with game #1,684,355 hash: 1b955c61cdf11f2462c6c2ed59fdb9ea3bbde2f480d7568e5f879804f07cbe8d. I've verified 800,000 rounds: according to the verifier, 800,000 rounds before the hash was 904e97bcb8586d0c4355ae9b311b54c390b762708210c070e7c71490971d5f2d. (you probably don't even know how to hash 800,000 times without making it crash your browser rotflmao.) The verifier calculated it because all it did was hash the hash I fed it 800,000 times, and that was the result. Now prove to me that was the actual hash used in the games on the website. Do you say that the website shows all bets? Wrong. All it does is show 200 pages of 20 bets each, that's the latest 4000 bets. It says it can't go beyond page 200 cause it's too high. Now, since the official hash posted by Mrbit is wrong, tell me how we are supposed to verify that the chain wasn't switched (potentially multiple times) hundreds of thousands of bets ago, and that it actually played the hash 904e97bcb8586d0c4355ae9b311b54c390b762708210c070e7c71490971d5f2d on the Nanogames website, using the VERIFIER. Since you are so expert at using it, apparently, and I'm the dumb one who doesn't know how to use it. Go ahead. The support staff told you already everything that you need to verify the bets. They told you that we have changed the salt in January 2022. So, you don't even need to verify all bets since before January it used another salt ( see my provably fair event ). If you tell me your username, I'm happy to pull out all your bets so you can verify them. We will do another PF event and my colleagues admitted already the mistakes were on our side with that, for your report we rewarded you with 250 USD. However, that doesnt mean that the game is unfair. You can still verify it with the verifier. If the developer sends you the first round hash, you can go through probably 250k games and verify each by each if that makes you happy. After that, you continue to try to extort us by claiming that we can manipulate futures rounds by changing the seed back and forth and if we don't pay you you will make it public... If you think so, please tell me us your username, ( which you have refused to ) so that we can pull up all your bets and verify them with you immediately. You are not acting in favor of the community or trying to "expose" something... As you said: All is well all that ends well, send me the money compensation and we'll forget about it. You are just someone who is trying to blackmail us for money. On top of that, you were spamming our telegram group and sending to all our staff DMs. That's the reason why you got banned on our social media. Now you are insulting our staff by telling them they are "dumb"? My colleague Dennis did everything perfectly, and you have refused to 1.) Wait for a reply from the developers about the first round hash with the new salt ( which is anyways nonsense because you don't care about it, you just look for a reason to blackmail us) 2.) Tell us your username, where we could pull out immediately all your bets and verify them. That being said. I won't continue to discuss with you because it's a waste of time to talk with a "criminal" who blackmails people. |
|
|
|
|
6
|
Economy / Gambling / Re: 🚀 NanoGames.io - Social Gambling | Play or Invest with a leverage up to 5x 🚀
|
on: June 03, 2022, 09:28:44 AM
|
 This is how they treat their users asking for recharge like any other decent casino by the way. Do the math and judge if you want to play here lol Let me follow up on this tread. The support staff told you already everything that you need to verify the bets. They told you that we have changed the salt in January 2022. So, you don't even need to verify all bets since before January it used another salt ( see my provably fair event ). If you tell me your username, I'm happy to pull out all your bets so you can verify them. We will do another PF event and my colleagues admitted already the mistakes were on our side with that, for your report we rewarded you with 250 USD. However, that doesnt mean that the game is unfair. You can still verify it with the verifier. If the developer sends you the first round hash, you can go through probably 250k games and verify each by each if that makes you happy. After that, you continue to try to extort us by claiming that we can manipulate futures rounds by changing the seed back and forth and if we don't pay you you will make it public... If you think so, please tell me us your username, ( which you have refused to ) so that we can pull up all your bets and verify them with you immediately. You are not acting in favor of the community or trying to "expose" something... As you said in your "scam accusation thread " All is well all that ends well, send me the money compensation and we'll forget about it. You are just someone who is trying to blackmail us for money. On top of that, you were spamming our telegram group and sending to all our staff DMs. That's the reason why you got banned on our social Media. Now you are insulting our staff by telling them they are "dumb"? My colleague Dennis did everything perfectly, and you have refused to 1.) Wait for a reply from the developers about the first round hash with the new salt ( which is anyways nonsense because you don't care about it, you just look for a reason to blackmail us) 2.) Tell us your username, where we could pull out immediately all your bets and verify them. That being said. I won't continue to discuss with you because it's a waste of time to talk with a "criminal" who blackmails people. |
|
|
|
|
7
|
Economy / Gambling / Re: Pasino.com Provably Fair Seeding Event for Fortune Wheel
|
on: May 30, 2022, 06:03:22 PM
|
Unfortunately your seeding event is missing one critical component: You didn't explain how you "interpret" a game hash. You should publish a function and game rules before the seed is picked. That way we know you can't tailor your interpret (i.e. hashToGameResult) function based on the future results
My apologies for not including the algorithm in the ANN. The code is open source and can be found on our verifier page (by checking the source code using CTRL + U). All calculations are performed on the client-side. function calculateWheelResult() {
var wheel_outcomes = ["1X", "6X", "1X", "12X", "1X", "3X", "1X", "6X", "1X", "3X", "1X", "52XA", "1X", "3X", "1X", "6X", "3X", "1X", "12X", "1X", "6X", "1X", "3X", "1X", "25X", "1X", "3X", "1X", "6X", "1X", "3X", "1X", "12X", "1X", "6X", "1X", "3X", "1X", "52XB", "3X", "1X", "3X", "1X", "3X", "1X", "12X", "1X", "6X", "1X", "3X", "1X", "25X", "1X", "3X"];
var client_seed = "00000000000000000000193048476f981a835cd00964b50043fb660f771dc2c3";
var last_seed = $("#server_seed").val();
var games = 10;
var actual_hash;
var p1, p2, p3, p4, roll, crash_point;
$("#tabled > tbody").html("");
for (x = 0; x <= games; x++) {
var md = forge.md.sha512.create();
md.update(client_seed + "-" + last_seed);
actual_hash = md.digest().toHex();
p1 = parseInt((actual_hash.substr(0, 2) + "").replace(/[^a-f0-9]/gi, ""), 16);
p2 = parseInt((actual_hash.substr(2, 2) + "").replace(/[^a-f0-9]/gi, ""), 16);
p3 = parseInt((actual_hash.substr(4, 2) + "").replace(/[^a-f0-9]/gi, ""), 16);
p4 = parseInt((actual_hash.substr(6, 2) + "").replace(/[^a-f0-9]/gi, ""), 16);
roll = toFixed((p1 / Math.pow(256, 1) + p2 / Math.pow(256, 2) + p3 / Math.pow(256, 3) + p4 / Math.pow(256, 4)), 12);
outcome = toFixed((roll * 53), 0);
outcome = wheel_outcomes[outcome];
$("#tabled > tbody").append("<tr>" + "<td>" + last_seed + "</td>" + "<td>" + outcome + "</td>" + "</tr>");
var md = forge.md.sha256.create();
md.update(last_seed);
last_seed = md.digest().toHex();
}
}The above code assumes that Forge (a library for cryptography is loaded on the page). Please refer to our website for more information: https://pasinocom.github.io/pasino-verify/fortune-quest.htmlThe code for the verifier is contained in the app.js file: https://pasinocom.github.io/pasino-verify/assets/js/app.jsThank you for your recommendations and suggestions. We'll keep them in mind and certainly implement the suggested improvements in our subsequent game releases. |
|
|
|
|
9
|
Economy / Gambling / Pasino.com Provably Fair Seeding Event for Fortune Wheel
|
on: May 11, 2022, 01:30:39 PM
|
|
Welcome to the Pasino Provably Fair Seeding Event for Fortune Wheel!
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: 172cb498b3df5f017c3763b6685f8b8e972054ab5101075413b1fb9d1ca58b15, 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 736013
Using our chosen starting serverSeed, the hash terminating the chain is 172cb498b3df5f017c3763b6685f8b8e972054ab5101075413b1fb9d1ca58b15. That is to say, the first game's hash played under the new provably fair scheme, when hashed will be 172cb498b3df5f017c3763b6685f8b8e972054ab5101075413b1fb9d1ca58b15.
|
|
|
|
|
11
|
Economy / Gambling / New Pasino.com Provably Fair Seeding Event for Crash!
|
on: November 29, 2021, 05:55:20 AM
|
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 711779The reference code (javascript) is as follows: 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: 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: 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. |
|
|
|
|
12
|
Economy / Gambling / Re: Pasino.com Provably Fair Seeding Event for Crash!
|
on: April 13, 2021, 12:14:50 PM
|
Thank you very much for archive and quote the thread!  I confirm Block 678978 is mined and our client seed will be: 0000000000000000000aa2dfb666783e6f5e100eefab4cd8756a359e7c247d1eWe have also updated the our verifier page: https://pasinocom.github.io/pasino-verify/crash.htmlPasino.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: 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: 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: 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.htmlhttps://ninjastic.space/post/56765148https://archive.is/wip/cwImK |
|
|
|
|
13
|
Economy / Gambling / Pasino.com Provably Fair Seeding Event for Crash!
|
on: April 12, 2021, 12:31:31 PM
|
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 678978The reference code (javascript) is as follows: 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: 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: 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. |
|
|
|
|
14
|
Economy / Gambling / Re: FaucetPay.io Provably Fair Seeding Event for Crash!
|
on: June 26, 2020, 12:31:02 PM
|
I tried Paid to click ? after clicked and see ads reference, my balance still 0, where to credited? How much Wagered/day on a crash game? I see small wagering only.  this, https://faucetpay.io/dice < recent bet running like crazy. maybe a hundred wagered per second. Yes, many people playing with little amounts. We are a microwallet, therefore it's pretty normal that they are playing with "micro" amounts. Also, we've just changed our contest to a daily one. You can win now up to $275 every day! |
|
|
|
|
16
|
Economy / Gambling / Re: FaucetPay.io Provably Fair Seeding Event for Crash!
|
on: June 17, 2020, 07:18:15 PM
|
A faucet payment processor along with gambling and trading? Sounds like a one stop hub for all the need. Good collection of services to stand alone and tall  . You got bunch of services which must need big team to manage; am not sure how effectively your team is going to handle like you may need to watch which faucet is going dry and might need to be removed from listing and updating sports events accordingly under sportsbetting. (Right now under cricket there is match for Eng vs WI on July whereas cricinfo is not showing anything like that but there is match between Ireland vs NZ on 19th June 2020; just 2 more days left which is missing in your listing) I mean running a dicing or faucet payment processor alone is something different than running a collection of services/businesses. If you are able to manage perfectly then this website may unveil huge potential beyond your dreams. Good luck! Thanks for the feedback! We really appreciate it Our Sportsbetting API provider isn't the best, to be honest. We are already in talks with a new provider and hopefully, we can implement the new one soon. |
|
|
|
|
18
|
Economy / Gambling / Re: FaucetPay.io Provably Fair Seeding Event for Crash!
|
on: June 15, 2020, 11:05:39 AM
|
Welcome to the FaucetPay 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: e3ac72b2b84cb8b64669e0441e50bb24834980ed065a479113505c0984ac32c5, by publicizing it here we are preventing any ability to pick an alternate sha256 chain. FaucetPay.io 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 635017The reference code (javascript) is as follows: 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: 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: 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 e3ac72b2b84cb8b64669e0441e50bb24834980ed065a479113505c0984ac32c5. That is to say, the first game's hash played under the new provably fair scheme, when hashed will be e3ac72b2b84cb8b64669e0441e50bb24834980ed065a479113505c0984ac32c5. Quoted to make sure nothing changes. Archived the Opening post to make sure nothing changes -> https://web.archive.org/web/20200615104847/https://bitcointalk.org/index.php?topic=5255740.msg54623486Awesome! Thank you. |
|
|
|
|
19
|
Economy / Gambling / FaucetPay.io Provably Fair Seeding Event for Crash!
|
on: June 15, 2020, 10:43:37 AM
|
Welcome to the FaucetPay 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: e3ac72b2b84cb8b64669e0441e50bb24834980ed065a479113505c0984ac32c5, by publicizing it here we are preventing any ability to pick an alternate sha256 chain. FaucetPay.io 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 635017The reference code (javascript) is as follows: 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: 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: 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 e3ac72b2b84cb8b64669e0441e50bb24834980ed065a479113505c0984ac32c5. That is to say, the first game's hash played under the new provably fair scheme, when hashed will be e3ac72b2b84cb8b64669e0441e50bb24834980ed065a479113505c0984ac32c5. |
|
|
|
|
