Why post-quantum seals, and why now
Records signed today with ECDSA or RSA may need to hold up for decades. Q-VITRN seals them now with a NIST post-quantum signature, on a public ledger anyone can re-read. It is software, not quantum hardware: the word that fits is post-quantum. The signature is ML-DSA-65, a lattice scheme standardized by NIST. The ledger is Hedera Consensus Service. The circuit on the home page is a three-qubit check on an ordinary machine.
The problem
Most public ledgers, Hedera included, authorize transactions with ECDSA or Ed25519. Those schemes are secure against today’s computers. They are not secure against a large-scale quantum attack. Until a chain accepts an ML-DSA account key, there is no native place to put a lattice signature. An ML-DSA-65 signature is 3,309 bytes. A consensus message stops at 1,024. So the signature cannot ride the topic even if you wanted it to.
What people do now
Do nothing
Keep ECDSA and Ed25519. Wait for the chain to add a post-quantum account key.
A large-scale quantum attacker running Shor’s algorithm would forge those signatures. Hedera has pointed at native support around 2027.
Classical timestamp
A public timestamp service, or a plain HCS document stamp. Hash the file, write the hash.
The hash is public. The identity behind it is still a classical key.
PDF and e-sign
An e-signature service or a notary. RSA or ECDSA over the file.
The same classical keys. The signature is not a consensus message anyone can re-read.
Content address
Git, IPFS, a CID. The bytes name themselves.
No signer, no time, no fee. A hash is not an identity.
What this desk does instead
The browser cuts an ML-DSA-65 key and signs a canonical document. The operator verifies the lattice signature on an ordinary machine, then writes only a SHA-384 of the document and a SHA-384 of the signature to topic 0.0.11345042. The raw signature stays with the signer. Anyone can paste the document later and check that its hash is on the topic. Checking is free. Issuing is paid, in testnet QVUSD, which is not a dollar.
Who leaves what they have
Most people will not leave a production notary, an e-signature service, or a timestamp service for a testnet desk. The person who has a reason is the one who needs the lattice property before the chain has a native key: a developer rehearsing the 2027 migration, a researcher who wants a public commitment of a lattice signature, or a counterparty who already holds the text and only needs to see that its hash was written. They do not come for a quantum processor. They come because the classical alternatives cannot show an ML-DSA signature at all.
Launch here means testnet, with the topic and the token already open. It does not mean mainnet, a dollar, or a fee someone has agreed to pay.