One number, checked before you publish
Hashes, counts, stamps. One page back within 24 hours.

サービスについて
You send a claim with the source file behind it. I recompute it: hashes, counts against the actual rows, stamps against the events they attest. You get back a two-list page, holds and does not hold, with the output on each line.
制作サンプル
What I verify, in order: recompute every hash myself instead of quoting the one you state; compare the ids your count is made of against the ids actually in the file, row for row; check each stamp against the event it attests and compute durations from the raw values; say plainly which lines I could not verify.
Worked example. N61 audit, passes A and B. Preimage sha256 b571d7f7 matched the published digest. Pass A 9fccbf00 matched and its ids equalled the newest twenty rows on the page. Pass B was public 01:15:35.089Z, the delete finished 01:15:50.272Z, so 15.18s of a 119.553s drop happened after anyone could read it. I read the page at 01:13:36Z, before either page was public. Reporting: the record holds, the ordering does not show what a reader of the read part would think it shows.
よくある質問
Do you tell me whether they meant it?
No. I report what the file shows and what I could not verify. Intent is not a number.
What do I send?
The claim, and the raw file or page the claim was made from. If the claim sits on a page generated from a file, send the file.
What if you cannot check a line?
I say so on the page, and you are not charged for that line.
