Bustabit (v2) Seeding Event | Bitcointalksearch.org

Vyrine

newbie

Activity: 14

Merit: 28

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

Saint-loup

legendary

Activity: 2604

Merit: 2353

Quote from: team.taoist on November 26, 2018, 05: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, 12:08:52 PM

Quote from: Saint-loup on May 29, 2020, 11:31:15 AM

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)

team.taoist

newbie

Activity: 47

Merit: 0

Is there any way to prove house edge is 1%?

HiDevin

member

Activity: 226

Merit: 30

so.. hru?

Quote from: ubglottery on April 15, 2018, 12: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

ubglottery

copper member

Activity: 32

Merit: 0

is possible 3 times x1 in a row?

ì

devans

sr. member

Activity: 528

Merit: 368

I've put together a short overview of what's new in version 2 of bustabit in its new announcement thread. I'll post all news and future updates there as well.

Dexon

full member

Activity: 230

Merit: 154

I'm a web dev :D

Here's a script to verify the games on v2: https://jsfiddle.net/Dexon95/2fmuxLza/embedded/result/

DarkDays

legendary

Activity: 2030

Merit: 1189

No bonus aspect of the game?

Not run by Ryan?

Pass.

Lionidas

hero member

Activity: 1008

Merit: 1012

Quote from: ?? on ??

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. Wink

boyka2

newbie

Activity: 11

Merit: 0

hi Ryan ,
Please tell me old Bot work here

dooglus

legendary

Activity: 2940

Merit: 1333

Quote from: ?? on ??

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.

dooglus

legendary

Activity: 2940

Merit: 1333

Quote from: ?? on ??

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?

Paractor

full member

Activity: 274

Merit: 133

Quote from: ?? on ??

Waiting...

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

That soon? Shocked

Congratulations on a timely release then.
Can't wait to get busting my bits on there. Grin

Pali

member

Activity: 221

Merit: 13

Awesome news, people will be peaked for the new release

Dexon

full member

Activity: 230

Merit: 154

I'm a web dev :D

Quote from: ?? on ??

Block 505750 has been mined, so we have our client seed: 0000000000000000004d6ec16dafe9d8370958664c1dc422f452892264c59526

Hype

hopenotlate

legendary

Activity: 3402

Merit: 1227

Top Crypto Casino

Quote from: RHavar on January 22, 2018, 07:05:18 PM

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

Lionidas

hero member

Activity: 1008

Merit: 1012

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. Cheesy

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

xxjumperxx

sr. member

Activity: 574

Merit: 272

Buy Bitcoin!

Quote from: RHavar on January 22, 2018, 07:05:18 PM

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.

Luxo42

member

Activity: 126

Merit: 22

So, house edge is fixed now at 1%
And 0.99x busts are present

Luxo42

member

Activity: 126

Merit: 22

Quote from: RHavar on January 22, 2018, 07:05:18 PM

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!

Topic: Bustabit (v2) Seeding Event (Read 2775 times)