Post-quantum document anchoring for AI agents on Algorand

Post-quantum document anchoring for AI agents on Algorand There's a quiet assumption baked into every e-signature platform: that RSA and ECDSA will still be hard to break when someone needs to prove the document is authentic. For a contract signed today and enforced in 2040, that assumption is worth examining. NIST finalised ML-DSA (FIPS-204) in August 2024 — the first post-quantum signature standard ready for production use. Algorand has been producing Falcon-512 state proofs over every block since 2022. The standards exist. The chain infrastructure exists. What was missing was a simple, open tool that wires them together and exposes them to the AI agents now autonomously executing agreements. That's what PQ Verifiable Archive is. It's open source, it runs on Algorand mainnet, and you can call it today. The problem with documents signed today A signed PDF sitting in a DocuSign vault has an integrity guarantee based on an RSA or ECDSA certificate chain. A large enough quantum computer breaks both. CNSA 2.0 mandates post-quantum cryptography for national-security systems by roughly 2030–2035, and regulated industries will be close behind. "Harvest now, decrypt later" is already happening — adversaries are archiving signed artifacts to attack once the hardware lands. The document you sign today may need to be verified in 2040. The signature on it will not survive. What PQ Verifiable Archive does It adds a quantum-resistant notarisation layer to any signed document, without requiring you to change your signing tool. The flow is straightforward: Take a SHA-256 hash of your signed PDF Anchor that hash to Algorand mainnet in a transaction note Sign a self-contained proof bundle with ML-DSA-65 (NIST FIPS-204) Hand anyone the bundle — they can verify it offline, decades from now, without trusting any vendor The bundle looks like this: { "protocol" : "pqva/1" , "envelopeId" : "contract-2026-001" , "documentHash" : "d88c1a367ad6e6bc..." , "merkleRoot" : "d88c1a367ad6e6bc..." , "algorandTxnId" : "QZDHEO4JKMRUXHNABS5AVRM53PYKBPKUUFULDBV2LANN3Z37PWAA" , "algorandRound" : 62158259 , "blockTimestamp" : "2026-06-14T22:18:41.000Z" , "stateProofRound" : 62158464 , "algorithm" : "ml-dsa-65" , "mldsaPublicKey" : "b1509e56..." , "signature" : "75483d62..." } Nothing in the bundle reveals document contents. Only irreversible hashes touch the chain. Five checks, three offline The verifier runs five checks. Three of them need no network connection at all — they work from the bundle alone: Check What it proves Network? ML-DSA-65 signature Bundle hasn't been tampered with since signing No SHA-256(PDF) match Correct document was anchored No (needs PDF) Merkle inclusion This hash is under the claimed root No Algorand anchor Root appears in on-chain transaction note AlgoNode only Falcon-512 state proof Block is covered by Algorand's native PQC proof AlgoNode only Steps 4 and 5 query AlgoNode — a public indexer — not a private vendor API. Anyone can run a verification against the public Algorand ledger forever. An MCP tool for AI agents AI agents are already signing NDA terms, executing purchase orders, and creating binding agreements autonomously. When an agent acts on your behalf, you need a machine-readable, tamper-evident receipt — not a PDF in a folder that disappears when a vendor shuts down. PQ Verifiable Archive ships as a Model Context Protocol server. Add it to Claude's settings: { "mcpServers" : { "pq-verifiable-archive" : { "command" : "npx" , "args" : [ "tsx" , "/path/to/pq-verifiable-archive/src/mcp-server.ts" ], "env" : { "ALGORAND_MNEMONIC" : "your 25-word mnemonic" , "DOCUSIGN_MLDSA_PUBLIC_KEY" : "..." , "DOCUSIGN_MLDSA_PRIVATE_KEY" : "..." , "DOCUSIGN_KEY_REGISTRATION_TXN_ID" : "..." } } } } Claude can then call two tools directly: anchor_document(hash, envelope_id?, signers?) — anchors to Algorand mainnet, returns a proof bundle verify_bundle(bundle, pdf_base64?) — runs all five checks, returns structured pass/fail An agent executing a c