Docs/Resources/Transparency

Transparency

Llamabet prioritises transparency and fairness in everything we do. Our blackjack — and every Llamabet game — is provably fair, with outcomes you can independently reproduce and verify.

How provable fairness works

🧑

Client seed

You can supply your own client seed in the game settings, directly influencing how the deck is composed.

🔐

Server seed

The house generates a server seed and keeps it confidential until the session ends. Its hash is published to the blockchain hourly, committing to it in advance.

🎲

Nonce

Each round derives a nonce from your client seed, the server seed, and the game's timestamp — combined with Sui transaction data.

🃏

Deterministic deck

A deterministic process shuffles four decks per session, transparent and fully reproducible from the seeds.

Anchored on Sui

All relevant data — client seeds, server hashes, and gameplay details — is recorded on the Sui blockchain and remains publicly accessible. Because the server hash is committed before play and revealed after, the house cannot change an outcome once your bet is placed.

🔎Verify it yourself

Combine the revealed server seed with your client seed to recompute the exact deck and confirm the deal was never tampered with. You never have to take our word for it.

Disclosure: a gap in on-chain commitments, 26–28 July 2026

Between 26 July 2026, 17:00 UTC and 28 July 2026, 08:40 UTC — about 40 hours — the hourly transaction that records the server-seed commitment on Sui was failing. This affects blackjack, roulette and dice, which share that rotating seed. We are documenting it here rather than quietly fixing it, because a fairness page that only describes the good case is not a fairness page.

A security upgrade changed the contract to require that the dealer's signature cover the committed hash itself, instead of a fixed value. The off-chain signer was updated to match, but the two halves reached production at different times. For that window the contract rejected every commitment, and — this is the part that let it run for 40 hours rather than one — our code recorded the transaction reference without checking whether the transaction had actually succeeded. On Sui a failed transaction still returns a reference, so our own records showed commitments that the chain had rejected.

What this did and did not affect

✅

Deals were not affected

Seeds rotated hourly as normal and decks were derived exactly as documented. Nothing about how cards were shuffled or how any hand was settled changed.

✅

Still verifiable

Hands from that window can still be checked the usual way: combine the revealed server seed with your client seed and recompute the deck.

⚠️

The advance proof is missing

What is absent is the on-chain record proving the seed was committed BEFORE play. For that window you have our published seed and hash, but not the chain's timestamp on it.

🔒

Fixed and hardened

The contract was redeployed on 28 July and commitments resumed. The code now refuses to record a commitment unless the chain confirms it, and raises an alert when one fails.

To be plain about the limit of this: for those ~40 hours the strongest claim we can make is that the seeds are internally consistent and reproduce every deal — not that a third party can prove we fixed them in advance. Outside that window, and from 28 July onward, the on-chain commitment stands as described above. The redeployed contract and the transactions are on the contracts page if you want to check the timeline yourself.

Every address, in one place

The contracts that record those commitments, and the wallets the house uses, are listed on the contracts page with links to a public block explorer. It also shows what isn't deployed yet — including the $LLAMA token, which does not exist on mainnet. Player deposits and house revenue are held in separate wallets on purpose, so your balance is never counted as our profit.

← Previous

Play Responsibly

Resources

Next →

FAQs