How We Track Casino Wallets On-Chain

Every casino ranking site shows you bonuses and licenses. We show you the money — the flow of funds between players and casino wallets, recorded on public blockchains. Here's how the whole pipeline works.

Every casino ranking site shows you bonuses and licenses. We show you the money — literally: the flow of funds between players and casino wallets, recorded on public blockchains where nobody can edit history. Here's how the pipeline works, end to end.

It starts with a wallet registry

Everything we publish depends on one asset: a curated registry of casino wallets. Today it holds 386 addresses across 43 casinos and 8 chains — Bitcoin, Ethereum, BSC, Polygon, Base, Arbitrum, Tron and Solana.

Each entry is labeled with the casino, its role (hot wallet, cold storage, deposit processor) and a confidence source. Some addresses are published by casinos themselves, some are confirmed through deposit flows, and some come from community intelligence that we verify before including. You can browse the whole registry on our Wallet Registry page — we consider this transparency part of the product.

Collectors that never sleep

Every five minutes, our collectors ask each chain: what moved since we last checked?

• EVM chains — we read token and native transfers from block explorers, with a fallback that queries Transfer event logs directly from public RPC nodes when an explorer degrades
• Tron and Solana — chain-specific APIs, same normalized output
• Stablecoins first — USDT, USDC, DAI and friends carry the majority of casino volume, so they're tracked alongside native coins on every chain

Every transfer lands in a local SQLite database — currently half a million transactions and growing, deduplicated by hash so restarts and backfills never double-count.

From raw transfers to metrics

Raw rows aren't interesting. What matters is what they tell you:

• Deposit volume — funds flowing into casino wallets, per casino, per day, in USD at current FX rates
• Netflow — deposits minus withdrawals; a casino paying out more than it takes in is a different story than the reverse
• Health score — volume trends, reserve behavior and activity patterns compressed into a single comparable number
• Whale watch — unusually large single transfers, flagged in near real time

Aggregates update incrementally as new rows arrive — we never rescan the full history to answer a question, which is why the site stays fast as the dataset grows.

Sanity checks matter

Blockchains don't make mistakes, but data pipelines do. Two lessons we learned the hard way:

1. Decimal places differ between tokens. A mislabeled token once produced a deposit "worth" $10^71 — more than every atom in the observable universe. Every value now passes through a sanity clamp before it touches any aggregate.
2. Explorers go down. When a major explorer instance died, one chain silently collected zero transactions. Every collector now reports its health, and failures trigger automatic fallback paths instead of quiet gaps.

Why this beats self-reported numbers

Casinos report whatever makes them look good. Blockchains report what actually happened. When we say a casino processed a given volume last month, that figure is reproducible — anyone can query the same public ledgers and arrive at the same answer.

That philosophy extends everywhere: live bet feeds come from public streams, giveaway draws are provably fair on Bitcoin block hashes, and our scoring methodology is published in full.

Questions about a specific wallet or metric? The FAQ covers the common ones — and the data is always one click deeper.