Verify a sealed record.
A seal hash or sequence number is enough to confirm a record against the public ledger — independently, by anyone.
Accepts
- Seal SHA-256 hash (full 64-character hex)
- Hedera sequence number
- Topic ID / sequence (e.g. 0.0.8369360/42)
Upload the evidence file.
Don’t trust a hash someone typed — not even your own. Upload the
canonical evidence file (APO-######.canonical.json) that ships inside the
court package. We recompute its SHA-256 and SHA-3-256 from your file and
check the recomputed hash against the public Hedera ledger. A single changed byte produces a
different hash — and a different hash will not be found.
We never see your keys or content beyond the single file you choose to
upload, and we never store it. Hedera is confirmed here, live. Bitcoin (OpenTimestamps) and
RFC-3161 are confirmed offline using the proof files bundled in your court package
(ots verify, openssl ts -verify) — against the same hash this
page recomputes.
How it works
Sealed at creation
Every AI interaction is sealed at the instant it is created — before anyone could alter it.
Anchored in public
The seal hash is anchored on the Hedera ledger, where the timestamp becomes public and permanent.
Anyone can check
Opposing counsel, the court, or the bar can verify the seal against the ledger. No account needed.