the amount that you send must be at least equal to the minimum amount...

...and at most equal to the maximum amount of the game you are playing

you can find the minimum and maximum amounts next to the game bars

That's it, wait for your bet to appear at the top of the game area!

Valid bets

Invalid bets

Good to know

You can highlight your own bets by entering your bitcoin address into the box located at
the top-right of the game area. If you do so, a special sound will indicate bets that come from your
address. All other bets will be displayed semi-transparent. Additionally, you will see your last
five bets in your personal table.

The box located at the top-right of the game area also features a chat that you can use to
chat with other players. See you there!

You can hover the falling coins or the multipliers with your mouse to get more info.

Some more technical details

Transaction fees

Very large wins

Suspicious transactions

Frequently Ask Questions

Does LuckyBit have a faucet?

How can I check if my bet was processed by LuckyBit?

Why my bet does not show up immediately on LuckyBit?

My payout transaction isn't found on block explorers!

I got a large win, but did not receive my payout immediately as usual.

How does the chat lottery work?

What is the shiny BONUS coin?

Why is this page taking so much CPU?

It is the price to pay for fancy javascript animations. We are working on improvements!

The origins of LuckyBit

Your odds in LuckyBit

Lucky Bit is provably fair

The key that LuckyBit uses to determine the "lucky moves" of a bet, and thus the winning amount,
is changed every day;

The key of a given day is made public after midnight of the next day;

The respective hashes of all keys, past and future, have been
published and prove that LuckyBit uses the correct key for each day;

Nobody can modify this file, as its hash is recorded in the blockchain
as of 10th of September, 2013;

You can verify each bet in the film fast five, which is
also accessible at the bottom of the main page.

Need more technical details?

Your lucky moves are determined using a hash of the following string:

<tx_id>:<vout_id>:<secret_key>

, where:

<tx_id>

is the transaction id of your bet as assigned by your wallet.
(This data is controlled by you.)

<vout_id>

is the rank of the output of your bet within the transaction's
list of outputs. (Rank starts at 0 and is controlled by you.)
This produces different lucky moves for each bet if you play several bets
within a single transaction.

<secret_key>

is the secret key of the day. It is unknown to you
at the time of playing, but the hashes of all keys have been are published in advance, so nobody can
modify these keys. The day of your bet is determined by the moment LuckyBit receives your bet's
transaction. (Typically 1 to 10 seconds after you sent it.)

From the hash of

<tx_id>:<vout_id>:<secret_key>

, LuckyBit takes the
binary representation of the last 2 bytes and read it from the left side. The bits determine
your lucky moves: A

1

translates to a right move, a

0

to a left move. For instance, if the hexadecimal
hash ends with

ffff

, your coin would always go right
as the binary string would contain sixteen

1

and no

0

You can easily verify that your lucky moves were correct by computing the hash of the string

<tx_id>:<vout_id>:<secret_key>

of your bet.
There are many websites that allow you to do this, for example:

The key of each day is made public after midnight (UTC). LuckyBit can prove that nobody changed this key afterwards
because the hashes of all keys, past and future, have been published in this file:
http://luckyb.it/secret-key-hashes.txt

The file that contains all key hashes has itself the following hash:

e45fb03ae911b267615bc923803bc553adb0e3dd6c9e47c939073f30ec912a63

You can compute the hash of this file as follows (on Linux/Mac):

curl -s http://luckyb.it/secret-key-hashes.txt | shasum -a 256 -t

Using the hash of this file as a bitcoin private key, it produces the
following bitcoin address:

1L85BxKU6J169kM934PQyV52maHmE86cFc

. We have sent a transaction to
this address on the 10/09/2013 (included in block 257126). You can verify this on any block explorer, for example: