The evidence pack and the verifier page
The evidence pack is a ZIP file with the ledger’s signed records for the chosen days, each day’s statement and its public timestamp proof, which anyone can verify without the app and without Palomar. A verified record proves that the statement existed, unaltered, at the anchored time, signed by the holder of a key; it does not prove the statement true.
What the pack holds
manifest.json — the list of the pack’s files, with each one’s hash, and the pack’s signature. keys/ — the public keys the records were signed with, by key id, in JSON and PEM. bindings.json and periods.json — the statements signed with the company’s wallet: the key’s binding to the wallet and the period statements. days/ — each day’s statement, with its public timestamp proof in the OpenTimestamps format. months/ — each month’s records, with their inclusion proofs in the day statement and with the disclosed content. README.ro.txt and README.en.txt — the verification steps. verifier/ — a copy of the verifier page.
A pack never carries a private key, credentials, a sample’s bytes or a query’s rows. A record’s content enters with everything it carries — a dataset’s owner, the person in a custody statement — and the app shows you the list before the export. A pack proves that the records existed, unaltered, at the anchored time; it does not prove who made them: whoever receives the pack asks you, by another route, for the key ids and the wallet address and compares them with the pack’s.
The verifier page
The verifier page reads the pack in the browser, on your computer, with no request to Palomar or to anyone else, and shows what it checked: the signatures, the chain of records, the inclusion proofs, the day statements and their anchors. It is published here and is the same page every pack carries in its verifier/ folder; the page to trust is this one, and the pack’s copy is for working without a connection.
- Open the verifier page and choose the pack’s ZIP file; the page reads it on your computer.
- Enter, if you have them, the company’s wallet address and the ids of the evidence keys in use now, received from the company by another route than the pack: with them, a stranger’s key or one the company no longer uses is reported as an error.
- For each public timestamp proof, bring the header of the Bitcoin block it ends in — from a node you run, from a source you trust or from a file; the page has no connection to the network. Without a header, the day’s anchor is reported as unchecked.
- Click “Verify the pack” and read the report: the findings, on three levels — errors, warnings, facts — the days in the pack with each one’s anchor state, and the wallets bound. “No errors found” means the pack’s parts agree with one another and with what you entered.