Algorithm Compatibility

QuantumSafe supports multiple NIST-standardized PQC algorithms. Not all algorithms are compatible with all custody modes.
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.
ML-DSA-65 is the recommended default algorithm for all new integrations. It provides:
  • 192-bit classical security (exceeds ECDSA’s 128-bit on secp256k1)
  • Compatibility with all custody modes (BYOK, Managed, Safe Guard)
  • Fast signing and verification
  • Reasonable key and signature sizes
Unless you have a specific reason to choose otherwise, use ML-DSA-65.

Compatibility Matrix

AlgorithmBYOK (v1.0)Managed (v1.5)Safe Guard (v2.0)Notes
ML-DSA-44YesYesYesFIPS 204, Security Level 2
ML-DSA-65YesYesYesRecommended default. FIPS 204, Security Level 3.
ML-DSA-87YesYesYesFIPS 204, Security Level 5
SLH-DSA-128sYesNoNoFIPS 205, hash-based. Cannot upgrade to Managed.
SLH-DSA and FN-DSA keys CANNOT be upgraded to Managed (KMS) mode. If you plan to use Managed custody in the future, choose an ML-DSA variant now. This is a permanent decision that cannot be changed after key generation.

Algorithm Details

ML-DSA-44

PropertyValue
StandardFIPS 204
Security Level2 (128-bit classical)
Public Key Size~1,312 bytes
Signature Size~2,420 bytes
Signing SpeedFast
Verification SpeedFast
Managed SupportYes (v1.5)
Best for: Applications where key and signature size are critical constraints.
PropertyValue
StandardFIPS 204
Security Level3 (192-bit classical)
Public Key Size~1,952 bytes
Signature Size~3,309 bytes
Signing SpeedFast
Verification SpeedFast
Managed SupportYes (v1.5)
ML-DSA-65 is the recommended default. It provides a strong balance of security (192-bit), performance, and future compatibility with all custody modes (BYOK, Managed, and Safe Guard).
Best for: Most use cases. Default recommendation for all new integrations.

ML-DSA-87

PropertyValue
StandardFIPS 204
Security Level5 (256-bit classical)
Public Key Size~2,592 bytes
Signature Size~4,627 bytes
Signing SpeedFast
Verification SpeedFast
Managed SupportYes (v1.5)
Best for: Maximum security requirements. Government, military, or ultra-high-value assets.

SLH-DSA-128s

PropertyValue
StandardFIPS 205
Security Level1 (128-bit classical)
Public Key Size32 bytes
Signature Size~7,856 bytes
Signing SpeedSlower
Verification SpeedSlower
Managed SupportNo
Best for: Maximum security confidence (hash-only assumptions). Cases where small public keys are required.

Choosing an Algorithm

Use ML-DSA-65 unless you have a specific reason not to.
  • 192-bit security exceeds the 128-bit security of ECDSA on secp256k1
  • Compatible with all current and future custody modes
  • Fast signing and verification
  • Reasonable key and signature sizes

Size Comparison with ECDSA

AlgorithmPublic KeySignaturevs ECDSA Public Keyvs ECDSA Signature
ECDSA (secp256k1)33 B64 B
ML-DSA-441,312 B2,420 B40x larger38x larger
ML-DSA-651,952 B3,309 B59x larger52x larger
ML-DSA-872,592 B4,627 B79x larger72x larger
SLH-DSA-128s32 B7,856 BComparable123x larger
PQC keys and signatures are significantly larger than ECDSA. This is a fundamental trade-off for quantum resistance. QuantumSafe’s off-chain attestation model minimizes the on-chain impact of these larger sizes.