DEV Community

Cover image for Post-Quantum Signatures for AI Agents: Why ML-DSA Matters
João André Gomes Marques
João André Gomes Marques

Posted on • Edited on • Originally published at dev.to

Post-Quantum Signatures for AI Agents: Why ML-DSA Matters

Quantum computers will break RSA and ECDSA. If your AI agents sign actions today with classical cryptography, those signatures can be forged tomorrow.

NIST finalized ML-DSA (FIPS 204) as the standard for post-quantum digital signatures.

Why AI agents need post-quantum signatures

AI agents make consequential decisions. Audit trails signed with classical cryptography have a shelf life. Once quantum computers arrive, anyone can forge those records.

Using ML-DSA with Asqav

Asqav uses ML-DSA-44, ML-DSA-65, and ML-DSA-87 via liboqs. Signing happens server-side; the SDK is a thin client.

pip install asqav
Enter fullscreen mode Exit fullscreen mode
import asqav
from asqav import Agent

asqav.init(api_key="sk_...")
agent = Agent.create(name="financial-agent", algorithm="ml-dsa-65")
receipt = agent.sign(
    action_type="transaction:approve",
    context={"amount": 50000, "currency": "EUR"},
)
Enter fullscreen mode Exit fullscreen mode

Algorithm comparison

Algorithm Security Level Signature Size
ML-DSA-44 2 2,420 bytes
ML-DSA-65 3 3,309 bytes
ML-DSA-87 5 4,627 bytes

Links

Top comments (0)