Cardano Proposal Wan Make Dem Share Rules for Regulated Stablecoins

One new Cardano problem statement dey propose one common technical framework for regulated stablecoins wey dem build with CIP-113. The goal na to make wallets, exchanges and DeFi protocols fit support multiple compliant assets without dem needing build separate integration for each token.

By SongMarketCap

Updated:

Cardano News - Cardano Proposal Wan Make Dem Share Rules for Regulated Stablecoins

Pull request #1266, wey dem title “Standardisation of Regulatable Stablecoins,” enter Cardano CIPs repository on September 10 from Alex Moser.

The document no introduce any stablecoin or approved standard. E define one interoperability problem wey fit affect regulated token issuers and infrastructure providers across the Cardano (ADA) ecosystem.

CIP-113 Tokens Fit Need Separate Integrations

CIP-113 dey provide shared infrastructure for programmable tokens, including one registry, core validators and one common method to hold the assets. Individual token rules dem dey handle am through extra substandards wey each issuer go choose.

According to the new proposal, the differences fit create heavy integration work. One transaction fit need reference inputs, proofs and redeemers wey specific to the token rules and how dem deploy am.

One stablecoin fit use denylist, another fit restrict transfers to approved users, while one third fit require verification from external KYC service. Wallets, exchanges, custodians and decentralized applications need understand those requirements before dem fit construct valid transactions.

The shared substandard wey dem propose go give compliant stablecoins consistent transaction structure. Issuers fit keep different roles and configurations without forcing infrastructure providers to build completely new transaction logic for every asset.

The Draft Cover Freezing, Seizure and Redemption

The CPS list capabilities wey future standard fit need support. These include issuer-controlled minting and burning, supply cap, account freezing and ability to seize or destroy frozen balances.

E also propose separate permissions for minting, administration and enforcement actions. Multisignature authorization and key rotation go dey supported without forcing the issuer to migrate the token.

Freezes and seizures fit carry standardized reason codes, wey go allow wallets and auditors interpret the action without putting personal information for the blockchain. Basic token information, including the issuer and reference to im terms or white paper, fit also follow common format.

The draft put special attention for redemption. E dey ask how transfers fit pause during incident but still allow eligible holder return tokens to the issuer for repayment.

Dem map these requirements against the European Union MiCAR framework and the United States GENIUS Act. The document use those regulations as design references and e talk clearly say e no provide legal advice.

Technical and Regulatory Questions Still Open

PR #1266 still open, e no get assigned CPS number and e no contain finalized solution. The current purpose na to collect feedback from stablecoin issuers and infrastructure providers before dem write technical standard.

Reviewers don request closer alignment with the ongoing development of CIP-113. Dem also warn say comparisons of existing implementations fit quick become outdated and make dem separate am from requirements wey suppose remain relevant over time.

Unresolved questions include whether denylist and allowlist systems fit use the same transaction structure, how dem go exclude personal data from permanent blockchain records and how protocols fit identify changes to issuer validation logic.

The proposal still dey ask whether issuer suppose fit freeze assets wey dey inside DEX pool or lending protocol, and how those applications fit evaluate that risk before dem list token.

CIP-113 don mark as dey in Last Check, but im pull request never merge enter the main CIPs repository. The regulated stablecoin CPS therefore no create any new requirements for issuers or applications for the ADA ecosystem.

The next steps go depend on CIP triage, feedback from issuers and confirmation say the proposed requirements fit implement without breaking CIP-113 into incompatible versions.