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

SliceAggregator deployed on BOT Chain

Project
Pizza Topping Oracle
Schema
vpn.event/1
Published
Jul 23, 2026, 12:00 PM UTC
Hash
9d1458e2…aa0ad4
Anchored
No
{"actor_user_id":"5f25c448-cbbc-464b-a7b2-a54c7cad72e5","body":"Address 0xcbb84be4188654e9968d6dbb33329915f9aaa91c\nRecorded by the team; the platform has not checked this deployment.","corrects_event_id":null,"event_type":"contract_deployed","id":"589e151e-8c63-483a-8186-e19b582b1a8f","metadata":{},"project_id":"14aff1d3-b2b3-4a4c-8e2b-e337153e30e8","provenance":"team_reported","published_at":"2026-07-23T12:00:00.000Z","schema":"vpn.event/1","source":{"created_at":null,"reference":null,"type":"manual","url":null},"title":"SliceAggregator deployed on BOT Chain"}

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.