Verify
Evidence that verifies itself.
A Proof Pack is the record AntBotics hands over after a job: what was done, what was covered, and the before and after evidence. This page checks one live, in your browser.
Below is a demonstration Proof Pack, rendered from its raw manifest. Press Verify and your browser recomputes the SHA-256 hash of every media file and of the manifest itself, then compares them against the values recorded in the pack. If a single byte had changed, the check would fail. Do not take our word for it: run it.
Demonstration only
This pack is synthetic and labeled as such throughout. It was generated to illustrate the open Proof Pack format; no real job took place. The verification below is real.
Loading the demonstration pack...
Verify your own pack
Anyone can issue and check a Proof Pack; the format is an open specification. Select a pack's manifest.json together with its media files, and this page runs the same checks on it.
Select manifest.json and the media files it references.
Files are read locally and never leave your device.
What is a Proof Pack?
Facility maintenance usually ends with an invoice you have to trust. A Proof Pack replaces that with evidence: a portable record of the job, the site, the coverage achieved, and the before and after media, sealed with cryptographic hashes. A client, an auditor, or an insurer can verify it independently, on any machine, without trusting AntBotics or even this website. Our machines are operator-flown and supervised by trained people; the proof layer is what makes that work verifiable.
The format is published as an open specification (Apache 2.0) with a reference validator, so the proof outlives any single vendor. Read the Proof Pack spec on GitHub
Step 1
Read the manifest
manifest.json is the authoritative record: issuer, job, site, coverage, and every piece of evidence with its SHA-256 hash.
Step 2
Check the structure
The manifest must carry the required fields of the specification: issuer, job, site, evidence, and integrity.
Step 3
Recompute the manifest hash
The manifest is canonicalized with RFC 8785 (JCS) and hashed with SHA-256, excluding the recorded hash itself. The result must equal integrity.manifestHash.
Step 4
Hash every media file
Each referenced file is hashed byte for byte and compared with the sha256 recorded in the manifest. One changed pixel breaks the match.