Skip to content
Pre-launch, play-money platform. No gambling operating licence in any jurisdiction, no live payment processor, no operator in production. Everything stated on this site is something you can check.

Casino & aggregation

Provable fairness as a mechanism, not a badge.

31 in-house game engines — slots, crash, blackjack, roulette, video poker, baccarat, craps, sic bo, keno, plinko, mines, hi-lo, limbo, dice, wheel, scratch, three-card and Caribbean stud, penalty shootout, snooker, virtual racing and a two-player Chinchón table. Every round's server seed is committed before it plays and revealed after, so any outcome can be recomputed by anyone.

Provable fairness

Commit, play, reveal

The server seed for a round is hashed with HMAC-SHA256 and the hash is published before the round runs. The player supplies or edits their own client seed. The outcome is derived from both plus a nonce. Afterwards the server seed is revealed, and the player — or a regulator, or you — can re-derive the result and check it against the hash that was committed first.

1 Commit server seed hashed, hash published first 2 Client seed player supplies or edits their own 3 Play outcome = HMAC-SHA256 (server, client, nonce) 4 Reveal server seed published, hash re-checkable anyone can recompute the round and check it against the hash committed in step 1
Why the ordering matters: the operator commits to a seed they cannot change once the player has seen the hash, and the player influences the outcome through a seed the operator cannot predict. Neither side can move after the other has committed. That is what makes the claim checkable rather than a promise.

Game mathematics

RTP is solved, never typed

Every in-house title's return-to-player is calculated by a solver directly from its real paytable. No RTP figure anywhere on this platform was entered by hand — a hand-entered RTP is a number that gets typed once, published, and then never checked against the game again.

31in-house game engines, each with its mathematics under test
53titles configured in the demo catalogue
HMAC-SHA256commit–reveal on every round
0hand-typed RTP figures

Slots

A five-reel engine with a solver over the real paytable, plus seed commitments recorded per spin. The maths is in the repository and the solver output is reproducible from a clean checkout.

Crash, shared and solo

A seed chain with published commitments, a shared multiplayer round so every player sees the same curve, and configurable variants. The chain means a round's fairness is checkable retroactively, not just individually.

Tournaments & jackpots

Leaderboard tournaments over game rounds, sit-and-go tables, and progressive jackpots with recorded wins — all settling through the same wallet ledger as everything else.

Third-party content

The aggregator seam

Licensed casino content arrives through a seamless-wallet protocol: the provider holds no balance, and every stake and win round-trips to the Ledgerfield wallet in real time. Game sessions, rounds and provider reconciliation are modelled first-class, with refunds and cancellation handled as ledger events rather than balance edits.

The single largest gap on this site, stated first rather than lastThere is no licensed casino content on the platform today. The in-house titles are in-house mathematics awaiting test-house certification — they are not certified, and "provably fair" is a different property from "certified", not a substitute for it. The aggregator protocol is built and tested; the supplier contract that would put certified content through it is not signed. For a licensed operator that is the gating item, and we would rather you learned it on this page than on the third call.

What that means practicallyThe realistic shape of a first deployment is Ledgerfield as the PAM, wallet, sportsbook and compliance layer, with a certified aggregator supplying casino content through the protocol that already exists. That is a smaller, more honest claim than "we have a casino", and it is the one we can stand behind today.

Recompute a round yourself.

On the call we will play a round, hand you the revealed server seed, and let your engineer re-derive the outcome against the hash that was published before it ran.