Free downloadable aggregates from WagerDB: daily per-casino deposit/withdrawal flows, tracked vault balances, solvency coverage and the RTP catalogue. Aggregates only, k-anonymity ≥ 50, cite wagerdb.com with a link.
The standing aggregates behind our pages, as flat CSV/JSON files: daily casino flows, vault balances, solvency coverage and the RTP catalogue. Aggregates only — no addresses, no hashes, no cells over fewer than 50 distinct addresses. Use them with one condition: cite wagerdb.com with a link.
Attribution required: if you use these numbers — in a story, a paper, a dashboard or another dataset — cite wagerdb.com with a link. Suggested line: Source: WagerDB (https://wagerdb.com). That is the entire licence.
Observed on-chain deposit and withdrawal volume per casino per day, summed in USD at the day's rate. Cells computed over fewer than 50 distinct external addresses are suppressed (k-anonymity), so gaps mean "below threshold", not "zero volume".
Cadence: Daily (rebuilt with the on-chain collector). 7,566 rows. Download: CSV · JSON. Live view: On-chain daily. Each file ships with a column dictionary on the live page.
The most recent snapshot round of publicly labelled casino hot wallets, summed per casino in USD. The same figures as the latest-balance ranking on the vault history page. Addresses are collapsed away — only the per-casino total, wallet count and chain count remain.
Cadence: Every collector round (~6 hours). 43 rows. Download: CSV · JSON. Live view: Vault history. Each file ships with a column dictionary on the live page.
Latest Solvency Watch round: tracked hot-wallet reserves divided by the casino's average daily payout over the trailing 30 days of observed bet feeds. Conservative on both sides — reserves are a floor, exposure is a sample. Not a solvency verdict.
Cadence: Every collector round (~6 hours). 9 rows. Download: CSV · JSON. Live view: Solvency Watch. Each file ships with a column dictionary on the live page.
Advertised RTP per (game, casino) from the unified slot catalogue — every title for which casinos run different RTP versions. The same data the RTP checker and RTP Watch pages render.
Cadence: With each catalogue refresh (weekly-ish). 1,678 rows. Download: CSV · JSON. Live view: RTP Watch. Each file ships with a column dictionary on the live page.
The same aggregates are available live for dashboards and tickers — public, unkeyed, same attribution rule, under https://wagerdb.com: /api/rtp-watch/events, /api/rtp-watch/stats, /api/solvency, /api/solvency/history, /api/onchain/balances-history, /api/onchain/daily, /api/onchain/market-share and /api/onchain/ggr.
Need a slice that is not here? Request a number — custom aggregates are free for journalists and researchers.
Everything on this page is an aggregate WagerDB already publishes somewhere on the site, packaged as a flat file so you can load it into a spreadsheet, R, Python or a charting tool without scraping pages. The builder is scripts/build_dumps.mjs in the site repository; it runs against the same SQLite store the live API reads.
The rule for inclusion is strict: a number ships in a dump only if it is already visible on a public page or is a safe roll-up of one. Nothing here requires an account, a key, or an email.
No wallet addresses, no player identities, no transaction hashes — ever. The daily-flows dump additionally suppresses every (casino, day, direction) cell computed over fewer than 50 distinct external addresses, the same k-anonymity threshold used for the cohort and migration datasets. A missing cell means "below threshold", which is itself only ever true for small populations.
If you use these numbers in a story, paper, dashboard or dataset, cite wagerdb.com with a link. That is the whole licence. The caveats printed beside each dump — coverage limits, floors, sampling windows — are part of the number; please keep them attached when you quote it.
The manifest (dumps/index.json) carries the generated-at timestamp of the last build. Flow and vault dumps are regenerated with the on-chain collector cadence; the RTP catalogue refreshes with the slot catalogue. The row counts shown on this page come from that manifest, so what you see is what you download.
Yes, with attribution. Publish derived charts, merge them into your own dataset, host a mirror — all fine, as long as wagerdb.com is cited with a link. Do not remove the privacy suppressions or present the aggregates as player-level data; there is none in them to begin with.
Either we observed no flow that day, or the cell covered fewer than 50 distinct addresses and was suppressed. We never export a count of the suppressed population, so the two cases look identical in the file — treat gaps as "no compliant aggregate", not as "zero volume".
Ask. Journalists and researchers can request custom aggregates free of charge via /research/request-a-number — if the underlying records exist, the answer is usually a few days away.
Yes — the dumps are built from the same database the API reads, and the vault/solvency dumps mirror exactly what /api/onchain/balances-history and /api/solvency return for the latest round. Use the API for live dashboards, the dumps for reproducible analysis.