Skip to content
Sign in

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

Community review of ShellInbox replay protection published

Project
Snailmail Bridge
Schema
vpn.event/1
Published
Oct 10, 2026, 12:00 PM UTC
Hash
aed8c8e3…bc9c27
Anchored
No
{"actor_user_id":"5f25c448-cbbc-464b-a7b2-a54c7cad72e5","body":"Two medium findings (double delivery by an enthusiastic snail; leaf reuse). Both fixed in shell-contracts main.","corrects_event_id":null,"event_type":"audit_published","id":"9cfaaaf6-0f52-45ac-8ac5-e714379c8d9e","metadata":{},"project_id":"2d9b63f0-86fc-49da-821b-256064156c7d","provenance":"team_reported","published_at":"2026-10-10T12:00:00.000Z","schema":"vpn.event/1","source":{"created_at":null,"reference":null,"type":"manual","url":"https://snailmail.example/audits/shellinbox-community-review.pdf"},"title":"Community review of ShellInbox replay protection published"}

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.

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.