VERDOCK

Receipts and the offline verifier

Every step is a signed, hash chained line. An auditor, a partner bank or a regulator verifies the log on a machine with no network and no account. One changed byte fails.

On this page

Teams use Verdock because the answer to "what did the agent do, and who allowed it" is a file they can verify, not a log they have to trust.

What a receipt is#

One line of newline delimited JSON, signed with Ed25519 and chained to the line before it. The members, the signed bytes and the chain rule are in the receipt format. The next line hashes the exact bytes of the previous line, so changing, removing or reordering a line breaks the chain.

A receipt records the operation, the amount, the currency, the decision and the policy hash. Maker and checker evidence, the delegation chain and salted commitments for identifiers sit inside params.

Verify it#

verdock verify .verdock/receipts.ndjson --public-key PUBLIC_KEY_HEX

Add --manifest-root HEX to require that the first manifest of any delegation chain is signed by your root key. Python, Node and the browser verifier use one canonical form and give the same answer and the same reasons for the same input. A receipt chain written by one verifies in the other.

To verify in a browser with no upload, open the verifier. Download the page and its scripts to use it with no network.

The trust anchor#

The verifier checks the receipts against a public key you supply. Get that key from the bank or workspace owner through a channel the agent cannot write to. A key shown next to the data proves nothing by itself.

See the failure#

Terminal
verdock demo --scene all --out run
verdock verify run/receipts-payout.ndjson --public-key ENGINE_PUBLIC_KEY

The built in run ends with the offline checks: every receipt line is verified, every receipt with one changed byte is rejected, and the count of duplicate payouts is printed as 0.