Who reports, and how often they are wrong.
Reporter identity is stored with every entry, and the overturn rate below is computed on chain as overturned / reported.
The record does not weight these rates into anybody else’s counters. It cannot: discounting a reporter after the fact would mean revisiting every record they ever touched, and no read here is allowed to grow. What it does instead is publish the rate, so a consuming contract can call reporter_quality and apply its own threshold - the same division of labour as everywhere else here. The record counts; you decide what the count is worth.
Nothing has been reported yet. The table fills the first time a contract calls report.
Both numbers come straight from the contract: reported moves on every accepted report and overturned only ever moves when an appeal is resolved against that reporter. Nothing here is an indexer’s opinion - the rate is a fraction the record can justify line by line.
The names are a weaker claim, and worth reading as one. A contract that called register_consumer chose its own label, so it is the contract’s word about itself rather than a fact the record checked. Anything without one shows as a bare address. The address is the part you can verify.
contracts that read the record
Nothing has announced itself yet.
Reads are view calls. They leave no trace and cost the record nothing, so this list is what contracts have declared about themselves by calling register_consumer - never a count of reads that were observed, because no such count exists.
the aggregate
- addresses with a record
- 0
- dealings graded
- 0
- entries contested
- 0
- of those, overturned
- 0
- reporting contracts
- 0
- reports accepted
- open
Pausing stops new reports and never stops a read. A consuming contract’s transaction must not fail because this contract’s owner pressed a button.