Cardano reviews quantum security, stablecoin rules in latest CIP update

Cardano has outlined new proposals for regulated stablecoins and quantum-resistant signatures in its November 1 improvement proposal roundup, alongside ongoing governance metadata discussions and two completed documentation items.

Summary

• Cardano’s November 1 CIP roundup features proposals covering regulated stablecoins and post-quantum signature verification.
• A stablecoin draft seeks common compliance requirements so wallet providers can support multiple programmable tokens.
• CIP-0206 proposes two quantum-resistant signature verification functions for Plutus smart contracts.
• Developers are reviewing governance metadata rules, particularly support for different signing methods.
• CIP-0204 and CPS-0037 have completed documentation milestones, although their status does not mean every proposed feature is operational.

According to the Cardano Improvement Proposals repository, the latest work covers how regulated digital assets interact with wallets, how smart contracts verify signatures and how ADA holders communicate their views on governance decisions.

The weekly roundup, compiled by CIP editor Robert Phair, identified two new submissions, one governance issue under review and two items that reached completion during the latest review cycle.

Cardano stablecoin proposal seeks common compliance standard

One submission focuses on standardizing regulated stablecoins created using Cardano’s CIP-0113 programmable-token framework.

The draft problem statement, filed under pull request 1266, argues that individual programmable stablecoins currently need separate integrations because their transaction requirements can differ.

For wallet developers, exchanges and other infrastructure providers, supporting each token separately means additional technical work. The author proposes a shared set of requirements that issuers across different jurisdictions could use.

A common integration would allow service providers to support multiple qualifying tokens without rebuilding their systems for every issuer.

However, the proposal remains open for discussion. Its author has requested feedback from issuers on regulatory requirements and from infrastructure providers on whether a shared standard would work in practice.

The effort builds on CIP-0113’s programmable token framework, whose mainnet implementation was announced in October.

As crypto.news previously reported, CIP-0113 allows asset issuers to apply selected identity checks, transfer restrictions and administrative controls to tokens issued under the framework.

Those permissions apply to participating programmable assets, not to ordinary ADA holdings.

The Cardano Foundation subsequently joined a Swiss tokenization association after the Capital Markets and Technology Association recognized a CIP-0113 implementation for tokenized equity securities.

Quantum-safe signature proposal enters CIP review

A separate submission from Quantova Inc. addresses Cardano’s preparations for quantum-resistant cryptography.

The proposed CIP-0206 introduces two signature verification functions for Plutus, Cardano’s smart contract platform.

Its authors selected ML-DSA and SLH-DSA, two algorithms standardized by the U.S. National Institute of Standards and Technology under FIPS 204 and FIPS 205.

ML-DSA uses lattice-based cryptography, while SLH-DSA relies on hash-based techniques. The submission proposes supporting both so developers can verify signatures created using different cryptographic approaches.

Quantova has supplied reference code, encoding rules and test cases. The accompanying documentation describes tests involving valid signatures, altered messages and mismatched signing methods.

Although the tests provide a starting point, adding verification functions to Cardano’s consensus-critical Plutus evaluator would require a network hard fork.

The proposal therefore does not represent an activated security upgrade or a change to existing wallet signatures.

Cardano founder Charles Hoskinson has previously discussed quantum computing risks and the difficulties blockchain networks face when replacing established cryptographic methods.

The latest submission addresses verification inside smart contracts, leaving any wider migration of Cardano accounts and transaction signatures to separate work.

Governance metadata rules remain under review

Another discussion concerns how Cardano governance records identify the signatures used to authenticate submitted metadata.

In GitHub issue 1302, contributors questioned why the CIP-0169 governance metadata schema no longer listed CIP-0008 as an accepted witness algorithm.

The change raised concerns about compatibility with existing hardware-wallet signing methods.

Reviewers examined whether the earlier entry should be restored and how the various governance metadata specifications describe supported signing arrangements.

The discussion has since included the relationship between CIP-0100 and CIP-0108, which document different parts of Cardano’s governance metadata system.

Developers are considering clearer documentation to explain how these related schemas should be interpreted and extended.

Two Cardano proposal documents reach completion

The roundup identified CIP-0204, titled Holder Answers on Governance Actions, among the completed items.

The specification describes a way for ADA holders to record Yes, No or Abstain responses to governance actions through transaction metadata signed with their stake keys.

These responses would provide a public record of holder preferences without replacing the formal voting responsibilities of delegated representatives, stake pool operators or the Constitutional Committee.

CIP-0204 remains classified as Proposed in the repository, despite its completed review milestone.

The second item, CPS-0037, concerns difficulties developers encounter when Cardano’s minimum unspent transaction output requirement affects application design and transaction construction.

A Cardano Problem Statement documents an issue for community discussion and potential future solutions. Completing the document does not itself change the network’s minimum transaction output rules.