Register change log
Every status change, dated, in the order it happened. Entries are appended and never removed or edited, so an operator that was flagged and later cleared shows both, and so does the reverse.
What changed on the registers
8 entries, newest first. These record what the register itself did: a section added, a field redefined, a published figure corrected. An error of our own about a company is a correction rather than a change, and goes to corrections, because the two say different things about who got something wrong.
| Date | Register | What changed | Why |
|---|---|---|---|
| 2026-09-22 | Data | Every register is now downloadable. One CSV per register, generated at build time from the files the pages render, listed at the data page with its columns, its row count, its last-updated date and a plain statement of what it does not cover. | Three section landing pages told readers the files behind them were downloadable from the data page. The data page published one file, the casino table. The claim was false on thirteen pages for as long as that was true. |
| 2026-09-22 | Method | A method page published for each of the five registers, at the method hub, each stating the inclusion rule, what is measured and how, what is never measured, the four-token absence vocabulary, the correction route and the commercial position. | Four registers pointed the last tab of their navigation at a page describing the casino payout score, which governs none of them. Their rules existed only as comments in the code that applied them. |
| 2026-09-22 | Build | A validator added for each new dataset and wired into the build. Every record must have a slug matching its file and an entity on the register, every quoted value a source URL and a retrieval date, every enum value a place in its permitted set, and no boolean may contradict the prose recorded beside it. | Three datasets shipped with no validator at all. The boolean check is not hypothetical: it is the check that would have caught the adverse-register defect below before it was published rather than after. |
| 2026-09-22 | Exchanges | Rows recording a search of a regulator’s register of non-compliant entities are typed as searches rather than as listings, and record that the entity was not present. Two exchanges previously carried a boolean saying the opposite of the sentence printed beside it. | The rows for those two exchanges opened with the words Negative check, meaning the register was downloaded, searched, and the exchange was not in it. A template counting the boolean would have published that two named exchanges sit on a regulator’s non-compliance register. |
| 2026-09-22 | Clause watch | The two contracts in the VPN sweep that could not be retrieved now record nothing at all: no stated consequence, no retrieval date, and no value in any derived column. They are counted in no published figure. | Both rows previously carried the token meaning the terms state no consequence, which rendered in the same cell, in the same words, as the operators whose terms were read in full and contain nothing. Two different findings had one rendering, on the page whose premise is that they are different. |
| 2026-09-22 | Wallets | The count of wallets marketed as non-custodial is computed from the custody language in the recorded marketing quote rather than from the presence of a quote. The published figure moved from 3 of 3 to 2 of 3. | One wallet’s recorded marketing quote is a claim about security and not about custody, which the note beside it said at length while the headline above it counted the wallet anyway. |
| 2026-09-22 | Casinos | The methodology page is generated from the constants in the scoring function. Every weight, band and threshold printed on it is read out of the code at build time. | An audit found the page describing a formula the code did not run. A register whose whole proposition is that a sceptic can recompute the working cannot afford the one page where they would get a different number. |
| 2026-09-22 | Site | Four registers added: exchanges, wallets, provably fair implementations and clause watch, with the first clause sweep covering VPN and location terms. | The method was always about reading binding documents against public registers. It was only ever applied to casinos, which described the subject rather than the method. |
No operator status changes yet
No operator has moved between statuses since the register launched with the entries below. This page fills as operators change: a licence lapses or renews, a marketing claim is corrected, a withdrawal test comes back, a complaint pattern emerges.
| Operator | First published | Opening status | On what basis |
|---|---|---|---|
| BC.GAME | 2026-09-02 | watchlist | Licence in the issuing register reads "Valid"; 1 high-severity contradiction documented; 3 medium-severity contradictions documented. |
| BetFury | 2026-09-02 | watchlist | Issuing register records the term as ended 2026-07-31; 5 high-severity contradictions documented; 3 medium-severity contradictions documented. |
| Bets.io | 2026-10-02 | watchlist | Licence in the issuing register reads "Valid"; 2 medium-severity contradictions documented. |
| Bitcasino | 2026-10-02 | watchlist | Licence in the issuing register reads "Indefinite"; 3 medium-severity contradictions documented. |
| Cloudbet | 2026-09-02 | watchlist | Issuing register records the term as ended 2026-05-23; 1 high-severity contradiction documented; 1 medium-severity contradiction documented. |
| Coins.game | 2026-10-02 | watchlist | Licence in the issuing register reads "Valid". |
| Duelbits | 2026-10-02 | watchlist | Issuing register records the term as ended 2025-12-24; 1 high-severity contradiction documented; 1 medium-severity contradiction documented. |
| Flush | 2026-09-02 | watchlist | Licence asserted by the operator and not confirmed against a register; 1 high-severity contradiction documented; 1 medium-severity contradiction documented. |
| FortuneJack | 2026-10-02 | watchlist | Licence in the issuing register reads "Valid"; 1 high-severity contradiction documented; 3 medium-severity contradictions documented. |
| Gamdom | 2026-09-02 | watchlist | Licence asserted by the operator and not confirmed against a register; 3 high-severity contradictions documented; 2 medium-severity contradictions documented. |
| Jackbit | 2026-09-02 | watchlist | Issuing register records the term as ended 2026-07-23; 4 high-severity contradictions documented; 2 medium-severity contradictions documented. |
| Lucky Block | 2026-10-02 | watchlist | Licence asserted by the operator and not confirmed against a register; 1 high-severity contradiction documented; 3 medium-severity contradictions documented. |
| mBit | 2026-10-02 | watchlist | Licence in the issuing register reads "Indefinite"; 2 medium-severity contradictions documented. |
| Metaspins | 2026-10-02 | watchlist | Licence in the issuing register reads "Valid"; 1 high-severity contradiction documented; 1 medium-severity contradiction documented. |
| Rakebit | 2026-09-02 | watchlist | Licence in the issuing register reads "Valid"; 3 high-severity contradictions documented. |
| Rollbit | 2026-10-02 | watchlist | Issuing register records the term as ended 2026-05-23; 1 high-severity contradiction documented; 1 medium-severity contradiction documented. |
| Roobet | 2026-09-02 | watchlist | Licence in the issuing register reads "Indefinite"; 1 high-severity contradiction documented; 3 medium-severity contradictions documented. |
| Shuffle | 2026-09-02 | watchlist | Licence in the issuing register reads "Indefinite"; 3 high-severity contradictions documented; 2 medium-severity contradictions documented. |
| Sportsbet.io | 2026-09-02 | watchlist | Licence in the issuing register reads "Active, with no expiry recorded"; 1 high-severity contradiction documented; 4 medium-severity contradictions documented. |
| Stake | 2026-09-02 | watchlist | Issuing register records the term as ended 2026-06-09; 2 high-severity contradictions documented; 3 medium-severity contradictions documented. |
| Thunderpick | 2026-09-02 | watchlist | Issuing register records the term as ended 2026-06-04; 1 high-severity contradiction documented; 1 medium-severity contradiction documented. |
| Vave | 2026-10-02 | watchlist | Licence asserted by the operator and not confirmed against a register; 3 high-severity contradictions documented; 3 medium-severity contradictions documented. |
| Wild.io | 2026-09-02 | watchlist | Licence asserted by the operator and not confirmed against a register; 3 medium-severity contradictions documented. |
| Winz.io | 2026-09-02 | watchlist | Licence asserted by the operator and not confirmed against a register; 4 high-severity contradictions documented; 4 medium-severity contradictions documented. |
How this page works
Entries are appended and never removed or edited. An operator that was flagged and later cleared shows both, in order, and so does the reverse. A register whose history can be quietly rewritten is not a register, and the change log is where that commitment is either kept or visibly broken.
A status change requires a documented reason, cited on the operator’s page. We do not move an operator because sentiment shifted or because a commercial relationship changed. The triggers are specific: a licence lapses or renews in the issuing register, a marketing claim is corrected or newly contradicted, a withdrawal test returns, or a complaint pattern crosses a threshold.
What is not a change log entry
Re-reviewing an operator and confirming nothing moved is not an entry. It updates the last-reviewed date on that operator’s page instead. Correcting our own error is not an entry either; that goes to corrections, which is a separate record on purpose, because the two say different things about who got something wrong.