ML-DSA-65 signed proofs are live on the gateway sidecar

Post-Quantum signed proofs

PaychainX seals every payment in a tamper-evident audit proof. As of this release, the gateway sidecar signs those proofs with ML-DSA-65 (FIPS 204), the NIST post-quantum signature standard, and a signed receipt was independently verified. The in-browser demo below shows the envelope structure; the real ML-DSA-65 signing runs live on the gateway and anyone can verify it.

Hybrid post-quantum lattice audit
Live nowNew

ML-DSA-65 signed proof receipts are live

PaychainX upgraded the post-quantum gateway sidecar from hash-only proofing to ML-DSA-65 signed proof receipts. A signed transaction proof was generated and independently verified through the public verify endpoint, returning valid = true. This moves PaychainX beyond a roadmap-only post-quantum posture to a live, quantum-resistant signature on every proof.

Verified proof receipt
Proof referencepaychainx-mldsa-proof-002
Proof IDpq_753a928f5a0ed7e3
Payload hashfd3b93c7…c871f14c
Signature algorithmML-DSA-65 (FIPS 204)
Key idpaychainx-mldsa65-e904452436d5
Verificationvalid = true
Public PQ gateway endpoints
Signed proofPOST /proof
VerifyPOST /verify
Hostpq.paychainx.ai

The sidecar performs payload hashing, signed receipt generation, ML-DSA-65 public-key verification, signed routing proofs, signed processor handoff proofs, and signed audit receipts.

Honest scope: signatures are live with ML-DSA-65 in the gateway sidecar, hashing is SHA-256, and ML-KEM (Kyber) key exchange remains roadmap-ready. Anyone can independently verify a receipt by posting its message, signature, and public key to pq.paychainx.ai/verify.

Why now

The post-quantum clock is federal, and it is running

On June 22, 2026 the President signed an Executive Order, Securing the Nation Against Advanced Cryptographic Attacks, directing the move to NIST post-quantum standards. It calls out the harvest now, decrypt later threat, where adversaries capture encrypted data today to break it once a quantum computer exists. The deadlines are concrete:

Key establishment to PQCby Dec 31, 2030
Digital signatures to PQCby Dec 31, 2031
FAR contractor complianceby Dec 31, 2030
StandardsFIPS 203 ML-KEM, FIPS 204 ML-DSA

PaychainX is built for this. The audit envelope already reserves the exact NIST slots, pq_sig: ml-dsa for signatures and pq_kem: ml-kem for key establishment, so the migration is wired into the architecture today, ahead of the federal timeline. A payments platform that can prove a quantum-resistant audit trail is years ahead of processors that have not started. Read the Executive Order.

1 · Classical audit proof Live today

Every payment commits to a tamper-evident proof: proof_hash = SHA‑256(canonical(payload)), where canonical JSON sorts keys recursively. This reproduces the gateway's real audit proof (hash_algorithm: sha256) in your browser.

press compute
press compute
not verified yet
Real cryptography: changing one character of the payload changes the hash, so verification fails. Try the Tamper button.

2 · Hybrid post-quantum envelope ML-DSA-65 live on gateway Browser demo

The SHA-256 audit above is sealed, and the gateway sidecar now signs that proof with ML-DSA-65 (FIPS 204), the NIST post-quantum signature standard, producing a signed receipt that anyone can verify at pq.paychainx.ai/verify. Web Crypto in the browser cannot run ML-DSA, so this panel demonstrates the envelope shape with an HMAC-SHA512 stand-in for the signature and a hybrid_attestation block. The real ML-DSA-65 signature is generated server-side on the gateway. The envelope shape stays constant, so the migration was drop-in.

compute the proof above, then build the envelope
Honest split: the SHA-512 hash and HMAC-SHA512 value shown here are a browser stand-in for the envelope shape. The production signature is real ML-DSA-65 generated by the gateway sidecar and is live, verified valid = true. ML-KEM (Kyber) key exchange remains roadmap-ready; hashing is SHA-256.

Key lifecycle

Classical audit live

Every payment emits a SHA-256 proof_hash over canonical JSON.

Proof schema pre-wired

The proof record reserves the signature and signature_algorithm fields for the PQ signature.

ML-DSA-65 sidecar live

The sidecar signs each proof with ML-DSA-65, independently verified valid = true.

Hybrid enforced

Set pq_mode to hybrid-enforced so every audit requires a valid PQ signature.

5
ML-KEM key exchange

Add ML-KEM (Kyber) for quantum-safe key establishment, plus scheduled key rotation.

pq_mode progression

offclassical audit only
hybrid-ready (today)ML-DSA-65 signed, not yet required
hybrid-enforced (next)valid PQ signature required
pq_sigml-dsa-65, live
pq_kemml-kem, roadmap

Backwards compatible at every step. The envelope shape never changes, so merchants integrate once and the PQ guarantees strengthen underneath them.