Verify a record

Check that a manifest or timeline entry is byte-for-byte what was hashed when it was published. All computation happens in your browser.

Timeline entry

Technical evidence: Approved

Project: Pizza Topping Oracle
Schema: vpn.event/1
Published: Oct 25, 2026, 09:10 AM UTC
Hash: d0198922…a40abc
Anchored: No

{"actor_user_id":"5f25c448-cbbc-464b-a7b2-a54c7cad72e5","body":"Scope: Source verification of SliceAggregator on BOT Chain.\n\nApproved by Provenant Admin","corrects_event_id":null,"event_type":"verification_changed","id":"eedb0bf5-5131-4dcf-89f9-df8152e48d2b","metadata":{"dimension":"technical","status":"approved","verification_id":"e7353ba9-8954-4527-adf0-08cf5dd9fa04"},"project_id":"14aff1d3-b2b3-4a4c-8e2b-e337153e30e8","provenance":"platform_verified","published_at":"2026-10-25T09:10:02.079Z","schema":"vpn.event/1","source":{"created_at":null,"reference":null,"type":"admin","url":null},"title":"Technical evidence: Approved"}

Check any record

Fetch a record from the public API — e.g. /api/v1/projects/<id-or-slug>/manifests/<version> or /api/v1/events/<id> — then paste it with its hash below. Or use your own tooling: the format is RFC 8785 canonical JSON hashed with SHA-256.

Record JSONExpected SHA-256 hash

What a matching hash proves — and what it does not

It proves integrity: the record has not changed since it was hashed and stored.
It does not prove truth: a team-reported claim stays a claim. Check its provenance and evidence.
Anchored records do not depend on this platform: registered projects commit hashes to the Provenant registry (0xb4a2b3949e21406fd7a13752f717785c01cdc507 on Bot Testnet). Read getManifest or getProjectEvent from the contract and compare with 0x + the SHA-256 above. Records that are not anchored are only as trustworthy as this platform.

Specification: canonical serialization & hashing.