Scenarios

An NDA you can verify without a phone call.

A law firm sends an NDA to a partner company. The recipient verifies the contract originated from the actual firm and has not been altered in transit.

Scenario: Whitfield Law (Ottawa) sends a mutual NDA for Project Phoenix to a prospective partner. The partner's legal team needs assurance that the document is authentic and unmodified before countersigning.

The verification

🛡 VERIFIED ✓ Authentic · Trust unknown
Document: mutual-nda-project-phoenix.pdf
Size: 248 KB • application/pdf
Signer: did:web:whitfield-law.ca#legal
Reason: Executive NDA for Project Phoenix partnership
Location: Ottawa, ON
Timestamp: 2026-03-04T14:22:00Z
✓Document IntegritySHA-256 hash verified
✓Manifest IntegrityDual-proof envelope seal valid
✓DID Resolutiondid:web:whitfield-law.ca resolved
✓Signature ValidEd25519 signature verified
✓DNS URI Record_did.whitfield-law.ca URI found
✓DNS TLSA RecordPublic key fingerprint matches
—Trust RegistryNo trust registry configured
✓Post-Quantum ProofML-DSA-44 signature verified
“Trust unknown” is honest, not alarming. The math checks out — the NDA is genuine and untampered. The partner simply hasn't configured a registry that vouches for Whitfield Law. That's a normal outcome, and often all a legal team needs: the domain whitfield-law.ca itself vouches for the key. See how verification works.

Inside the .vrfy file

The .vrfy file is a JSON document containing the document metadata and three cryptographic proofs, including a post-quantum ML-DSA-44 signature. Here is an excerpt:

{
  "version": "3.0",
  "type": "VerifiableDocumentSignature",
  "did": "did:web:whitfield-law.ca",
  "payload": {
    "documentHash": "a7b3c9...f41e2d",
    "hashAlgorithm": "SHA-256",
    "fileName": "mutual-nda-project-phoenix.pdf",
    "reason": "Executive NDA for Project Phoenix partnership",
    "location": "Ottawa, ON"
  },
  "proof": {
    "type": "Ed25519Signature2020",
    "verificationMethod": "did:web:whitfield-law.ca#legal",
    "proofValue": "kWn8x...Rq3mA=="
  },
  "manifestProof": {
    "type": "Ed25519Signature2020",
    "verificationMethod": "did:web:whitfield-law.ca#legal",
    "proofValue": "Yt4pL...Hv7wQ=="
  },
  "pqManifestProof": {
    "type": "MLDSASignature2024",
    "verificationMethod": "did:web:whitfield-law.ca#legal-pq",
    "proofValue": "Mq9xR...wK2bA=="
  }
}

Why three proofs?

Document Proof (proof) — Signs the payload containing the document hash. Proves the signer endorsed this specific document.
Manifest Proof (manifestProof) — Signs the entire .vrfy file including the first proof. This is an envelope seal — if anyone tampers with any field in the file (version, DID, payload, or proof), the manifest proof breaks immediately.
Post-Quantum Manifest Proof (pqManifestProof) — An ML-DSA-44 (FIPS 204) signature over the same manifest. This proof is quantum-resistant — even when large-scale quantum computers arrive, documents sealed today remain verifiable and tamper-proof. PQ-Ready

All three proofs are generated by default on every seal. The post-quantum proof provides future-proof protection at zero extra effort for the signer.

No phone calls. No notaries. No middlemen. The partner's legal team verifies the NDA's authenticity in seconds using only the .vrfy file and the public identity hosted on whitfield-law.ca.

Verify a document right now.

▶︎ Try the Live Demo How It Works, in Depth