Bitcoin Forum

Economy => Gambling => Topic started by: RHavar on January 23, 2018, 12:05:18 AM


Title: Bustabit (v2) Seeding Event
Post by: RHavar on January 23, 2018, 12:05:18 AM
In a few days I will be releasing version 2 of bustabit. The principle of our provably fair system remains the same, but the algorithm that converts game hashes to game results has changed. Therefore I'm holding a new seeding event.

Starting with a secret I've generated a chain of 10,000,000 SHA256 hashes. Each element is the hash of the lowercase, hexadecimal string representation of the previous hash. The hash of the chain's last element is 86728f5fc3bd99db94d3cdaf105d67788194e9701bf95d049ad0e1ee3d004277.

Every game maps to a hash in the chain: The 10,000,000th element of the chain is the hash of game #1 and the first element in the chain is the hash of game #10,000,000. To verify that a hash belongs to a game #n, simply hash it n times and compare the result with the terminating hash.

To calculate a game's result from its hash:
Code:
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 505750. This block has not been mined yet, proving that I have not deliberately picked a chain that is unfavorable for players.

Title: Re: Bustabit (v2) Seeding Event
Post by: RHavar on January 23, 2018, 12:07:12 AM
To prevent editing of the OP, I have taken an archived snapshot of the page: http://archive.is/18raj   and ask that people quote and save the original post (and confirm that block 505750 is still not mined).

Title: Re: Bustabit (v2) Seeding Event
Post by: joksim299 on January 23, 2018, 12:46:42 AM
Quote from: RHavar on January 23, 2018, 12:05:18 AM
In a few days I will be releasing version 2 of bustabit. The principle of our provably fair system remains the same, but the algorithm that converts game hashes to game results has changed. Therefore I'm holding a new seeding event.

Starting with a secret I've generated a chain of 10,000,000 SHA256 hashes. Each element is the hash of the lowercase, hexadecimal string representation of the previous hash. The hash of the chain's last element is 86728f5fc3bd99db94d3cdaf105d67788194e9701bf95d049ad0e1ee3d004277.

Every game maps to a hash in the chain: The 10,000,000th element of the chain is the hash of game #1 and the first element in the chain is the hash of game #10,000,000. To verify that a hash belongs to a game #n, simply hash it n times and compare the result with the terminating hash.

To calculate a game's result from its hash:
Code:
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 505750. This block has not been mined yet, proving that I have not deliberately picked a chain that is unfavorable for players.

Title: Re: Bustabit (v2) Seeding Event
Post by: Lionidas on January 23, 2018, 01:21:41 AM
It has been a while since you announced a new version of the site would be released and I think it is just about time to unveil it.
Seems like a year now since I first heard about the site getting redesigned and slapping a Version 2 to the splash screen. ;)

Title: Re: Bustabit (v2) Seeding Event
Post by: dooglus on January 23, 2018, 02:13:06 AM
Quote from: RHavar on January 23, 2018, 12:05:18 AM
In a few days I will be releasing version 2 of bustabit. The principle of our provably fair system remains the same, but the algorithm that converts game hashes to game results has changed. Therefore I'm holding a new seeding event.

Starting with a secret I've generated a chain of 10,000,000 SHA256 hashes. Each element is the hash of the lowercase, hexadecimal string representation of the previous hash. The hash of the chain's last element is 86728f5fc3bd99db94d3cdaf105d67788194e9701bf95d049ad0e1ee3d004277.

Every game maps to a hash in the chain: The 10,000,000th element of the chain is the hash of game #1 and the first element in the chain is the hash of game #10,000,000. To verify that a hash belongs to a game #n, simply hash it n times and compare the result with the terminating hash.

To calculate a game's result from its hash:
Code:
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 505750. This block has not been mined yet, proving that I have not deliberately picked a chain that is unfavorable for players.

Ryan asked me to quote this. So I'm quoting this.

Title: Re: Bustabit (v2) Seeding Event
Post by: dooglus on January 23, 2018, 02:16:05 AM
The current Bitcoin block height is 505626 by the way. Block 505750 hasn't been mined yet, but will be in the next 24 hours or so.

Title: Re: Bustabit (v2) Seeding Event
Post by: DarkStar_ on January 23, 2018, 02:49:45 AM
Quote from: RHavar on January 23, 2018, 12:05:18 AM
In a few days I will be releasing version 2 of bustabit. The principle of our provably fair system remains the same, but the algorithm that converts game hashes to game results has changed. Therefore I'm holding a new seeding event.

Starting with a secret I've generated a chain of 10,000,000 SHA256 hashes. Each element is the hash of the lowercase, hexadecimal string representation of the previous hash. The hash of the chain's last element is 86728f5fc3bd99db94d3cdaf105d67788194e9701bf95d049ad0e1ee3d004277.

Every game maps to a hash in the chain: The 10,000,000th element of the chain is the hash of game #1 and the first element in the chain is the hash of game #10,000,000. To verify that a hash belongs to a game #n, simply hash it n times and compare the result with the terminating hash.

To calculate a game's result from its hash:
Code:
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 505750. This block has not been mined yet, proving that I have not deliberately picked a chain that is unfavorable for players.

Title: Re: Bustabit (v2) Seeding Event
Post by: DarkDays on January 23, 2018, 03:59:12 AM
Quote from: RHavar on January 23, 2018, 12:05:18 AM
In a few days I will be releasing version 2 of bustabit. The principle of our provably fair system remains the same, but the algorithm that converts game hashes to game results has changed. Therefore I'm holding a new seeding event.

Starting with a secret I've generated a chain of 10,000,000 SHA256 hashes. Each element is the hash of the lowercase, hexadecimal string representation of the previous hash. The hash of the chain's last element is 86728f5fc3bd99db94d3cdaf105d67788194e9701bf95d049ad0e1ee3d004277.

Every game maps to a hash in the chain: The 10,000,000th element of the chain is the hash of game #1 and the first element in the chain is the hash of game #10,000,000. To verify that a hash belongs to a game #n, simply hash it n times and compare the result with the terminating hash.

To calculate a game's result from its hash:
Code:
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 505750. This block has not been mined yet, proving that I have not deliberately picked a chain that is unfavorable for players.

The current block is 505641.

Title: Re: Bustabit (v2) Seeding Event
Post by: dooglus on January 23, 2018, 08:10:49 AM
I put the sha256 hash of OP's message in the Bitcoin blockchain:

Quote
# download a copy of the message
$ wget -q https://just-dice.com/misc/signing-event-2.txt

# show the start of its first line
$ head -n 1 signing-event-2.txt | cut -c 1-150
In a few days I will be releasing version 2 of bustabit. The principle of our provably fair system remains the same, but the algorithm that converts g

# show the start of its last line
$ tail -n 1 signing-event-2.txt | cut -c 1-150
Before being used to calculate the corresponding result, each game hash is salted with the lowercase, hexadecimal string representation of the hash of

# compute the hash of the message
$ sha256sum signing-event-2.txt
a015693871d8bde65f57ec82f52f6b192e9a11fa26a37e63e17dc3092c6c7fab  signing-event-2.txt

# create, sign, and broadcast a transaction containing the hash
$ bitcoin-cli sendrawtransaction $(bitcoin-cli signrawtransaction $(bitcoin-cli createrawtransaction '[{"txid":"2c5a01bc4bfb0dfde815ebbe7f08e0c93c3b2d40d220021095c06938abf3b29e","vout":0}]' '{"bc1qnle0kjvz4wyju49m00krxztdqu5ygak00nft37":1.265456, "data":"a015693871d8bde65f57ec82f52f6b192e9a11fa26a37e63e17dc3092c6c7fab"}' 0 true) | grep hex | cut -d'"' -f4)
b6439e1c9eb3915b3cc89871d2c2479f3f1847f0c7bab252c3ebc503b8f6d344

# check that the transaction includes the hash of the message
$ bitcoin-cli getrawtransaction b6439e1c9eb3915b3cc89871d2c2479f3f1847f0c7bab252c3ebc503b8f6d344 true | grep "RETURN a01569"
        "asm": "OP_RETURN a015693871d8bde65f57ec82f52f6b192e9a11fa26a37e63e17dc3092c6c7fab",

It was included in block 505672 (https://live.blockcypher.com/btc/tx/b6439e1c9eb3915b3cc89871d2c2479f3f1847f0c7bab252c3ebc503b8f6d344/). Block 505750 still hasn't been mined.

Title: Re: Bustabit (v2) Seeding Event
Post by: Luxo42 on January 23, 2018, 09:16:19 AM
Quote from: RHavar on January 23, 2018, 12:05:18 AM
In a few days I will be releasing version 2 of bustabit. The principle of our provably fair system remains the same, but the algorithm that converts game hashes to game results has changed. Therefore I'm holding a new seeding event.

Starting with a secret I've generated a chain of 10,000,000 SHA256 hashes. Each element is the hash of the lowercase, hexadecimal string representation of the previous hash. The hash of the chain's last element is 86728f5fc3bd99db94d3cdaf105d67788194e9701bf95d049ad0e1ee3d004277.

Every game maps to a hash in the chain: The 10,000,000th element of the chain is the hash of game #1 and the first element in the chain is the hash of game #10,000,000. To verify that a hash belongs to a game #n, simply hash it n times and compare the result with the terminating hash.

To calculate a game's result from its hash:
Code:
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 505750. This block has not been mined yet, proving that I have not deliberately picked a chain that is unfavorable for players.
Finally!

Title: Re: Bustabit (v2) Seeding Event
Post by: Luxo42 on January 23, 2018, 09:32:51 AM
So, house edge is fixed now at 1%
And 0.99x busts are present

Title: Re: Bustabit (v2) Seeding Event
Post by: xxjumperxx on January 23, 2018, 01:23:38 PM
Quote from: RHavar on January 23, 2018, 12:05:18 AM
In a few days I will be releasing version 2 of bustabit. The principle of our provably fair system remains the same, but the algorithm that converts game hashes to game results has changed. Therefore I'm holding a new seeding event.

Starting with a secret I've generated a chain of 10,000,000 SHA256 hashes. Each element is the hash of the lowercase, hexadecimal string representation of the previous hash. The hash of the chain's last element is 86728f5fc3bd99db94d3cdaf105d67788194e9701bf95d049ad0e1ee3d004277.

Every game maps to a hash in the chain: The 10,000,000th element of the chain is the hash of game #1 and the first element in the chain is the hash of game #10,000,000. To verify that a hash belongs to a game #n, simply hash it n times and compare the result with the terminating hash.

To calculate a game's result from its hash:
Code:
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 505750. This block has not been mined yet, proving that I have not deliberately picked a chain that is unfavorable for players.


I have been waiting a while for BaB2.

Title: Re: Bustabit (v2) Seeding Event
Post by: Lionidas on January 23, 2018, 03:53:56 PM
Yeah I have been waiting for this site release for a while.
Can't wait to pour another close to 5btc into this reloaded version of the site now. :D

When will it be officially launched and will you be having some kind of competition during the launch? ;D

Title: Re: Bustabit (v2) Seeding Event
Post by: RHavar on January 23, 2018, 03:54:49 PM
Thanks everyone! (Especially dooglus for embedding the hash in the blockchain!)


Quote from: Luxo42 on January 23, 2018, 09:32:51 AM
So, house edge is fixed now at 1%
And 0.99x busts are present

Almost! The last line:

Code:
Math.max(1, result / 100)

Guarantees no bust is less than 1  (but 1.01x will be the min cash out)

Title: Re: Bustabit (v2) Seeding Event
Post by: hopenotlate on January 23, 2018, 06:55:34 PM
Quote from: RHavar on January 23, 2018, 12:05:18 AM
In a few days I will be releasing version 2 of bustabit. The principle of our provably fair system remains the same, but the algorithm that converts game hashes to game results has changed. Therefore I'm holding a new seeding event.

Starting with a secret I've generated a chain of 10,000,000 SHA256 hashes. Each element is the hash of the lowercase, hexadecimal string representation of the previous hash. The hash of the chain's last element is 86728f5fc3bd99db94d3cdaf105d67788194e9701bf95d049ad0e1ee3d004277.

Every game maps to a hash in the chain: The 10,000,000th element of the chain is the hash of game #1 and the first element in the chain is the hash of game #10,000,000. To verify that a hash belongs to a game #n, simply hash it n times and compare the result with the terminating hash.

To calculate a game's result from its hash:
Code:
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 505750. This block has not been mined yet, proving that I have not deliberately picked a chain that is unfavorable for players.

Really curious to see V2

Quoting for reference.


Edit: just noticed Dooglus did it way better than me

Title: Re: Bustabit (v2) Seeding Event
Post by: RHavar on January 23, 2018, 08:32:43 PM
Block 505750 has been mined, so we have our client seed: 0000000000000000004d6ec16dafe9d8370958664c1dc422f452892264c59526

Title: Re: Bustabit (v2) Seeding Event
Post by: Dexon on January 23, 2018, 11:09:34 PM
Quote from: RHavar on January 23, 2018, 08:32:43 PM
Block 505750 has been mined, so we have our client seed: 0000000000000000004d6ec16dafe9d8370958664c1dc422f452892264c59526

Hype :D

Title: Re: Bustabit (v2) Seeding Event
Post by: Pali on January 26, 2018, 05:39:33 PM
Awesome news, people will be peaked for the new release  :)

Title: Re: Bustabit (v2) Seeding Event
Post by: RHavar on January 26, 2018, 09:55:13 PM
Quote from: cryptotricks on January 26, 2018, 09:03:22 PM
Waiting...

If everything goes according to plan, it should be launched in < 24 hours =)

Title: Re: Bustabit (v2) Seeding Event
Post by: Paractor on January 26, 2018, 09:58:31 PM
Quote from: RHavar on January 26, 2018, 09:55:13 PM
Quote from: cryptotricks on January 26, 2018, 09:03:22 PM
Waiting...

If everything goes according to plan, it should be launched in < 24 hours =)
That soon? :o
Congratulations on a timely release then.
Can't wait to get busting my bits on there. ;D

Title: Re: Bustabit (v2) Seeding Event
Post by: dooglus on January 26, 2018, 11:11:19 PM
Quote from: vadoff on January 26, 2018, 10:53:40 PM
Ryan, when Bustabit v1 is taken down, could you reveal the 10,000,000th game's hash (the first generated hash)? For legitness.

Why would you care about the hashes of any of the games which were never played?

Do you realize that all the games which have been played can already be verified?

Title: Re: Bustabit (v2) Seeding Event
Post by: RHavar on January 27, 2018, 01:04:38 AM
Quote from: dooglus on January 26, 2018, 11:11:19 PM
Why would you care about the hashes of any of the games which were never played?

Do you realize that all the games which have been played can already be verified?

It might make sense to look at future games, to check if that's the motivation for the new hash chain (or the timing of the release of it). I honestly have never looked "at the future" (although I can't prove that) so I don't know what the games are like -- but to answer @vadoff's question: I have no problems releasing the first generated hash to let everyone view the chain in it's entirety. It won't be the first thing I do after the launch of v2, but once I have a free 20 minutes I'll be happy to post it here =)

Title: Re: Bustabit (v2) Seeding Event
Post by: dooglus on January 27, 2018, 08:01:08 AM
Quote from: RHavar on January 27, 2018, 01:04:38 AM
It might make sense to look at future games, to check if that's the motivation for the new hash chain (or the timing of the release of it).

Oh yes, that's a good point. It could be that the players were due for a good green streak, and so you've decided to switch to a new random sequence.

It seems unlikely that there are any long enough streaks to make it worth your while switching, but at least it's a plausible reason for people to want to be able to examine the whole chain.

Title: Re: Bustabit (v2) Seeding Event
Post by: RHavar on January 27, 2018, 04:03:22 PM
Bustabitv2 has been launched (under new ownership)!


The original hash for v1 provably fair was "ac4b6c46171daa0189b679bd7523c7bab6410f7155a21635b7e0ecdf370a9000" if anyone wants to check future games

Title: Re: Bustabit (v2) Seeding Event
Post by: boyka2 on January 27, 2018, 04:07:01 PM
hi Ryan ,
Please tell me old Bot work here

Title: Re: Bustabit (v2) Seeding Event
Post by: Lionidas on January 27, 2018, 05:43:22 PM
Quote from: RHavar on January 27, 2018, 04:03:22 PM
Bustabitv2 has been launched (under new ownership)!


The original hash for v1 provably fair was "ac4b6c46171daa0189b679bd7523c7bab6410f7155a21635b7e0ecdf370a9000" if anyone wants to check future games
Congratulations on the new launch of the site.
I am assuming it is the same old website address because there was nothing telling us different to use to get to the V2 of the site.
Just hope it allows users to win something just like bustadice did in it's first few days. ;)

Title: Re: Bustabit (v2) Seeding Event
Post by: DarkDays on January 27, 2018, 07:14:54 PM
No bonus aspect of the game?

Not run by Ryan?

Pass.

Title: Re: Bustabit (v2) Seeding Event
Post by: Dexon on January 27, 2018, 10:52:29 PM
Here's a script to verify the games on v2: https://jsfiddle.net/Dexon95/2fmuxLza/embedded/result/

Title: Re: Bustabit (v2) Seeding Event
Post by: devans on February 07, 2018, 02:58:23 PM
I've put together a short overview of what's new in version 2 of bustabit in its new announcement thread (https://bitcointalk.org/index.php?topic=2897545.0). I'll post all news and future updates there as well.

Title: Re: Bustabit (v2) Seeding Event
Post by: ubglottery on April 15, 2018, 05:10:54 PM
is possible 3 times x1 in a row?

ì

Title: Re: Bustabit (v2) Seeding Event
Post by: HiDevin on April 15, 2018, 05:23:30 PM
Quote from: ubglottery on April 15, 2018, 05:10:54 PM
is possible 3 times x1 in a row?

ì


not to sidetrack, but on Bustabit v1 i seen 4 1x mixed in with 0x in a row

Title: Re: Bustabit (v2) Seeding Event
Post by: team.taoist on November 26, 2018, 10:04:03 AM
Is there any way to prove house edge is 1%?

Title: Re: Bustabit (v2) Seeding Event
Post by: Saint-loup on May 29, 2020, 05:37:54 PM
Quote from: team.taoist on November 26, 2018, 10:04:03 AM
Is there any way to prove house edge is 1%?
Yes! RHavar has just explained it in another thread :

Quote from: RHavar on May 29, 2020, 05:08:52 PM
Quote from: Saint-loup on May 29, 2020, 04:31:15 PM
Thank you very much for these very precise and clear clarifications RHavar.  :)

But now, I don't understand why you're dividing "97" by this number :
crash = Math.floor(97 / crash);

I'm sorry for these questions but I'm trying to understand how that works.
TYVM RHavar

So the first thing to note is that a final outcome of 123 means a multiplier of 1.23x. So `123 / crash` is easier to reason about if you think of it more like `1.23/crash` in maths terms. And as we already discussed, `crash` is evenly distributed between 0 and 1. So if you wanted to simply turn it into a multiplier you'd do:   `100 / crash`  ... but no casino is going to do that, as they need a house edge for themselves. I know bustabit effectively uses `99 / crash` to make a house edge of 1%, but rocketpot is using `97 / crash` which is going to result in a significantly higher edge (of which some will be used to fund the bonuses/jackpots/other benefit thats bustabit might not have).

It's the "99" of
Code:
// 4. X = 99 / (1-X)
  X = 99 / (1 - X)

Title: Re: Bustabit (v2) Seeding Event
Post by: Vyrine on February 15, 2021, 02:25:16 PM
Quote from: RHavar on January 27, 2018, 04:03:22 PM
Bustabitv2 has been launched (under new ownership)!


The original hash for v1 provably fair was "ac4b6c46171daa0189b679bd7523c7bab6410f7155a21635b7e0ecdf370a9000" if anyone wants to check future games

Can I know what hash is used after the Bustabit v1? I can't find these hashes "ac4b6c46171daa0189b679bd7523c7bab6410f7155a21635b7e0ecdf370a9000" and "86728f5fc3bd99db94d3cdaf105d67788194e9701bf95d049ad0e1ee3d004277" on 4.2 million hashes.

Edit: Nevermind, I've found it. 9f57575fd54cd441e962448537e155ace9555df10cd27fa817bbcaf48a59ebcf


Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines