Verify
Verify an evidence package
Try a sample, paste an envelope, or drop the .json file — every check runs in your browser: subject integrity, artifact and envelope signatures, receipts, key status. Supply the original bytes to prove integrity end-to-end; tick the online option to confirm settlement receipts against public RPCs. Nothing is uploaded to FileOnChain.
Try a sample
Protocol conformance fixtures, verified by the same code as anything you paste.
The original artifact, to recompute its digest locally.
Nothing is uploaded to FileOnChain. A link carries the envelope itself (?envelope=) or points at a URL your browser fetches directly (?url=). Share controls appear under the report.
Schema, claims & envelope
The envelope is well-formed, its application-profile claims validate, and the envelope digest matches its canonical encoding.
Awaiting a package…
Subject integrity
The subject's SHA-256 digest — recomputed bit-for-bit when you supply the original bytes.
Awaiting a package…
Artifact signatures — who signed
Who made or approved the subject. Claimed identities and delegations are part of these checks: a key is proven, the identity behind it is claimed.
Awaiting a package…
Envelope signatures — who assembled
Who put the evidence together — verified separately from who made the artifact.
Awaiting a package…
Receipts
Storage, settlement, and inclusion receipts — each one checkable on its own public system.
Awaiting a package…
Key status
Whether signing keys declare a status endpoint. A signature alone cannot prove a key was never revoked, so this may honestly be unknown.
Awaiting a package…