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

purrliament-dao/collar-firmware v1.0.0-beta.2

Project: Purrliament DAO
Schema: vpn.event/1
Published: Oct 16, 2026, 12:00 PM UTC
Hash: 31e9c25c…3ffb1d
Anchored: No

{"actor_user_id":"5f25c448-cbbc-464b-a7b2-a54c7cad72e5","body":"Collar battery now lasts a full nap cycle plus one zoomies episode.","corrects_event_id":null,"event_type":"release","id":"fbacb1ef-b16f-49ab-8aa0-949098cb5a7a","metadata":{"tag":"v1.0.0-beta.2"},"project_id":"cba976a8-bd8b-4dcc-8479-49f9446b7cbe","provenance":"team_reported","published_at":"2026-10-16T12:00:00.000Z","schema":"vpn.event/1","source":{"created_at":null,"reference":null,"type":"manual","url":null},"title":"purrliament-dao/collar-firmware v1.0.0-beta.2"}

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 (0x47bee0ef49213b1427f2c3be0920c0a14eff8387 on Bot Testnet). For a manifest, call anchorOf(projectId, 0x + the SHA-256 above): a non-zero result means it is anchored. For a timeline entry, read getProjectEvent and compare its hash with 0x + the SHA-256 above. Records that are not anchored are only as trustworthy as this platform.

Specification: canonical serialization & hashing.