Watch · narrated walkthroughs

ML-DSA in Depth: What the Proofs, the Parameters and the Deployments Actually Rest On

FIPS 204 calls ML-DSA strongly unforgeable, hedges its signing randomness, offers three ways to sign, and the IETF has now fixed how its keys and signatures travel in certificates, messages and tokens. This paper series reads each of those decisions at the level of its evidence: what the quantum random-oracle proof actually assumes and where it was repaired, why a byte-exact signature matters for logs, tokens and ledgers, which fault attacks the rnd input stops and which it does not, what moves out of a hardware module when signing is split at the message representative, and what RFC 9881, RFC 9882, RFC 9964 and the composite draft settle or leave to the deployer. Every topic is tied to the signatures AI agents now depend on: signed tool calls, agent identities and model provenance.