Verify a receipt
Check a tattler receipt: whether the rows still hash to what was signed, and whether the signature covers the body. Or a disclosure, which shows one row of an answer and proves it belonged there without handing over the rest. This runs entirely in your browser, on the same compiled Rust the command-line tool runs. Nothing is uploaded, because checking a receipt against our server would mean trusting us.
Loading the verifier…
What a disclosure shows
One row, how many rows there were, and the question that was asked. Not the other rows: those are present only as hashes of hashes, and the answer they came from is never sent. It is for the ordinary case where a counterparty wants to check a single line and the holder will prove that line without publishing the book.
The limit worth knowing: the leaves are not salted, so anyone holding a disclosure can test a guess at a neighbouring row by hashing it. Against rows carrying an address or a uint256 that is no help at all. Against rows drawn from a small set, a single low-cardinality column say, it is trivial. Disclose from the former.
What a green tick here does not mean
It means nobody edited the rows since they were signed. It does not mean the answer is true: a signed wrong answer is a wrong answer, signed. For that, replay the receipt's question against a nest the issuer does not run and compare hashes.
tattler replay --receipt receipt.json --endpoint <not theirs>
Replay is a command-line job on purpose: it has to talk to an endpoint of your choosing, and a browser on this domain is the wrong thing to route that through. You can start from the datasets on the SQL page.