Frequently Asked Questions
General
Is QuantumSafe quantum-proof?
No. QuantumSafe is quantum-ready, not quantum-proof. No cryptographic system can guarantee absolute security. QuantumSafe uses NIST-standardized post-quantum algorithms (ML-DSA, SLH-DSA) that are believed to be resistant to quantum attacks based on current research. However, cryptanalysis is ongoing, and new attacks may be discovered.
QuantumSafe is built on current NIST-standardized algorithms and does not guarantee absolute security. This is a quantum-readiness tool, not a quantum-proof solution.
When will quantum computers break ECDSA?
The timeline is uncertain. Estimates range from 2030-2040 for a cryptographically relevant quantum computer (CRQC) capable of running Shor’s algorithm at scale. However, the Harvest Now, Decrypt Later threat means data exposed today is already at future risk.
Which blockchain chains are supported?
Currently: Ethereum, Bitcoin, Solana, Polygon, and Avalanche. More chains will be added based on demand.
Do I need to change how I interact with the blockchain?
No. QuantumSafe adds a parallel PQC attestation layer alongside your existing blockchain workflow. You continue signing transactions with ECDSA as usual. QuantumSafe adds a quantum-ready signature on top.
Security
Do you store my private keys?
Never. In BYOK mode (the only mode in v1.0), key generation happens entirely on your device. Only the public key is registered with QuantumSafe. The private key never touches our servers.
What happens if QuantumSafe goes down?
Your private keys are stored locally and remain fully functional. You can still sign with your ECDSA keys as before. QuantumSafe’s service is needed only for:
- Registering new PQC public keys
- Creating hybrid attestations
- Verifying attestations
- Scanning wallets
How are attestations stored?
Attestations are stored in QuantumSafe’s database with cryptographic integrity guarantees. Each attestation is immutable once created. We plan to anchor attestation roots to public blockchains in a future release.
What if the PQC algorithms are broken?
NIST algorithms went through years of public cryptanalysis. If a vulnerability is discovered:
- NIST will issue guidance
- QuantumSafe will add support for replacement algorithms
- You can generate new keys with the updated algorithm
- Existing attestations remain valid records of what was signed
Open Source
Is QuantumSafe open source?
The SDKs are open source under the MIT license:
The API server and infrastructure are proprietary.
Can I audit the cryptographic implementation?
Yes. The SDK source code is fully available. Key generation and local signing use well-audited libraries:
- TypeScript: Web Crypto API (browser/Node.js native)
- Python:
pqcrypto (C bindings to reference NIST implementations)
Pricing & Plans
Is there a free tier?
Yes. The Free tier includes:
- 10 wallet scans per minute
- 5 key generations per minute
- 5 hybrid attestations per minute
- 20 verifications per minute
See Rate Limits for full details.
What are the paid plans?
| Plan | Price | Best For |
|---|
| Free | $0/mo | Evaluation and development |
| Builder | $49/mo | Small production deployments |
| Pro | $199/mo | High-volume production use |
| Enterprise | Custom | Custom limits, SLA, dedicated support |
Technical
Why are PQC keys so much larger than ECDSA keys?
This is a fundamental trade-off of lattice-based cryptography. ML-DSA-65 public keys are ~1.9 KB vs 33 bytes for ECDSA. However, QuantumSafe’s off-chain attestation model means these larger keys do not impact on-chain storage or gas costs.
QuantumSafe works alongside any wallet. You sign with your existing wallet as usual, then create a PQC attestation through the SDK. No wallet plugin required.
What is the difference between ML-DSA and SLH-DSA?
ML-DSA is lattice-based (faster, smaller signatures, compatible with all custody modes). SLH-DSA is hash-based (more conservative assumptions, but cannot be upgraded to Managed custody). See Algorithms for a full comparison.
