Check a reference AuditProof

Drop in a reference artifact. This page checks declared structure, hash-chain consistency, and any supplied signature locally. It does not observe the underlying capsule or independently establish who controls a supplied key.

Runs in your browser · artifact not uploaded · network disabled after document load

Drop the AuditProof you were given

a .json file — or several at once for a batch check

Compare with a supplied trust manifest and pinned fingerprint (advanced)

By default this page checks integrity against supplied material: the hash chain reproduces and the signature verifies against the key the artifact itself carries. You may also supply a trust-chain manifest and fingerprint obtained through a channel you independently trust. The page checks consistency with that supplied pin; it does not establish that the pin is an official Nanorix root. The production Nanorix root is published at /.well-known/trust-chain.json on this host (and at nanorix.io/trust-chain.json) with its fingerprint at /.well-known/identity.txt. This page never fetches them for you, because it runs with the network disabled, so obtain them through a channel you trust and attach them here.

Check the customer's activity record against the proof (optional)

A capsule created with declare_activity carries one signed field, customer_declared_activity_root — a SHA-512 Merkle root over the raw bytes of the activity file the customer's own code wrote (activity_events.jsonl). The events themselves are not in the proof; the customer keeps the file. Attach that file here and this page recomputes the root from its bytes and compares. Without the file, a declared root is reported as declared, not checked. The file is read locally and never uploaded; its contents are hashed, not interpreted.

Also accepts the legacy cdp.json filename, receipt bundles, and capsule output bundles. Works offline — save this page and open it anywhere, even air-gapped.