The first PQC audit for the MPC custody stack — Fireblocks, Coinbase Custody, Privy, Lit, Web3Auth, Safeheron, DFNS, Turnkey, Capsule, Cobo.
Specialised audit for MPC / threshold wallets — every major MPC custody stack ships with classical primitives at every layer (ECDSA / EdDSA output signatures, X25519 / ECDH DKG channels, classical KEMs wrapping shares at rest, classical recovery vaults). We score the full MPC pipeline against a maintained vendor matrix, identify the harvest-now-decrypt-later (HNDL) exposure points, and deliver a signed MPC Posture Certificate that procurement, custody-counterparty diligence, and regulators can cite. Covers GG18 / CGGMP21 ECDSA TSS, FROST / DKLs Schnorr / EdDSA TSS, proactive secret sharing refresh ceremonies, and recovery vault constructions.
Cryptographic Migration Certificate · signed PDF, embeddable SVG, hash on the QorTrace public registry.
Fireblocks. Coinbase Custody. Privy. Lit. Web3Auth. Safeheron. DFNS. Turnkey. Capsule. Cobo. Zengo. Every major MPC wallet shipping in 2026 outputs an ECDSA / EdDSA signature, runs DKG over X25519 / ECDH channels, wraps shares at rest with classical KEMs, and protects recovery with classical Shamir. None of it survives Q-Day. The DKG transcripts are HNDL-exposed today. We're the only firm in the world auditing this stack against a PQC migration plan you can hand to procurement.
Every engagement ships against this fixed manifest. No scope-creep invoices, no surprise “phase 2” line-items. If we change the scope, we re-sign first.
We score your MPC SDK + custody vendor against our maintained matrix: Fireblocks, Coinbase Custody, Privy, Lit, Web3Auth, Safeheron, DFNS, Turnkey, Capsule, Cobo, Zengo, Sepior, Curv, Knox, Ledger Vault. Each vendor scored against the same PQC criteria so you can compare apples to apples.
Every DKG round shuttles share material over X25519 or ECDH. We map exactly which transcripts are HNDL-exposed forever, and write the hybrid-KEM upgrade plan (X25519 ⊗ ML-KEM-768) for the share-refresh ceremony.
Your shares are encrypted at rest with classical wrap. We score the construction (RSA-OAEP / ECIES / argon2 / scrypt / hkdf) and write the migration to ML-KEM-768 hybrid wrap, with the share-metadata versioning model so re-wraps can run atomically.
If you persist presigs or nonce pools across signing sessions, every persistence window is HNDL-exposed. We score your TTL + AEAD choice and write the volatile-memory migration plan.
If you don't have a `refreshShares` ceremony, you can't migrate cryptography without rotating the public key. We review your existing (or planned) PSS protocol against Herzberg '95 and CGGMP21 §6.
Shamir backups, social recovery, WebAuthn / passkey recovery — every recovery path scored. We write the FIDO2 hybrid-attestation migration plan when WebAuthn is on the table.
Every signing attestation, vault event signature, regulator-facing receipt — scored. Co-signing migration plan to ML-DSA-65 so future auditors can verify your audit trail post-quantum.
Deterministic, methodology-citable. SVG + PDF certificate verifiable on qortrace.com/verify/<id>. Procurement teams + custody counterparties + regulators can cite the score directly.
The post-quantum migration is not a slide — it’s a specific set of standards, libraries, and key-management primitives. Below is what we touch on every engagement, why it exists, and what it protects you against.
The lattice-based key-exchange standard NIST finalised in August 2024. Replaces ECDH on every TLS 1.3 handshake, every IPsec tunnel, every messaging-app key wrap. We integrate the FIPS-203 module ML-KEM-768 by default (Level 3 security · ~256-bit classical · quantum-resistant).
The lattice-based signature standard. Replaces RSA-PSS and ECDSA on code-signing, document-signing, and TLS server authentication. We deploy ML-DSA-65 (Level 3) for transitional dual-signing alongside the classical algorithm during the migration window — never replace, always co-sign first.
The U.S. federal mandate: PQC primitives operational across National Security Systems by 2030, exclusive by 2035. Defines the exact KEM (ML-KEM-1024) and signature (ML-DSA-87) profile used at NSS-grade and the migration-pace expected from contractors. Every Cryptographic Migration Certificate we issue carries an explicit CNSA 2.0 attestation block.
The transitional posture every serious PQC rollout uses: combine a battle-tested classical primitive (X25519, the Curve25519 ECDH variant — or X448 at higher security level) with the post-quantum KEM in a single key-derivation step. If either side breaks, the other still holds. Browsers shipped this in 2024 (Chrome “X25519MLKEM768” group); we operationalise it for your endpoints.
The Open Quantum Safe project’s OpenSSL 3.x provider that exposes ML-KEM, ML-DSA, SLH-DSA, and the hybrid groups as first-class crypto algorithms inside any application that already speaks OpenSSL. We do not maintain a private fork — we ship upstream patches and point your CI at a reproducible build with a pinned commit.
The C library underneath everything else — implementations of every PQC candidate that ever entered NIST’s evaluation, including the four standardised winners (ML-KEM, ML-DSA, SLH-DSA, FN-DSA). Audited, side-channel-aware, and the de-facto reference for open-source PQC. We pin the version, we record the commit hash, and the hash makes it onto your migration certificate.
The version line that gives us providers (modular crypto), proper FIPS module isolation, and the runtime negotiation hooks needed to ship hybrid TLS without a fork. We standardise every engagement on OpenSSL 3.2+ and surface the version on the certificate so auditors don't need to grep your container builds.
Where your most sensitive keys actually live. Every cloud KMS now exposes ML-KEM and ML-DSA key types (AWS “ML_KEM_768”, GCP “PQ_SIGN_ML_DSA_65”, Azure “ML-KEM”), and on-premise HSMs from Thales and Entrust ship FIPS-203/204 firmware lines. We map your existing key inventory, design the wrap-and-rotate path, and ship the runbook your SRE team executes — without you ever exposing key material outside the boundary.
One business day to a senior engineer. Fixed-fee scoping memo within five business days. NDAs available on request.
We use strictly-necessary cookies to run the app. With your consent we also use analytics cookies to understand how QorTrace is used so we can improve it. Cookie Policy · Privacy Policy