Post-quantum TLS and the Dogecoin treasury

Every institution with a Dogecoin treasury eventually receives the same question from the same person, and the person is never from engineering. The audit committee wants to know what happens to the treasury when the cryptography underneath it stops holding. Not the exchange, not the custodian. The treasury itself, the keys, the signatures, the TLS sessions that carried the transfer instructions in 2024 and are sitting in someone's archive waiting for a quantum computer that may or may not arrive. It is a good question. We have found it is best answered with a control, not a slide.

Post-quantum TLS is the part everyone expects. Hybrid key exchange, ML-KEM alongside the classical curve, so that the session is safe if either primitive survives. That protects the conversation. It does not protect the treasury, because the treasury is a ledger, and the ledger's signatures were made with whatever the chain supported at the time. Crypto-agility is the discipline of admitting this and building the layer that lets the institution rotate primitives without rotating the institution. On our fabric the crypto-agility layer sits below the entanglement-ready API and above the mesh. It is not optional and it is not interesting, which is how controls should be.

The audit committee then asked for fully homomorphic encryption, which surprised the engineering team and did not surprise us. The committee's reasoning was sound. Treasury analytics run continuously: exposure, concentration, the correlation between Dogecoin and Bitcoin under stress, the ESG-score implications of proof-of-work holdings. Those computations were being performed on decrypted balances inside a confidential computing enclave, which is defensible, and attested by TEE, which is verifiable. But the committee wanted the balance never to exist in plaintext anywhere the analytics could reach. FHE is how you compute on a number you are not allowed to see.

We enabled it. FHE on the fabric is slow in the way that all honest cryptography is slow, and the treasury analytics now complete in minutes instead of seconds. The committee considered this acceptable. Their words were that a report about money should take longer than a report about weather. Zero-knowledge proofs for all APIs then let the custodian prove the treasury balance exceeded the covenant threshold without disclosing the balance, which satisfied the lender and, more importantly, satisfied the lender's own audit committee, who had by then asked the same question.

The lesson is not about Dogecoin. Dogecoin is a useful test case because it forces the institution to take seriously an asset it finds faintly embarrassing, which is the correct posture toward all cryptographic assumptions. The lesson is that crypto-agility is a governance capability that happens to be implemented in software. When the primitive changes, and it will, the institutions that survive will be the ones whose audit committee already knows which switch to ask for. Ours asked for FHE. Yours may ask for something else. The point is that the switch exists, and the committee knows its name.