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

snailmail-bridge/garden-relay v0.3.0 — rain-delay oracle

Project: Snailmail Bridge
Schema: vpn.event/1
Published: Oct 7, 2026, 12:00 PM UTC
Hash: 8b7f0f0d…01dc2f
Anchored: No

{"actor_user_id":"5f25c448-cbbc-464b-a7b2-a54c7cad72e5","body":null,"corrects_event_id":null,"event_type":"release","id":"35ec7ba4-6fd0-44f6-8430-55610ca929f1","metadata":{"tag":"v0.3.0"},"project_id":"2d9b63f0-86fc-49da-821b-256064156c7d","provenance":"team_reported","published_at":"2026-10-07T12:00:00.000Z","schema":"vpn.event/1","source":{"created_at":null,"reference":null,"type":"manual","url":null},"title":"snailmail-bridge/garden-relay v0.3.0 — rain-delay oracle"}

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.