Paste any Trust Registry record below. Your browser recomputes the content hash,
re-derives the issuer's key from its did:key, and checks the ed25519 signature
itself. The record never leaves your device — there is no server call in the
cryptographic checks, so you are not trusting us to tell you the truth about our own log.
What this checks, entirely on your device. (1) the record's
id is the SHA-256 of its own canonical bytes; (2) the issuer DID really
encodes the public key in proof.public_key; (3) the ed25519 signature verifies over
those same bytes. All three run locally via WebCrypto — the record's cryptographic validity never
depends on trusting this page or our server.
What this additionally checks, by asking our server. (4) whether the record's
id is actually present in the published log, and (5) whether it falls under the
latest wallet-signed checkpoint (anchored) or was written after it (pending, up
to ~15 minutes). This one check is server-dependent by nature — log inclusion isn't something your
browser can determine alone — so treat it as a convenience, not a substitute for the crypto checks
above. For a fully independent confirmation, use the
offline Python verifier against your own copy of
the signed log root and log
range.