What is the difference between quantum-resistant marketing and shippable technology?

Marketing describes a future mainnet, a forthcoming token, or a research roadmap. Shippable technology has a deployment path on infrastructure that exists today, named integrations or design partners, and a concrete answer to what happens to assets and keys that exist right now.

Should quantum protection live at the chain level or the wallet level?

Chain-level migration is the end state but takes years of ecosystem coordination. Wallet- and exchange-level protection (the approach QKey takes) can be deployed now, protects assets where they already live, and does not require users to move funds or pay per-transaction fees. For most organizations, wallet-layer first is the pragmatic sequencing.

How to evaluate a quantum-readiness vendor

Q: What should a CTO ask before signing with a quantum-readiness vendor?

Five questions separate shippable technology from marketing: (1) Does it work on existing chains and infrastructure, or require migration? (2) What does it cost per transaction at scale? (3) Is it deployed or deployable now — who is using it? (4) Which post-quantum algorithms does it use, and are they NIST-standardized (ML-DSA, ML-KEM, SLH-DSA)? (5) What is the migration path for existing keys and funds — does anything have to move?

A procurement guide for CTOs, CISOs, and procurement officers. The quantum-threat narrative is real — which is exactly why it attracts vendors selling vapor. These are the questions that separate shippable technology from marketing.

The five questions that matter

1. Does it work on what you already run?

The single most revealing question. If the answer involves a new blockchain, a bridge, a wrapper token, or your users moving funds, you are looking at a multi-year migration project with adoption risk — not a security upgrade. Wallet- and exchange-layer solutions protect assets in place. Ask it first; half the field eliminates itself here.

2. What does it cost per transaction at your volume?

Some approaches embed protection in a service layer that charges per transaction. At exchange or custodian volume, that is an unusable tax. Get the fee model in writing and model it against your real throughput before anything else is discussed.

3. Is it deployed — or described?

Ask who is using it today, or who can deploy it this quarter. "Mainnet launching next year," "token sale upcoming," and "research partnership announced" are all synonyms for does not exist. A credible vendor names integrations, design partners, or a shipping product.

4. Which algorithms — and are they NIST-standardized?

NIST finalized its first post-quantum standards in 2024: ML-KEM (FIPS 203), ML-DSA (FIPS 204), and SLH-DSA (FIPS 205). A vendor that cannot name its primitives, or uses proprietary "quantum-proof" cryptography with no external review, is asking you to trust unaudited math with your treasury. Standardized, reviewed algorithms only.

5. What happens to the keys and funds that exist right now?

This is where wallet-layer architecture earns its keep. QKey's hardened HD wallet design (BIP39/BIP32/BIP44) is built to migrate to post-quantum signatures without re-seeding or moving funds — the migration is a key ceremony, not an evacuation. Any vendor whose answer involves moving assets should explain why, in detail.

Red flags checklist

"Quantum-proof" with no named algorithms — proprietary, unreviewed cryptography
Protection that requires a new chain, bridge, or wrapped asset — migration risk rebranded as security
Per-transaction fees at undisclosed rates — a permanent tax discovered after signing
No answer for existing keys — protects only future deposits, leaving current holdings exposed
Urgency without specificity — "quantum computers are coming" is true; it is not a product

Green flags

NIST-standardized primitives (ML-DSA, ML-KEM, SLH-DSA) with public documentation
Deploys on existing infrastructure — wallets, exchanges, custodians as they run today
No per-transaction fees — security as a property, not a toll
A concrete answer for existing funds — migration without evacuation
Named advisors and integrations you can independently verify

Common questions

What should a CTO ask before signing with a quantum-readiness vendor?

Five things: does it work on existing infrastructure; what does it cost per transaction at scale; is it deployed now; which algorithms does it use and are they NIST-standardized; and what happens to existing keys and funds.

Marketing vs. shippable — what's the tell?

Marketing describes a future mainnet, token, or roadmap. Shippable technology has a deployment path on today's infrastructure, named integrations, and a concrete answer for assets that exist right now.

Chain level or wallet level?

Chain-level migration is the end state but takes years. Wallet- and exchange-level protection deploys now, protects assets in place, and — in QKey's case — carries no per-transaction fees. Wallet-layer first is the pragmatic sequencing for most organizations.

Want a second set of eyes on a vendor proposal? jeremy@nftdemon.com · Quantum advisory services →

About the author

Jeremy Ryan is the founder of NFT Demon Holdings LLC and an advisor to QSAVE and QKey on quantum-resistant crypto security. He spent a decade in telecom and cybersecurity consulting before becoming the largest NFT artist on BNB Chain. Full bio →