TOCIO · V31 · CRYPTOGRAPHIC VERIFICATION

Independent Document Verification.

Verify the exact PDF bytes against the Founder-issued Ed25519 signature. The PDF stays on your device. No account is needed to verify a public institutional document.

01 / LOAD AN ISSUER RECORD

Signed Receipt

Enter a public document reference to retrieve its signed record, or load the .json receipt supplied with a private document.

Document UUID

Or choose an existing receipt file

No receipt loaded.

02 / VERIFY FILE IN YOUR BROWSER

Original PDF

Use the original issued PDF, not a screenshot, printout or PDF edited by another application.

Select PDF (max. 30 MB)

Select a PDF to check its SHA-256 fingerprint.

Optional original platinum seal PNG

Separate seal image not checked.

03 / CONFIRM WHOSE KEY YOU TRUST

Independent Key Check

To authenticate the issuer independently of this website, obtain Tocio's public signing key through a separately trusted channel and paste its Base64 value below.

Trusted Ed25519 public key (Base64, optional)

Without a separately trusted key, a matching signature proves consistency with the receipt only—not independently certified issuer identity.

04 / INDEPENDENT TIME EVIDENCE

OpenTimestamps

A standard .ots proof can be independently checked against the original PDF with the OpenTimestamps client. Proofs may take hours to be anchored.

No timestamp proof inspected.

On your computer: ots verify Tocio-document.pdf.ots, with the original PDF alongside the proof. A submitted/pending proof is not a confirmed Bitcoin timestamp.

OpenTimestamps Project

VERIFICATION RESULTS

Awaiting Document And Signed Receipt

Ed25519 signatureNot Checked

Original PDF SHA-256Not Checked

Externally trusted issuer keyNot Established

Issuer-reported publication stateNot Checked

Independent timestampNot Verified Here

The verifier uses your browser's Web Crypto API; the selected document and private receipts are not uploaded.

What This Verification Means

An Ed25519 signature authenticated against a separately trusted Tocio key, combined with a matching SHA-256 digest, supports the claim that the exact PDF was issued under that key and has not changed. It does not establish the legal identity of Tocio, independently certify its key, validate the factual content, or constitute a qualified eIDAS seal. Publication/revocation data comes from Tocio's own registry. OpenTimestamps requires separate Bitcoin-attestation verification.