How each register works
Five registers run the same method on five kinds of company: read the binding document, check the claim against a register somebody else controls, and publish every place the two disagree. The instrument is different in each one, so the method is published in each one, rather than at a single page that happens to describe the oldest of them.
Each page below states who goes on that register, how every field on it was established, what it does not measure and will not pretend to, how an absent value is written, how to correct an entry and what commercial relationships exist. Where a method page prints a figure, it computes it from the function the register page computes with, so a method page cannot disagree with the register it describes.
The five registers
| Register | Entries | What it measures | Score | Method |
|---|---|---|---|---|
| Casinos | 24 | A five-component weighted score, plus the licence register check behind it. | Yes, published on 24 of 24 entries | Casinos method |
| Exchanges | 24 | Which entity holds which registration, what a reserves exercise is signed by, and what the freeze, withdrawal and insolvency clauses permit. | No | Exchanges method |
| Wallets | 30 | The custody claim against the binding custody position, and every sub-service clause in the app. 95 recorded. | No | Wallets method |
| Provably fair | 14 | Whether a published fairness scheme is specified closely enough for a third party to recompute a result from it. | No | Provably fair method |
| Clause watch | 24 | One clause read across a whole register. 1 of 3 sweeps read so far. | No | Clause watch method |
Why four of the five publish no score
The casino register publishes a number because five components were defined, weighted and written down before any operator was scored, and because a component with no data is excluded from the denominator rather than counted as zero. That formula is generated from the code that runs it, which is the only reason it can be trusted to describe the number on the page.
Nothing equivalent exists for an exchange, a wallet, a fairness claim or a clause sweep. There is no defined component set, no weighting anybody has argued for, and in most cases no measured quantity at all. What those four registers have is recorded fact: 14 of 24 exchanges hold a registration confirmed in an issuing register, 26 of 30 wallets name a company in the document that binds you, 5 of 14 operators publish a fairness scheme a third party can reproduce, and 11 of the 20 contracts read in the VPN sweep prohibit the tool. Compressing any of those into a number out of a hundred would add nothing a reader could check and remove the thing they can.
What is the same on all five
A value is recorded only where a primary document supports it, and every recorded value carries the URL it came from and the date it was read. A company’s own footer is not evidence of its own licence. A register row is evidence of what that register said on the day it was queried and of nothing after it. Where a document could not be retrieved, the entry says so and is counted in no figure, because a contract nobody could read is not a contract that says nothing.
How an absent value is written
Four tokens, used the same way on every register. A table that renders a missing measurement and a published refusal in the same cell is making a false statement about one of them.
| Token | What it means | On this register |
|---|---|---|
| Not measured | The measurement is in scope and we have not made it yet. The gap is ours. | Used where a measurement is in scope and has not been made. |
| Not applicable | The concept does not fit this kind of entity at all. Reserved for a type mismatch, never for a count of zero. | Used only where the field does not fit the entity type. |
| Not disclosed | The company publishes nothing on the point. The gap is theirs and it is a finding about them. | Used where a company publishes nothing on the point. |
| No data | We looked and either nothing exists or nothing would load. The gap is in the record. | Used where retrieval was attempted and produced nothing. |
Corrections
If an entry about any of the five registers is wrong, send the primary source that corrects it to the address on the contact page. A correction needs the document, not a request: a link to the clause, the register row or the page that shows the recorded value is not what it was on the date we read it.
Corrections are published with their date at corrections, and the original value stays visible rather than being edited away. A change to what an entry records about a company is logged at the change log on the day it is made. A register whose history can be rewritten quietly is not a register.
Commercial disclosure
CryptoGuardz holds commercial affiliate relationships with 3 of the 24 operators on the casino register, named in full at the disclosure page and named again on every page that carries one of them. Being paid through them is the intended model rather than a description of the current build: no outbound link here carries affiliate tracking yet. No exchange, wallet or wallet provider on this site is a commercial partner, and no page in those four registers carries an affiliate link. No commercial relationship is an input to anything computed on this site, and the build rejects a data file that tries to set a derived value by hand.
The data behind all of it
Every register is published as a CSV with its columns, its row count and its known gaps at the data page. If you disagree with a conclusion, the file the conclusion was computed from is the first link on that page.