Post-quantum keys, where they can carry weight today.
QuantLayer Quantum implements FIPS 203, 204 and 205 in Rust (libcrux and fips205) and exposes them to TypeScript through Node-API. It protects identities, credentials and authorizations; it does not change how Ethereum accounts sign.
Signatures: ML-DSA and SLH-DSA
ML-DSA is the default: lattice-based, fast, 3,309-byte signatures at category 3. SLH-DSA rests only on hash functions; its slow signing suits long-lived roots of trust.
| Algorithm | Standard | NIST category | Public key | Signature | Sign | Verify |
|---|---|---|---|---|---|---|
| ML-DSA-44 | FIPS 204 | 2 | 1,312 B | 2,420 B | 112 µs | 31 µs |
| ML-DSA-65 | FIPS 204 | 3 | 1,952 B | 3,309 B | 156 µs | 46 µs |
| ML-DSA-87 | FIPS 204 | 5 | 2,592 B | 4,627 B | 192 µs | 70 µs |
| SLH-DSA-SHA2-128s | FIPS 205 | 1 | 32 B | 7,856 B | 877 ms | 742 µs |
| SLH-DSA-SHA2-128f | FIPS 205 | 1 | 32 B | 17,088 B | 39 ms | 2.2 ms |
| SLH-DSA-SHA2-256s | FIPS 205 | 5 | 64 B | 29,792 B | 1,323 ms | 1.6 ms |
Key encapsulation: ML-KEM
ML-KEM establishes a shared secret; it does not sign. QuantLayer uses ML-KEM-768 to seal proof witnesses to the proving worker.
| Algorithm | Standard | NIST category | Public key | Ciphertext | Encapsulate | Decapsulate |
|---|---|---|---|---|---|---|
| ML-KEM-512 | FIPS 203 | 1 | 800 B | 768 B | 6.4 µs | 6.6 µs |
| ML-KEM-768 | FIPS 203 | 3 | 1,184 B | 1,088 B | 11.0 µs | 11.5 µs |
| ML-KEM-1024 | FIPS 203 | 5 | 1,568 B | 1,568 B | 15.3 µs | 16.3 µs |
Hybrid authorization
A classical key and an ML-DSA-65 key sign the same domain-separated input. The request is allowed only if both verify, so neither a classical nor a post-quantum break alone is enough.
Key custody and lifecycle
Custody keys are generated in the Rust module and sealed under a key-encryption key. Only public keys, signatures and KEM shared secrets leave it.
Rotation and cryptographic agility
A verification method keeps its identifier while its algorithm changes. Algorithm identifiers are versioned in the protocol and on-chain.
- Rotation
- Same algorithm, new version; the previous version is retired and keeps verifying history.
- Migration
- A new algorithm of the same kind (for example ML-DSA-65 to ML-DSA-87), with a transition statement signed by both versions.
- Revocation
- Terminal: the version stops verifying and its sealed secret is erased.
Migration architecture
- Today
- Identity keys may already be ML-DSA or SLH-DSA; credentials can be issued by post-quantum issuers; authorizations can require hybrid or post-quantum evidence.
- On-chain
- QuantLayerAuthorizationManager accepts post-quantum evidence through an EIP-712 attestation from a k-of-n attestor set, and reports the result as Attested.
- Path to trustless
- Arbitrum Stylus (ML-DSA in WASM), a future precompile, or a ZK proof of ML-DSA verification can replace the attestors without changing the manager’s interface.