Skip to content
Crypto

Cardano reviews quantum security, stablecoin rules in latest CIP update

4 min read

Cardano reviews quantum security, stablecoin rules in latest CIP update

Cardano has introduced new proposals for regulated stablecoins and quantum-resistant signatures in its November 1 improvement proposal roundup. The update also covers ongoing discussions about governance metadata and two items that have completed their documentation milestones.

Summary

  • Cardano’s November 1 roundup includes proposals for regulated stablecoins and quantum-resistant signature verification.
  • One stablecoin proposal aims to create 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, including support for different signing methods.
  • CIP-0204 and CPS-0037 have completed documentation milestones, but this does not mean all their proposed features are already active.

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

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

Cardano stablecoin proposal aims for common compliance standards

One proposal focuses on creating common standards for regulated stablecoins issued through Cardano’s CIP-0113 programmable-token framework.

The draft, submitted under pull request 1266, explains that different programmable stablecoins currently require separate integrations because their transaction rules can vary.

This creates extra technical work for wallet developers, exchanges, and other service providers that want to support multiple tokens. The proposal suggests creating a shared set of requirements that issuers in different jurisdictions could follow.

With a common standard, service providers could support several qualifying stablecoins without having to build a separate integration for every issuer.

However, the proposal is still open for discussion. Its author is seeking feedback from stablecoin issuers about regulatory requirements and from infrastructure providers about whether a shared standard would work in practice.

The proposal builds on Cardano’s CIP-0113 programmable-token framework, which was announced for mainnet implementation in October.

CIP-0113 allows issuers of participating tokens to apply identity checks, transfer restrictions, and administrative controls. These rules apply only to supported programmable tokens, not to regular ADA holdings.

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

Quantum-resistant signature proposal enters review

Another proposal from Quantova Inc. focuses on preparing Cardano for future quantum-computing risks.

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

The proposal uses ML-DSA and SLH-DSA, two algorithms standardized by the US 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 cryptography. Supporting both would allow developers to verify signatures created through different cryptographic methods.

Quantova has provided reference code, encoding rules, and test cases. The documentation includes tests for valid signatures, altered messages, and mismatched signing methods.

However, adding these verification functions to Cardano’s Plutus evaluator would require a network hard fork.

This means the proposal is not yet an active security upgrade and does not change the signature methods used by existing wallets.

Cardano founder Charles Hoskinson has previously discussed the risks quantum computing could create for blockchain networks. The latest proposal focuses specifically on signature verification within smart contracts. Any wider change to Cardano accounts and transaction signatures would require separate work.

Governance metadata rules remain under discussion

Another issue involves how Cardano governance records identify the signatures used to verify 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 discussed whether the earlier entry should be restored and how Cardano’s governance metadata specifications describe supported signing methods.

The discussion also covers the relationship between CIP-0100 and CIP-0108, which explain different parts of the governance metadata system.

Developers are now considering clearer documentation to explain how these related standards should be understood and extended.

Two Cardano documents reach completion

The roundup also listed CIP-0204, titled Holder Answers on Governance Actions, among the items that completed a review milestone.

The proposal 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 create a public record of holder preferences. However, they would not replace the formal voting responsibilities of delegated representatives, stake pool operators, or the Constitutional Committee.

Although its review milestone is complete, CIP-0204 is still classified as Proposed in the repository.

The second completed item, CPS-0037, addresses problems developers face when Cardano’s minimum unspent transaction output requirement affects application design and transaction creation.

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

Leave a Reply

Your email address will not be published. Required fields are marked *