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

The Catnip Collective: Feline-native governance — Season 1

Project: Purrliament DAO
Schema: vpn.event/1
Published: Jul 19, 2026, 12:00 PM UTC
Hash: 0e5787b8…0aee7d
Anchored: No

{"actor_user_id":"5f25c448-cbbc-464b-a7b2-a54c7cad72e5","body":"Awarded 42,000 USDC. Reported by the team. Disbursed to date: 16,800 USDC.","corrects_event_id":null,"event_type":"grant_awarded","id":"15c5c9b7-f473-4d56-82a7-53ba80aa36be","metadata":{},"project_id":"cba976a8-bd8b-4dcc-8479-49f9446b7cbe","provenance":"team_reported","published_at":"2026-07-19T12:00:00.000Z","schema":"vpn.event/1","source":{"created_at":null,"reference":null,"type":"manual","url":"https://catnip-collective.example/grants/season-1"},"title":"The Catnip Collective: Feline-native governance — Season 1"}

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.