LabsVerifier

Verify a receipt

Paste a humanproof/1 receipt, or a batch (JSON array), and the public key. Verification runs entirely in your browser, with the same code as the command-line verifier: nothing is sent anywhere. The receipt carries no biometrics, no image and no identifier in the clear: what refers to the person is pseudonymized, which lowers exposure and does not make the receipt anonymous.

The receipt is the signed record of what happened in an act; a batch is a file with several receipts at once. Pseudonymized means the person’s data becomes a code that does not identify them on its own.

Drop the whole package here, as it came from the panel (act dossier or campaign auditor package), or choose the files:

The page recognizes each file by its content, builds the batch and checks, beyond the receipts, what the package states: that the receipt is the one the dossier declares, that every act in the campaign has a valid receipt and, if there is a checkpoint, that the batch matches it. The key used is the one Hummand publishes; the one in the package is only compared with it.

Or open a file:

The published key anyone uses to check the signature; the kid, inside the receipt, says which key to use.

The key is also at gateway.hummand.com.br/.well-known/humanproof/keys.json; keep a copy alongside the receipts. Fetching it is the only request this page makes, and only when you ask, open a package or open the page from a dossier code.

What is verified

The signature against the key of the declared kid; the format, which rejects any unknown field; internal coherence, such as a result consistent with the steps and a level consistent with the guarantees; and, in a batch, the client chain rebuilt from the hashes, in any order. The format is described in the note The humanproof/1 format. To verify outside the browser, the command-line verifier does the same, offline, and is distributed to clients with a checksum.

It confirms the receipt was not altered after signing, that it is well formed and coherent, and, in a batch, that no receipt was removed, inserted or moved in the middle of the series.

To write your own verifier, the format specification has the full rules and the test vectors, with the expected result of each.

1.0

Verify a receipt

Paste the JSON and the public key. No account, nothing sent: it runs in your browser.

Open the verifier
2.0

Talk to us

A technical conversation, straight with the people who build it, no sales script.

Contact