Check a Profit Record yourself.
Every promise on a Profit Record is sealed before the email that announces it is sent, and every measurement is chained after the promise it answers. Drop in a Record export and this page recomputes all of it: each entry against its seal, each link in the chain, each measurement against its promise. It says the Record is intact, or names the first entry that is not and the check that caught it.
Read in this browser. Nothing is uploaded.
No Record of your own?
| Entry | The check | What it found |
|---|
| Entry | Sealed | What | Dollars | Seal |
|---|
A head from a printed page, a seal from an email.
A printed page of a Profit Record carries the Record's head: 64 characters, in groups of eight. An email that announced a sealed move prints its seal beside the expected dollars: the first twelve. Paste either one here, after the export has checked out above, and this page says whether that exact entry is in the chain it just recomputed, and where.
A hash on its own proves nothing. It means something only as a place in a chain you have just recomputed from the whole Record.
Hubricon's published head.
Every client's entries also sit in one chain across all clients. Its head, how many entries it covers and when the last was sealed are public; nothing in them names a client or a promise.
Reading the published head…
Read it without this page
It is public_record_seal() on Hubricon's database, callable by anyone with the public key every page of this site uses:
What the Seal proves, and what it cannot yet.
An intact Record proves that each promise says today what it said when it was sealed, before its email went out; that the entries are in the order they were sealed, with nothing taken out; that every measurement answers the promise it claims to; and that the evidence in the export is the evidence each figure was sealed with.
Two things it cannot prove yet:
- There is no outside timestamp. Nothing beyond Hubricon's own systems dates the head today. Having something outside Hubricon record the head as it moves is the next step, and it is not built.
- Whoever owns the database could rewrite the table consistently, recomputing every seal so that a rewritten Record checks out on its own. What a rewrite cannot reach is what already left: the seals in clients' inboxes, the heads on pages already printed, and the exports already downloaded. A rewritten Record disagrees with those, and this page says so when you paste one. That is evidence of a rewrite, not prevention of one.
Without this page: the export carries the same checker as a file beside the Record, verify-record.mjs. With Node installed, node verify-record.mjs followed by the export's file name runs every check here, and needs nothing else. The checking code on this page is that file's, line for line.