From a simple JSON file on your website to tamper-evident, quantum-safe document verification — no blockchain, no cloud, no uploads.
Tamper-evident digital signatures on any file type. Recipients verify locally with zero uploads—complete privacy, instant answers.
Encrypt files for anyone with a DID. Only the intended recipient can decrypt. No key exchange meetings, no shared passwords.
DIDs are simple JSON files hosted on your own website. No infrastructure to buy, no third-party services, no vendor lock-in.
Every verification answers two questions. Is it genuine?—cryptographic proof, with DNS records corroborating the signer's keys. Who vouches for the signer?—answered by the trust registries you choose. Authentic-but-untrusted is a normal, honest result.
A DID is just a web address that points to a simple text file containing public cryptographic keys. That's it.
Think of it like a digital business card—anyone can look it up, it tells people how to verify documents you've signed, and it's completely under your control.
A DID is a simple string—just like an email address. It is your cryptographic identity. You can put it on your paper business card right below your email. Anyone who has it can look up your public keys and verify documents you've signed.
The email tells people where to reach you. The DID tells people how to verify anything you've signed. One maps to the other—no guesswork, no central directory.
{
"id": "did:web:trustdid.ca",
"verificationMethod": [{
"id": "did:web:trustdid.ca#support",
"type": "Ed25519VerificationKey2020",
"publicKeyMultibase": "z6Mk..."
}]
}https://trustdid.ca/.well-known/did.json
✓ Runs on their computer
✓ Fetches your public DID
✓ Verifies locally—no uploads
✓ Complete privacy
Three actors, three edges, one verifiable truth. The signer, the verifier, and the resolvable DID form a cryptographic triangle that establishes trust without any central authority.
The signer uses their private key to sign the document. A .vrfy sidecar is generated containing the signature, hash, and DID reference.
The document and its .vrfy sidecar travel together to the verifier. The sidecar contains everything needed to verify—no cloud service required.
The verifier resolves the signer's DID to retrieve the public key, then validates the signature against the document hash. Trust is established cryptographically.
Finance team sends invoice.pdf via email
→ Recipient calls: "Did you really send this?"
→ Manual verification, phone tag, delays
Finance team sends invoice.pdf + invoice.pdf.vrfy
→ Recipient runs TrustDID verification on their computer
→ TrustDID fetches: trustdid.ca/.well-known/did.json
→ Verification happens locally—no uploads, complete privacy
✓ Signed by trustdid.ca finance department
No phone calls, no manual verification, no doubts, no privacy concerns
That's it.
No blockchain. No complex infrastructure. No vendor lock-in. No cloud uploads. Complete sovereignty.
Now that you understand the fundamentals, discover what's inside the .vrfy sidecar—the cryptographic companion file that makes every document verifiable.