Rules

You can set your bet number on the My Bets page. Your browser timelock-encrypts the number and sends only the ciphertext to the server — the plain number never leaves your device. Nobody, not even the host, can read your bet until the round closes.

How to enter

1. On My Bets, type your number and set the bet — it's encrypted in your browser first.
2. Send Xanax to TimTommerson [3936502] to fund your balance — the message doesn't matter, every send counts. Your number comes only from the bet you set here, never from the message.
3. Your bet goes live the moment your balance reaches the bet cost (1 Xanax). The two steps can happen in either order.

Balance & rollover

Xanax you send accumulates as an unused balance. Each live bet costs 1; any leftover rolls over to future rounds and is never reset. Xanax that never funds a live bet stays as your balance — nothing is auto-refunded, though the host can send it back manually.

Changing your bet

While your bet is staged (balance below the cost) you can freely re-set your number — the old ciphertext is replaced, nothing is staked yet. Once it goes live it is locked for the round and cannot be changed. The My Bets page removes the input once your bet is live.

Why the host can't peek (and can't fake it)

Timelock encryption uses the drand quicknet beacon — a network of independent nodes that publishes one unpredictable random value every 3 seconds on a fixed schedule. Your bet is encrypted to the beacon value for the round's close time. Before that time the decryption key does not exist anywhere; at that time it becomes public to everyone. So the host physically cannot decrypt early — this isn't a promise, it's math.

Verify your own bet after close

After the round closes the beacon is public, so anyone can decrypt any bet's ciphertext. To confirm yours was recorded unaltered: copy the ciphertext receipt shown on your My Bets page and decrypt it with drand's tle CLI —

tle -d bet.age        # returns your number

If it returns your number, your bet was stored exactly as you set it. This is a trustless proof — it relies on no promise from the host.

Prize payouts — a weaker guarantee

Every closed round also publishes the timestamp of the host's outgoing prize send, confirmed automatically from Torn's log. If you won, that timestamp and amount match the receive event in your own Torn log, so the host can't fake a payout to you. But this is winner-verifiable, not trustless — Torn exposes no public transfer record, so unlike the bet privacy above, it can't be proven to third parties. Two different trust levels, deliberately not conflated.