The Ledger
Cardano Assigns CIP-0206 to Quantum-Resistant Plutus Signatures
Cardano’s CIP editors confirmed a proposal for ML-DSA and SLH-DSA signature-verification functions in Plutus, while the open pull request leaves implementation unsettled. A November 1 test report says 32 vectors passed, later than an October 17 comment that described 31.

“The conformance target is now a single CIP file, test-vectors.json, with 31 vectors, each stating the property it establishes.”
Quantova Inc., proposal author, in an October 17 comment
Candidate status, not a network upgrade
Cardano CIP editors confirmed the post-quantum signature proposal as candidate CIP-0206 on October 28, assigning it a place in the community review process. Quantova Inc. submitted the proposal to add two signature-verification built-ins to Plutus, Cardano’s smart-contract platform. The GitHub pull request remains open, and the candidate label does not mean the proposal has been approved for deployment.
The distinction matters: CIP-0206 describes a proposed capability for Plutus developers, not a change to the signatures used by Cardano wallets or ordinary transactions. Integrating the built-ins into the consensus-critical Plutus evaluator would require a hard fork. The proposal gives no activation date.
Two NIST schemes, two verification functions
The draft specifies verifyMlDsaSignature and verifySlhDsaSignature, corresponding to ML-DSA and SLH-DSA. The schemes use different cryptographic approaches: ML-DSA relies on lattice-based cryptography, while SLH-DSA uses hash-based cryptography. The proposal draws on the standards published as FIPS 204 and FIPS 205.
Both functions take a public key, a message and a signature as byte strings, and return a Boolean result. The specification uses a versioned encoding with an identifier for the selected scheme, rather than trying to infer the algorithm from the input’s size. Its authors also discuss Falcon and SQIsign as possibilities for later identifiers, rather than including them in the proposed pair of built-ins.
Test vectors and transaction-size concerns
The October 17 comment quoted above described the conformance file as containing 31 vectors. That was an earlier count, not the latest reported test result. On November 1, Quantova said a script ran every vector in test-vectors.json through a stock OpenSSL build and reported 32 passed. The pull-request discussion does not explain the difference between the October 17 count and the later test result, so 31 should not be presented as the current total. The proposal describes checks for encoding and verification, including valid signatures, altered messages, mismatched schemes and malformed inputs. Quantova says it will maintain the vectors and support Cardano’s Plutus and ledger teams during implementation and cost-model work.
Reviewers have also raised a practical constraint: signature size. The pull-request discussion cites 3,309 bytes for ML-DSA-65 and 7,856 bytes for SLH-DSA-SHA2-128s, compared with a 16-kilobyte transaction limit. The larger figure applies to the SLH-DSA variant; a reviewer warned that large witnesses could leave less room for other transaction data and raise questions about network timing assumptions. Those figures are not a Plutus performance benchmark, and the proposal says native cost assessment remains part of the implementation work.
Plutus support would not settle Cardano’s wider migration
Cardano’s separate problem statement CPS-0027 describes the lack of practical, built-in post-quantum signature verification for script and decentralized-application developers. It names existing Plutus verification operations for Ed25519 and secp256k1-based signatures, which would be vulnerable to a sufficiently capable quantum computer running Shor’s algorithm. CIP-0206 addresses that specific smart-contract gap, not the broader task of changing account keys, wallet signatures or the network’s other cryptographic components.
The candidate can now receive technical and community scrutiny, while the pull request’s open status and hard-fork requirement leave implementation unsettled. Its concrete proposal is for Plutus verification functions and encoding rules; it does not provide quantum-resistant signature support on Cardano’s live network.
Sources
- Original source Cardano Improvement Proposals on GitHub github.com
Other pages read
- Cardano Improvement Proposals cips.cardano.org