CoinDesk reported that Cardano has launched CIP-0113, a token standard intended for regulated stablecoins, funds and bonds. The CIP-0113 specification defines a framework for attaching programmable transfer policy to a token; it does not require every token using the standard to enable every possible restriction or administrator power. Its defining feature is straightforward: compliance policy can become part of the token’s onchain transfer logic.

That is a meaningful shift from the familiar model of crypto ownership. With a conventional native token, holding the relevant private key normally means a holder can send the asset to any valid address, subject to basic network rules. An issuer may impose terms in legal agreements, pressure exchanges to block deposits, or maintain an offchain whitelist. But the holder’s wallet remains the immediate technical source of spending authority.

CIP-0113 introduces another layer. A transfer can be valid only if it satisfies policy encoded around the asset. Depending on the rule set an issuer selects, that policy may require recipient authorization, reject sanctioned destinations, freeze a position, permit a regulated transfer agent to reassign holdings, or apply another custom condition chosen by the issuer. Those are configurable policy features, not universal powers embedded in every CIP-0113 token.

For institutions, this is not simply a compliance feature. It changes the asset’s control surface. The important question becomes: who has practical authority over a balance at the moment it needs to move?

From transferable token to conditional token

A regulated asset has always had constraints. A money market fund may accept only eligible investors. A private credit vehicle may limit secondary transfers. A stablecoin issuer may have legal obligations to block sanctioned users or respond to court orders.

The historic difficulty was keeping those requirements intact once the asset moved through self-custody wallets, decentralized exchanges, lending pools and settlement systems. Compliance was often enforced at an entry point, such as issuance or redemption, while token transfers themselves stayed broadly open.

CIP-0113 takes the opposite approach. Instead of treating compliance as a gate around the system, it allows an issuer to make compliance a test within the token’s movement path. A holder can sign a transaction, but that signature alone may not be enough if the asset’s configured policy requires additional conditions.

Holder Walletcontrols the tokens
signed transfer request
Transaction Builderassembles the transfer
assembled token transfer
CIP-0113 Policy Contractchecks issuer-defined conditions
recipient not authorized, sanctioned, or frozenpolicy conditions and transfer data
Transfer Rejectedpolicy condition not met
Cardano Validatorsverify the transaction
validated transfer
Recipient Walletreceives the tokens

A signature starts the path; policy conditions decide whether it completes

Figure 1 - How a CIP-0113 token transfer carries issuer-defined compliance checks through the movement path

A simple transfer can now involve several distinct questions:

  1. Does the sender control the tokens?
  2. Does the token’s configured policy permit the sender to transfer them?
  3. Is the recipient eligible to receive them, if recipient authorization is required?
  4. Is the token or account under a configured freeze condition?
  5. Does an authorized administrator have a contrary instruction, where the issuer has granted that authority?
  6. Has the policy itself been updated since the holder acquired the asset?

The transaction succeeds only when the conditions required by that token’s policy hold. This matters because a wallet can accurately display a balance that its owner cannot freely use.

That distinction is familiar in traditional finance. A shareholder may own stock subject to transfer restrictions. A bank account may show funds that have been restrained by a legal order. CIP-0113 allows that kind of conditional ownership to enter a public blockchain workflow, where the restriction can be evaluated before a transaction is accepted.

The resulting product can be more suitable for real world assets, but it is not economically equivalent to an unrestricted cryptocurrency, even when both appear in the same wallet interface.

Where the control actually sits

The most useful way to understand a CIP-0113 asset is to separate custody from control.

A holder may retain the private key and still lack unilateral spending power if the issuer has configured policy constraints. The issuer may not hold the token directly, but may control a policy role that determines whether the token moves. A regulated administrator may have the ability to update a whitelist or, if those powers are configured, execute a freeze or reassignment. A governance process may be able to alter the underlying rules later.

These are different authorities and should not be collapsed into the vague claim that an asset is either “custodial” or “self-custodied.”

FREEZES OR REASSIGNS IF CONFIGUREDSIGNS TRANSFERSETS RULE MODULEFREEZES OR REASSIGNS IFCHANGES UNDERLYING RULESCIP-0113ASSETmoves onlyunderconfiguredHOLDER KEYcreates thetransferrequestISSUERPOLICYROLEdefinespermittedtransferCOMPLIANCEADMINISTRATORoperationalcompliancepowersCARDANOGOVERNANCEcan altertheunderlyingAccent = direct transfer authority; alt = rule-changing authority
Figure 2 - The distinct authorities that can move, constrain, administer, or reshape a CIP-0113 asset

The holder key is the first control point. It creates the transfer request and remains important for ordinary voluntary movements. Yet it may be constrained by policy.

The issuer policy role is the second. This authority defines the permitted transfer logic, whether through a standard ruleset or customized conditions. The crucial diligence question is whether that role is fixed, time-limited, subject to multiple signatures, or able to make unilateral updates.

The compliance administrator is the third. An issuer might delegate operational actions to a transfer agent, compliance provider or trustee. Depending on the policy the issuer configures, this role may be allowed to authorize recipients, maintain a denial list, freeze an asset, or initiate seizure and reassignment. A token holder needs to know not only that such a role exists, but also what powers it actually has, what triggers them, and whether its actions are public, reversible and appealable.

Governance is the fourth. CoinDesk’s July report on Cardano’s Van Rossem hard fork described a network upgrade approved through Cardano’s onchain governance system, rather than directed solely by its founding developer. That matters here because token policy does not operate in a vacuum. The application rules may be set by an issuer, while the broader execution environment evolves through network governance.

Under Cardano’s governance, ADA holders can approve protocol upgrades, parameter changes and treasury withdrawals; they do not thereby alter a token issuer’s transfer or redemption policy. Where an issuer uses CIP-0113, the issuer or its administrator, not protocol governance, sets and may update the token’s compliance rules, including any freeze or seizure authority the issuer has elected to configure.

Restricting the token is not the same as restricting the account

This distinction is easy to miss and essential for risk analysis.

An account-level restriction targets a wallet or identity. The effect can extend across every asset that relies on that account’s status. For example, a compliance system might mark a wallet ineligible, preventing it from receiving any asset governed by that system.

A token-level restriction targets a particular asset or position. The same wallet could hold unrestricted ADA, an open stablecoin and a restricted fund token. The wallet might be able to transfer the first two while the fund token remains immobile.

That granularity has advantages. It avoids making a single compliance event contaminate unrelated assets. It also lets issuers apply rules that match the legal character of a specific instrument. A tokenized bond and a retail payment token may need different recipient checks, transfer windows and administrative powers.

But granular policy also creates operational complexity. Wallets and portfolio systems must communicate that a displayed balance is subject to rules. A user should not discover only at settlement that a token cannot be delivered to the selected counterparty.

A serious interface should distinguish at least four states where they are supported by the asset’s policy: transferable, transferable only to eligible recipients, frozen, and subject to administrator reassignment. It should also show the policy version and identify the parties that can change status.

Freeze, seizure and the difference between each

“Freeze” and “seize” are often used together, but they produce different risk profiles. Neither is an inherent feature of every CIP-0113 token; each depends on the policy capabilities an issuer chooses to enable.

Where a policy provides for it, a freeze generally prevents a balance from moving. The holder still appears to own the asset, but cannot spend, sell, pledge or redeem it through the ordinary transaction path. The freeze may be narrow, affecting a specified quantity, or broad, affecting all holdings of that asset at an address.

Where a policy provides for it, seizure, clawback or forced transfer goes further. An authorized role can move the asset without the holder initiating the transaction. That power may be necessary where a court order, fraud recovery process or sanctions obligation requires more than immobilizing a balance. It is also the feature that most directly weakens the assumption that possession of a private key settles all questions of control.

ADMINISTRATOR FREEZE ORDER, IF CONFIGUREDAUTHORIZED CLAWBACK, IF CONFIGUREDTRANSFER TO COURT, ISSUER, OR REPLACEMENT HOLDERADMINISTRATOR FREEZERELEASEAUTHORIZED CLAWBACK, IFTRANSFER TO COURT, ISSUERACTIVERECIPIENT-RESTRICTEDFROZENSEIZEDREASSIGNED
Figure 3 - How configured issuer powers can restrict, freeze, seize, and reassign Cardano token holdings

The design question is not whether such power is good or bad in the abstract. It is whether the power, if configured, fits the asset’s purpose and is disclosed precisely enough for a holder to price the risk.

A regulated stablecoin used for institutional settlement may need a credible sanctions response. A tokenized fund may need to reverse a transfer made to an ineligible investor. A payroll token or merchant payment balance, by contrast, may be less useful if every recipient must fear opaque administrative intervention.

The best implementations will make extraordinary powers narrow, rule-bound and auditable. A well-designed policy should specify who can act, what evidence or event is required, whether multiple approvals are needed, where the action is recorded, and whether a mistaken action has a defined remediation path.

Wallet compatibility is a security issue, not a marketing detail

CIP-0113 can work across wallets and applications that implement the standard, but compatibility should not be confused with bypass power. A compatible wallet can construct the right transaction, query eligibility information, surface warnings and help a user complete an authorized transfer. It cannot make a prohibited transfer valid.

This creates two practical requirements for wallet builders.

First, the wallet needs policy awareness. It should identify the token standard, retrieve the applicable rules and alert the sender before they pay fees for a transaction likely to fail. If a recipient must be verified, the interface should say so before the user signs.

Second, the wallet needs intelligible status reporting. A balance labelled only with a ticker and quantity is inadequate when the asset may be frozen, restricted or reassigned under its configured policy. The user needs to see whether an address is eligible, whether the asset is transferable to a given destination, and whether an administrator has exceptional powers.

For decentralized applications, the same problem becomes composability. A lending protocol, automated market maker or treasury tool cannot assume that a CIP-0113 token behaves like ADA. It must understand that the token’s transferability can be contingent.

Collateral is where the policy becomes financial risk

The sharpest test for a restricted token is not a simple payment. It is collateral.

A lender that accepts a tokenized fund share, bond or stablecoin as security needs to know whether it can liquidate the asset in a default. With a normal cryptoasset, the lender’s analysis focuses on custody, price volatility, market depth, smart contract risk and liquidation mechanics.

With a CIP-0113 asset, there is another category: policy enforceability risk.

Question for a lender Why it matters
Can the asset be frozen after deposit? The collateral may become non-transferable during liquidation.
Can it be forcibly reassigned? The lender could lose control despite holding the pledged tokens.
Must a buyer be approved? A liquidation auction may have too few eligible bidders.
Can rules change after deposit? Collateral quality can deteriorate without a market price move.
Can the issuer block redemption? Token value may diverge from the underlying claim.

A lending protocol should not treat such an asset as binary collateral, either accepted or rejected. It should assign a policy risk score. A token with no configured seizure function, immutable rules and broad recipient eligibility may deserve a different collateral factor from one controlled by a single administrator with update authority.

Centralized lenders can review legal agreements and negotiate issuer protections. Onchain lenders need those protections expressed in machine-readable terms. They may require pre-approved liquidation addresses, a dedicated custody structure, emergency substitution rights, or a rule that prevents policy changes while tokens are pledged.

The critical insight is that liquidity can disappear before price does. A token may retain a quoted valuation and still be poor collateral if a lender cannot legally or technically sell it to an eligible buyer when it matters.

A practical audit of a token’s control surface

Before accepting a CIP-0113 asset as payment, collateral or settlement inventory, a buyer should perform a control audit.

Start with the policy itself. Is the contract code and configuration publicly identifiable? Which rule modules are active? Are there whitelists, blacklists, jurisdictional filters, holding limits or transfer windows? Does the issuer’s configuration include freeze, seizure or reassignment authority, or does it use only recipient and transfer eligibility checks?

Then inspect authority. Which keys or entities can update rules, freeze balances, seize tokens or authorize recipients, if those powers are enabled? Are these powers controlled by one party, a multisignature group, a regulated trustee, or a governance process? Is there a time delay before a policy update takes effect?

Next, model failure modes. What happens if the issuer’s compliance provider is offline? Can valid transfers fail because an allowlist is stale? What happens when a wallet does not support the standard? Can the issuer act during a dispute, and how would a wrongly frozen holder recover access?

Finally, match the control profile to the use case. A tightly governed token may be excellent settlement inventory for a closed network of regulated institutions. It may be unacceptable as collateral in a permissionless lending market. It may work for a fund subscription, yet be a poor substitute for cash at a merchant checkout.

CIP-0113 is valuable because it makes these choices explicit in the transaction path rather than hiding them in terms of service. For Cardano, that can expand the design space for compliant financial products. For users, it replaces a simple ownership story with a more realistic one: the balance in a wallet is only part of the asset. The rules attached to that balance, including the optional powers its issuer has chosen to configure, may matter just as much.

#Cardano#CIP-0113#CoinDesk#ADA#Van Rossem hard fork

Jessica Jones 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-luna and gpt-5.6-terra. 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 Jessica Jones's usual length and in Jessica Jones'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.

Read and checked by admin on 11/19/2026

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.