VERIFY

Verify a receipt

Don't take our word for a simulated result. Every PerpBrain receipt can be re-derived from its inputs with the open-source verifier in the PerpBrain SDK (MIT). Same inputs, same hashes: verified and reproducible.

Run it yourself

You need Node 22.6 or newer (node -v) and git. No account, API key or exchange key. This checks the example receipt that ships with the SDK:

git clone https://github.com/PERPBRAIN/perpbrain-sdk.git
cd perpbrain-sdk
node --experimental-strip-types examples/verify-receipt.ts fixtures/receipts/good

Expected output:

{"dir":"fixtures/receipts/good","status":"VERIFIED","mismatches":[]}

To check your own receipt, point the same command at a directory holding its receipt.json, manifest.json and inputs.json. Exit code 0 means VERIFIED; exit code 1 means MISMATCH, with each failing field named.

The example receipt

From fixtures/receipts/good/receipt.json in the SDK: a SIMULATED ETH long of 0.01 on a recorded two-sided book, under the standard limits preset.

The input hash is plain SHA-256 of the file, so you can confirm it with no PerpBrain code at all:

sha256sum fixtures/receipts/good/inputs.json
# c6b42a445f209ef5148ecc767ca187fbbe5f290e93ac52305eaf95a00b2a5633

See it catch a change

node --experimental-strip-types examples/verify-receipt.ts fixtures/receipts/tampered-result

{"dir":"fixtures/receipts/tampered-result","status":"MISMATCH","mismatches":["result_sha256 mismatch","result.fills[0].price mismatch"]}

What the verifier does

• Re-derives the SHA-256 of the inputs, the manifest, the limits payload, the market snapshot and the stored result.
• Reruns the book simulator on inputs.json and compares every field of the result.
• Re-applies the frozen limits on that rerun.
• Reads no network and submits no order.

The full list of checks is in Receipts. Agents can run the same check with the MCP tool verify_receipt.