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

Correction: October paw report

Project: Purrliament DAO
Schema: vpn.event/1
Published: Oct 14, 2026, 12:00 PM UTC
Hash: 827c4518…e1ac69
Anchored: No

{"actor_user_id":"5f25c448-cbbc-464b-a7b2-a54c7cad72e5","body":"Gas savings from batching are 91%, not 94%. We had counted one very long nap twice.","corrects_event_id":"6fcbfebf-3bd4-422c-843e-6e64bef6e5e0","event_type":"update","id":"1f390fdf-9fe9-4b70-8dd5-78283a4a1dc7","metadata":{},"project_id":"cba976a8-bd8b-4dcc-8479-49f9446b7cbe","provenance":"team_reported","published_at":"2026-10-14T12:00:00.000Z","schema":"vpn.event/1","source":{"created_at":null,"reference":null,"type":"manual","url":null},"title":"Correction: October paw report"}

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.