On October 7, CoinDesk reported that Cardano had launched CIP-0113, a programmable-token standard for regulated stablecoins, funds and bonds. The stated use case is straightforward: issuers can restrict recipients, screen transfers and, when policy permits, freeze, seize or redirect holdings. The controls apply at every movement of the token, not only when it is minted or redeemed.

That distinction matters. A conventional Cardano native asset can be created under a minting policy and then transferred within Cardano’s UTxO accounting model. CIP-0113 puts regulated assets in a script-enforced path instead. The asset may still look like a token balance in a wallet, but moving it requires the transaction to satisfy rules set by the issuer.

“The rules have to travel with the asset and be enforced every time it moves,”

The Cardano Foundation announced that the standard is live on mainnet, with KYC, AML, sanctions, freeze, seizure and transfer restrictions available as ledger-enforced controls. The product has shipped. What remains unproven is usage: no issuance, circulation or settlement figures were published with the launch.

A native asset is not automatically a programmable asset

The cleanest way to understand the standard is to separate the token from the conditions attached to spending it.

With an ordinary native asset, a holder creates a transaction that consumes UTxOs containing the asset and creates new UTxOs for the recipient. The network verifies signatures, transaction structure and the relevant minting policy. The transfer does not normally call an issuer’s compliance rulebook.

With CIP-0113, the token is held under a shared validator. The transaction must present the correct redeemer and satisfy the asset’s configured policy before the UTxO can be spent. The policy can ask whether the sender and receiver are approved, whether either is sanctioned, whether a transfer limit applies, or whether the particular holding is frozen.

CIP-0113 PROGRAMMABLE ASSET PATHSIGNED TRANSACTIONSETTLED OUTPUTASSET-BEARING TRANSACTIONPOLICY INPUTSAPPROVAL OR REJECTIONAPPROVED ASSET OUTPUTHOLDERWALLETUTXOordinaryCardanonativeTRANSACTIONsignatureandledgerRECIPIENTWALLETnew UTxOHOLDERWALLETUTXOCIP-0113programmableassetSHAREDVALIDATORredeemerandpolicyCOMPLIANCEMODULESidentitysanctionsfreezeRECIPIENT-ASSOCIATEDOUTPUT UTXOlocked bysharedvalidatorTransfers are rejected when any required check fails
Figure 1 - How ordinary Cardano transfers differ from programmable-asset transfers subject to on-chain compliance checks

This is not merely a blacklist table that an issuer consults offchain after settlement. The rule sits on the path to settlement. The network will not accept a noncompliant transfer if the validator rejects it. CoinDesk described the design as using a shared smart contract to control movement and said the standard required no Cardano hard fork.

That is useful to regulated issuers because the restriction follows the asset across wallets and services. It is also a direct reduction in the permissionlessness of that asset layer. ADA itself remains ADA. A CIP-0113 stablecoin or fund token is a different bargain.

The keys matter more than the freeze button

“Can the issuer freeze tokens?” is the headline question. It is not the hard one.

The harder questions are: which role can freeze, what exactly can it freeze, who can transfer assets without the holder’s consent, and how can that authority change? Those answers determine whether a token is suitable for an exchange, a lending protocol or an institutional custodian.

Cardano’s technical overview describes a modular system built around a shared validator, a token registry and stake-credential ownership. It also uses a withdraw-zero pattern, allowing the validator to run through a zero-value withdrawal rather than treating every policy check as a token transfer. Wallets, explorers and applications need to recognize that a visible balance may carry rules beyond ordinary ownership.

The CIP-0113 reference implementation sets out roles for token registries, shared custody, issuer-authorized transfer and third-party delegates, alongside an upgrade authority and selectable policy modules. In practice, a regulated issuer can divide authority rather than put every power behind one operational key.

A compliance key might update a sanctions state. A recovery delegate might be authorized to move tokens under a court order. An upgrade authority might change the module set if rules or regulations change. A multisignature arrangement can reduce dependence on one signer, but it does not remove discretion. It distributes it.

POLICY AND ROLE DEFINITIONSMOVE TOKENS UNDER COURT ORDERPOLICY IDENTIFIER AND ENABLED MODULESPOLICY AND ROLECONFIGURE RULESUPDATE SANCTIONS STATEMOVE TOKENS UNDER COURTREPLACE MODULEPOLICY IDENTIFIERTOKENREGISTRYpolicyidentifier,modulesSHAREDVALIDATORenforcesprogrammableasset policyISSUERADMINauthorityroleCOMPLIANCEKEYauthorityroleRECOVERYDELEGATEauthorityroleUPGRADEAUTHORITYauthorityroleWALLET •EXPLORER •EXCHANGEdisplay“programmableassetDistributed authority limits dependence on one operational key but does not remove discretion
Figure 2 - How a Cardano programmable token exposes its policy, authority roles and issuer intervention powers

For users, the practical issue is disclosure. A wallet or exchange should be able to identify the policy identifier, the enabled modules, the relevant authority roles and the conditions under which an issuer can intervene. A token symbol alone says almost nothing. Two assets called USDx could have entirely different holder rights.

That is especially important for collateral. CoinDesk noted that the specification tells lending services to examine issuer powers before accepting such tokens as collateral. A token that can be seized or redirected introduces a risk that does not exist for an unrestricted asset held in the same wallet.

What a regulated transfer looks like

Consider a fund token issued only to verified investors.

First, the issuer mints units into the shared custody arrangement and records the token’s policy configuration. The investor completes the issuer’s onboarding process. The issuer or a delegated compliance provider associates an approved credential with the investor’s wallet or stake credential.

Next, the investor sends the token to another wallet. The transaction names the relevant token UTxO and provides the data required by the shared validator. The validator reads the applicable modules. It checks whether the sender may spend, whether the recipient is eligible, whether either side is restricted and whether the UTxO is frozen.

If all checks pass, the consumed UTxO becomes new output UTxOs controlled for the recipient. If one check fails, settlement does not occur. There is no later reversal to negotiate because there was no valid onchain transfer in the first place.

1 Mint issuer unitsIssuer creates the token
minted token units
2 Investor identity approvalWallet or stake credential is approved
identity approval
3 Holder builds transfer transactionNames the token UTxO and validator data
transfer transaction and token UTxO
4 Shared validator checks policy modules✓ eligible recipient ✓ not restricted ✓ not frozen
failed compliance checkvalidated transaction
Reject transactionNo valid onchain transfer occurs
5 Ledger accepts compliant UTxO spendThe consumed UTxO becomes recipient output UTxOs
recipient-controlled output UTxO
6 Recipient receives tokenSettlement completes onchain
Figure 3 - How Cardano’s shared validator checks a token transfer before the ledger accepts the spend

Exceptional intervention follows the same principle, but the signer and rule are different. If a wallet is compromised or a legal order requires action, the authorized delegate can invoke the freeze or seizure path defined by the token policy. The validator still decides whether the transaction is valid. The issuer does not get a general network-level ability to alter Cardano balances.

The contrast with Ethereum stablecoin controls is useful. Decrypt reported that Circle and Tether froze about $318,000 in USDC and USDT associated with a September Bitget exploit, while roughly 170 ETH in the same wallet could not be frozen by either issuer. Issuers can control their own token contracts, not the base asset of the chain.

For USDC and USDT holders, this means Ethereum issuers can freeze funds through each token’s contract, while CIP-0113 places comparable Cardano restrictions in a shared, issuer-configured validation path.

Seizure is harder than the word suggests

Status: open GitHub issue; argued failure mode, not independently demonstrated behavior across every implementation. In GitHub contributor nemo83’s audit issue, the contributor argues that UTxO fragmentation can make a full seizure non-atomic: if a holder’s balance sits across several UTxOs, recovery may require multiple transactions. Some units could remain spendable between those transactions unless they are frozen first.

That is not a philosophical objection. It is an operational one. A seizure process that assumes “balance” means one object can fail when the balance is actually several independently spendable outputs. The issue argues that freezing first is necessary where atomic seizure guarantees are required. A maintainer or specification response is needed to establish whether freezing is required for atomic seizure under CIP-0113’s intended design.

The standard’s upside is compliance that is explicit, programmable and visible to validators. Its cost is a new governance surface: key rotation, compromised delegates, disputed legal orders, module upgrades and user disclosure all become part of the token’s risk model.

The specification demonstrates configurable asset controls; what remains unknown is any published issuance or transfer data. Before accepting a CIP-0113 asset, users should verify its supply, enabled modules, authority roles, freeze or seizure conditions, and whether their wallet or exchange clearly discloses those powers.

#Cardano#CIP-0113#Cardano Foundation#CoinDesk#Ethereum#Circle#Tether

Daniel Friedman is not a person. No notebook, no deadlines, no face behind the name — just a byline this newsroom publishes under. Here is the production line underneath it, because a name beside a portrait reads like a journalist, and this one is not one.

The models. Writing: gpt-5.6-luna. Out on the live web: gpt-5.6-terra and gpt-5.6-luna. Pictures: gpt-image-1. Swap one in the newsroom and this line swaps with it — it is read off the machines, not typed here.

How a story is made

  • Research. The searching model reads around the story, pointed at primary sources — the filing, the post, the repository — rather than at somebody else's write-up of them.
  • Writing. The writing model drafts it against what was found, at Daniel Friedman's usual length and in Daniel Friedman's usual register.
  • The loop. A reviewer reads the draft and sends it back with notes. Then reads it again. A piece can go round several times before it leaves the building.
  • Enrichment. A quotation has to appear word for word on the page it is taken from. A chart may only use figures that appear in the source it cites. Whatever fails is dropped, and the reason is kept.
  • Fact check. A last pass hunts for claims the article makes and its sources do not.
  • A human stop. Sensitive subjects are held for a person to read before publication, and a person can kill any of it at any point.

If that sounds less like a newsroom and more like a factory: quite. It is called Press Factory.

This article was generated using AI and published automatically without human pre-publication review.

How this article was made

The article was produced by the Grandmonts Media News Engine using automated research, drafting and verification workflows. No human editor reviewed the article before publication. Grandmonts Media remains responsible for the published content. Errors can be reported at office@grandmonts.cz.