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

Bounty: Accelerometer model: sitting vs. lying down

Project
Purrliament DAO
Schema
vpn.event/1
Published
Oct 15, 2026, 12:00 PM UTC
Hash
2ac0fbda…0ad088
Anchored
No
{"actor_user_id":"5f25c448-cbbc-464b-a7b2-a54c7cad72e5","body":"Reward 3,000 USDC (funded).","corrects_event_id":null,"event_type":"opportunity_created","id":"87b96c16-0547-483d-84ca-0a0a9048b020","metadata":{},"project_id":"cba976a8-bd8b-4dcc-8479-49f9446b7cbe","provenance":"team_reported","published_at":"2026-10-15T12:00:00.000Z","schema":"vpn.event/1","source":{"created_at":null,"reference":null,"type":"manual","url":null},"title":"Bounty: Accelerometer model: sitting vs. lying down"}

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 (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.