Bustabit (v2) Seeding Event - page 2.

dooglus

legendary

Activity: 2940

Merit: 1333

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. Block 505750 still hasn't been mined.

DarkDays

legendary

Activity: 2030

Merit: 1189

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.

The current block is 505641.

DarkStar_

legendary

Activity: 2772

Merit: 3284

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.

dooglus

legendary

Activity: 2940

Merit: 1333

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.

dooglus

legendary

Activity: 2940

Merit: 1333

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.

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

Lionidas

hero member

Activity: 1008

Merit: 1012

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

joksim299

legendary

Activity: 2198

Merit: 1014

Bitdice is scam scam scammmmmmmmmmmmmmmmmmmmmmmmmm

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.

RHavar

legendary

Activity: 1463

Merit: 1886

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.

Topic: Bustabit (v2) Seeding Event - page 2. (Read 2785 times)