Evidence & disputes
Every Dynamo session already generates the artifacts a dispute needs: EIP-712 vouchers signed by scoped session keys, JWS allowance credentials, signed oracle attestations, settlement records with chain/PSP references, refund and break-point records, holdback declarations. The evidence export assembles them into one portable bundle whose signatures verify offline, versioned from birth. This page describes the per-session evidence/1.0.0 bundle. The owner API exports a whole budget as evidence/1.1.0 and later, with the signed authority chain; see Verify an evidence file offline. Status: Live.
Offline verification
What offline verification covers. The verifier checks every signature and digest in the file. From evidence/1.5.0 on it binds and checks each stream's sessionKeyAddress against the vouchers. Pair the file with on-chain settlement (or the engine-signed payment records) to complete a money proof. It is weakest on Control Mode and the credit card rail, where there is no chain to check.
Verification re-checks every signature and every content digest with zero network access. The verifier prints the engine signer named inside the file. A per-session evidence/1.0.0 bundle is checked against that signer (a --signer pin applies to budget files from evidence/1.1.0 on, not to 1.0.0), so a bundle re-signed end to end with another key would pass: compare the printed signer with the one you obtained out of band. A 1.0.0 pass also carries the notice "completeness not proven: no signed head". Inside the bundle, voucher signatures recover to the session keys the budget registered, credentials and attestations verify against the signer material inside the bundle, the manifest's digests match the content, and the Σ proofs (Σ child settlements ≤ funded ceiling; explicit fee rows; finality per unit range) are re-derived from the bundle's own records - not read from its summary. A tampered byte anywhere returns a named FAIL identifying the broken element.
The rendering (Markdown/HTML) states what was signed, delivered, settled, and refunded, with references - suitable for a card-network representment or a counterparty dispute. It never opines: objective facts only.
Getting a file from your instance
The budget's owner exports it over the owner API (1.5.0 and later): GET /owner/v1/budgets/{id}/evidence, the console's "Download evidence" button, or the SDK helpers. Which schema to ask for, and how to run the TypeScript and Python verifiers, is on Verify an evidence file offline. Verification is yours to run, anywhere, offline; for a budget file, pin the engine signer you obtained out of band (--signer), so you are not trusting the file for it.
The building blocks the bundle is made of are all client-visible: every tick returns its voucherSeq, signed consume receipts bind a requestRef to billed units, and allowance credentials verify offline against your budget's pinned engineSigner.
What rides in the bundle
| Section | Contents |
|---|---|
session | The full reconciled session view: budget, streams, per-stream settled totals, refunds, fee rows, holdback states, finality, and the settlement-layer records with backend references (chain transactions, PSP intent/capture/transfer/refund ids) |
artifacts.vouchers | Every EIP-712 voucher with its signature and signing domain |
artifacts.credentials / artifacts.attestations | The compact JWS artifacts (allowance credentials, oracle attestations) collected at issuance |
voucherDomain / engineSigner | The verification anchors, digest-pinned by the manifest |
manifest | SHA-256 content digests for every element plus the bundle digest |
The tamper answer
make demo-evidence exports a credit card sandbox session (Stripe TEST when keys are in .env, the in-repo simulator otherwise), verifies it in a network-disabled process, then flips ONE byte and shows the fail-closed verdict naming the broken element - with the bundle digest and PSP intent ids printed for dashboard cross-check.
Versioning
Every evidence schema follows the same interface discipline as every public artifact: additive changes bump the minor version with a CHANGELOG entry; a breaking change without a deprecation note is forbidden. The verifiers still accept every earlier schema, and the verification material rides inside the file, not in any repository.