Quantum Verify

Post-quantum cryptography, measured and dated

Aaim's public hostnames negotiate the hybrid post-quantum key exchange X25519MLKEM768, measured from outside, most recently on October 29, 2026. Signatures follow on dated commitments, and a cryptographic inventory that a gate re-derives from the code on every commit records where each algorithm stands. Quantum Verify, Aaim's identity and attestation system, is built on the same NIST standards and is in development.


Post-Quantum Program

Key exchange first, then signatures

RSA and elliptic-curve cryptography protect every TLS session, identity token and signed record in financial services, and a large enough quantum computer breaks both. NIST published the replacements on August 13, 2024: FIPS 203 (ML-KEM) for key establishment, FIPS 204 (ML-DSA) and FIPS 205 (SLH-DSA) for signatures. NIST IR 8547 deprecates the classical public-key algorithms after 2030 and disallows them after 2035.

Traffic recorded today can be decrypted once such a computer exists, so key exchange is the urgent surface. Aaim's public hostnames already negotiate X25519MLKEM768 with every client that offers it, under a declared TLS policy that sets TLS 1.2 as the floor. The hybrid exists in TLS 1.3 only, so the floor rises to TLS 1.3 on dated terms, and every connection Aaim configures at both ends moves to hybrid key exchange by March 31, 2027; a connection a cloud provider terminates is held to the provider's published date and, from January 31, 2027, measured daily from inside the network. Signatures matter most where a record is checked years after it is signed. License files and archive manifests will carry an ML-DSA-87 signature, and consent receipts and pledge records an ML-DSA-65 signature, beside the classical one from the first deployment of each signer and no later than June 30, 2027. Where Aaim verifies the record itself, both signatures must verify. Aaim ID publishes an ML-DSA-65 key on the same dates, signs its access tokens with it, and signs ID tokens with it for each institution that selects it. By June 30, 2028, no path on which Aaim holds both ends accepts a classical signature alone.

Every algorithm the platform relies on is listed in a cryptographic inventory with its parameters, quantum exposure, deployment status and the file that proves it, and a gate re-reads each row against the code on every commit. Quantum Verify carries implementations of ML-KEM, ML-DSA and SLH-DSA with known-answer tests, and production post-quantum signing keys will be held in a managed cloud key service. From January 31, 2027, this page carries the daily measurement of every public hostname with its date, and Aaim has already named the replacements should NIST deprecate ML-KEM-768 or ML-DSA: SLH-DSA (FIPS 205) for signatures, and HQC for key encapsulation once NIST publishes it.

Aaim's Post-Quantum Commitments

Key Exchange

X25519MLKEM768 (ML-KEM-768, FIPS 203)

Public hostnames: measured October 29, 2026. Connections Aaim configures at both ends: by March 31, 2027. Provider-terminated connections: the provider's published date, measured daily from January 31, 2027.

Digital Signatures

ML-DSA-87 and ML-DSA-65 (FIPS 204) beside the classical signature

Long-lived records, from each signer's first deployment and no later than June 30, 2027; both signatures must verify where Aaim verifies.

Classical Retirement

No classical-only signature accepted where Aaim holds both ends, by June 30, 2028

NIST IR 8547 deprecates the classical algorithms after 2030 and disallows them after 2035.


Zero-Knowledge Proofs

Prove compliance without exposing data

Zero-knowledge proofs allow proving a statement is true without revealing the underlying data. This reduces data exposure during vendor assessments, examinations, and cross-institutional verification. Quantum Verify's proof circuits are built as a library on Groth16.

KYC Completion Verification

Prove that a customer has completed KYC requirements without sharing the underlying identity documents, SSN, or verification details with the requesting party.

Regulatory Compliance Proof

Demonstrate that specific regulatory controls are satisfied without exposing the control implementation details or internal compliance documentation to unauthorized parties.

Vendor Assessment Attestation

During vendor assessments and examinations, reduce data exposure by proving compliance statements are true without revealing the full scope of internal controls.


QVToken Architecture

Cryptographic identity attestation

A QVToken is designed as a signed attestation that identity verification occurred. Each token carries proof of verification, never personal data, under an ML-DSA-65 signature (FIPS 204). The token is built as a library; production tokens will verify against an issuer-published key.

1

Mint

On successful identity verification, a QVToken is created containing a cryptographic attestation that verification occurred. The token contains proof-of-verification metadata, not personal data.

2

Verify

Any authorized party can verify a QVToken is valid and unrevoked by checking its ML-DSA signature against the issuer's published key and its status in the audit store. No personal data is exposed during verification.

3

Revoke

If an identity is compromised or verification is invalidated, the token is revoked. Revocation is recorded in the audit store for full lifecycle tracking.

Data Minimization by Design

QVTokens contain only the cryptographic proof that verification occurred, the timestamp, and a reference to the verification method. Personal data (name, SSN, identity documents) is never encoded in the token. This design enables verification sharing across institutional boundaries without creating additional data exposure.


Blockchain Audit Store

Tamper-evident compliance records

The audit store is designed to anchor compliance events to a public ledger, giving an audit trail cryptographic proof in place of attestation-based trust.

Immutable Record

Designed to anchor compliance events to a public ledger, creating a tamper-evident record that cannot be altered after the fact.

Merkle Proof Verification

Designed so any party can verify that a specific record existed at a specific time with a Merkle proof, without trusting any single authority.

Stronger Than PDF Reports

Traditional compliance relies on attestation-based trust: a PDF report signed by an auditor. A ledger anchor is cryptographic proof that the underlying data existed and was unaltered.

Examination Support

Tamper-evident audit trails are designed to spare examiners the independent reconstruction of compliance timelines during examinations.


Explore Quantum Verify

Learn how Quantum Verify is designed to bring post-quantum algorithms to your institution's identity verification and compliance records, and what is built today.