CIP-0113 lets issuers of regulated Cardano tokens—such as stablecoins, funds or bonds—make transfers conditional on programmable rules. Those rules can support identity and compliance checks, restrict eligible recipients or transfers, and, when built into that token’s implementation, freeze or seize assets; an authorized party may even be able to move tokens without the holder’s consent. (CIP-0113; Cardano Foundation; CoinDesk)

CardanoOct 7, 2026, 06:36 UTC

These are controls for tokens that adopt the standard, not powers that apply to every Cardano asset. The CIP says users and integrators must inspect a token’s specific rules and trigger authority; conformance alone does not establish that every token supports seizure or issuer control. (CIP-0113)

Ask your own

Case file

Cardano

Answered Oct 7, 2026, 06:36 UTC

Sources 3

CIP-0113cips.cardano.org
Cardano Foundationx.com
CoinDeskcoindesk.com

Research trace 17

Latest posts of @Cardano
The page leviathannews.xyz
The page leviathan.news
The page cardanofoundation.org
The supplied CoinDesk report says CIP-0113 embeds identity checks and transfer controls, and may let authorized parties move assets without the holder’s consent. I’m checking the proposal itself and Cardano Foundation’s announcement to pin down the issuer powers and their limits.
The CIP text and CoinDesk report describe programmable transfer rules and possible issuer-directed seizure; I’m checking the Foundation’s announcement for the concrete controls and scope it attributes to the standard.
The official CIP text and Foundation announcement already establish that CIP-0113 makes token transfers programmable and that it is live on mainnet. I’m checking the specification’s rule categories to distinguish what issuers can enforce from powers that depend on a token’s chosen implementation.
The CIP text defines programmable ownership changes and warns that powers depend on each token’s substandard. I’m retrieving the exact rule and authorization details before summarizing what issuers can configure.
The CIP and Cardano Foundation announcement establish that programmable transfer rules are live, while CoinDesk reports controls such as identity checks and issuer-directed seizure. I’m checking the CIP’s current detailed specification for the available rule types and the limits on those powers.
The CIP page is returning clipped detail, so this step seeks a readable copy of its rule categories and the Foundation’s explanation of what issuers can enforce.
The retrieved CIP page is clipped, but its readable text confirms that ownership changes can be gated by scripts and that extra powers depend on the token’s substandard. CoinDesk and the Foundation identify the practical controls, so I’m checking the full article and current CIP text via a second route for the rule examples and limits.
The CIP’s readable summary and Cardano Foundation’s announcement establish that issuers can encode compliance checks, but the exact controls depend on each token’s implementation. This step checks the cited standard and announcement for the scope and limits of those controls.
The official announcement confirms programmable compliance rules are live, while the CIP page’s clipped text leaves its rule details unclear. I’m checking the standard’s primary source and related technical materials for what the issuer can encode and what remains token-specific.
The official announcement and CoinDesk report establish that CIP-0113 makes token transfers programmable and can support compliance checks, restrictions, freezes, and seizure. The remaining useful distinction is which controls are available in the standard and which depend on a token’s specific rules.
The official CIP page has repeatedly returned clipped text, so I’m looking for an independently readable copy of the specification’s rule types and its caveat about issuer authority. That distinction matters because the question asks what issuers can do, while the standard says powers can vary by token implementation.
The CIP page has repeatedly clipped its detailed rule list, while the official announcement confirms only that compliance rules can be built into regulated tokens. I’m checking the proposal’s source file and Cardano Foundation’s announcement for the specific controls and how their use depends on each token’s implementation.
The supplied CoinDesk report, Cardano Foundation announcement and CIP-0113 specification establish that the standard supports programmable transfer rules, including compliance controls and possible freeze or seizure powers. The key qualification is that each token’s implementation determines which powers are enabled and who can trigger them.