Crypto casino proof of reserves, explained

Proof of reserves (PoR) means showing, on-chain, that an operator holds enough crypto to cover what it owes players. Because public blockchains let anyone read the balance of any address, once a casino's hot and cold wallets are identified, their total balance is independently verifiable — no need to trust the operator's word, a press release, or a screenshot. It is the single most objective solvency signal available for an industry that is otherwise opaque and largely unregulated.

The idea was popularised by crypto exchanges after several high-profile collapses, where customers discovered too late that the funds they thought were custodied simply weren't there. The same failure mode applies to a casino: your deposit sits in the operator's wallet until you withdraw, and nothing on the website tells you whether that wallet is actually funded.

This distinction is the one most players miss, and it matters. Proof of reserves shows that assets exist at a set of addresses. Proof of custody would additionally show that the operator exclusively controls those assets and that they are not double-counted, borrowed for the snapshot, or pledged elsewhere. On-chain balances alone cannot prove custody: a wallet can be funded with borrowed crypto minutes before a snapshot and emptied afterwards.

So a reserve figure answers "do the funds exist right now?" — not "are they really the operator's, free and clear, and enough to cover everyone?" That gap is why we never present reserves as a clean bill of health, and why a single snapshot should never be the only thing you look at.

Crypto casinos are unregulated in most markets, so there is no deposit insurance, no ombudsman, and no auditor of last resort. The dominant risk to a player is not a rigged game — provably-fair systems are common — it is the operator becoming insolvent, throttling withdrawals, or exit-scamming. Visible, stable on-chain reserves that comfortably exceed near-term withdrawal demand are the strongest available signal that withdrawals can be honoured today. Thin reserves, or reserves that only appear around withdrawal times, are the opposite.

We map wallets to operators from public block-explorer name-tags and on-chain behaviour (a confirmed deposit address is expanded to a wallet cluster using the standard common-input-ownership heuristic), then read their balances of stablecoins and major assets across every chain we track and price them in USD. Crucially, we publish a coverage level — how complete our wallet mapping is for that brand — instead of a single "fully reserved" claim, and we never present an operator's self-reported figure as verified. Reserves are an all-chain, best-effort estimate and are partial by brand. The full process is documented in our proof-of-reserves methodology.

Don't read the dollar amount in isolation — read it three ways. Relative to flow: reserves should comfortably exceed recent withdrawal volume, not just be "a big number". Over time: a stable or rising reserve trend is reassuring; a balance that spikes right before known payout periods and drains afterwards is a classic dress-up pattern. Against coverage: a large figure at "low coverage" means we've mapped only part of the operator's wallets, so treat it as a floor, not a total. We pair every reserve figure with net flow and a trend precisely so it can't be read naively.

PoR proves assets, not liabilities: it cannot show how much an operator owes players, only what it holds. It is a point-in-time read on a moving target — balances change every block. It also can't see off-chain assets (fiat banking, custodial holdings) or off-chain debts. None of this makes it useless; it makes it one input. That is why we combine reserves with net flow, independent trust ratings, complaint trends and continuous monitoring rather than treating any single snapshot as proof of solvency.