> For the complete documentation index, see [llms.txt](https://docs.projectcatalyst.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.projectcatalyst.io/open-funding/funding-basics/integration-guides/programmable-tokens-cip-0113.md). # Programmable tokens (CIP-0113) #### What it is CIP-0113 is a token standard with embedded logic: tokens that carry rules which can change after issuance. Think RWA tokenization with compliance logic (whitelist and blacklist rules an issuer can update), sanctions screening, or regulatory reporting built into the token itself. The design has two layers: a core standard (custody model, on-chain registry, global validation coordinator, issuance) plus pluggable "substandards" for token-specific rules. #### What you could build * Compliant RWA or tokenized-securities products with updatable transfer rules * Sanctions-screened transfer rails for regulated markets * Regulated stablecoin logic on top of a programmable-token base #### What the pilot expects Leveraging CIP-0113 means real compliance-governed token actions on mainnet: mints, transfers, and rule updates under your declared policy. Actions initiated from your own declared wallets never count (Standard §5.2), so design flows where third parties, not the issuer alone, generate the activity. Floors and target guidance for this category are in the Transaction Integrity Standard (§3.1, §3.3). #### Get building * [Programmable tokens; developers.cardano.org](https://developers.cardano.org/docs/developers/curriculum/native-tokens/programmable-tokens/#why-it-matters) * [CIP-0113 spec (CIPs PR #444)](https://github.com/cardano-foundation/CIPs/pull/444) * [cardano-foundation/cip113-programmable-tokens](https://github.com/cardano-foundation/cip113-programmable-tokens): reference on-chain validators (Aiken) with docs:[ introduction](https://github.com/cardano-foundation/cip113-programmable-tokens/blob/main/documentation/01-INTRODUCTION.md) ·[ developing substandards](https://github.com/cardano-foundation/cip113-programmable-tokens/blob/main/documentation/09-DEVELOPING-SUBSTANDARDS.md) * [cip113-programmable-tokens-platform](https://github.com/cardano-foundation/cip113-programmable-tokens-platform): end-to-end testnet environment * Community implementation:[ FluidTokens ft-cip-113](https://github.com/FluidTokens/ft-cip-113) * Background:[ CF blog explainer](https://cardanofoundation.org/blog/programmable-tokens-cardano) * [On-Chain Compliance: CIP-0113 KYC Standard & Implementation with Thomas Kammerlocher](https://www.youtube.com/watch?v=VVkPj7CSqzc) #### Readiness & constraints **You'd be building on a moving standard, so go in with open eyes**. The spec is still an open pull request (close to merge, but it may change before finalization). The reference implementation has been tested on the Preview testnet only, is not professionally audited, and describes itself as not production-ready. You can start development and adoption work on pre-production environments now; plan for the standard to evolve under you. The pilot's mainnet requirement still applies: your M1 plan should show how you get from pre-production to real mainnet transactions within the window, including how you handle the audit and risk gap. There are already a few substandards, if one of them fits your needs use them over writing a new one. Example of a substandard (in progress): . **A note on adoption and standard-level risk.** The adoption leg of this grant depends on CIP-0113 being viable on mainnet. If the standard itself proves not feasible to run on mainnet within the program window, through no fault of your team, the adoption part of the grant may be delayed or, where delivery is impossible, cancelled; the build payment is not affected. Raise any standard-level blocker with the program as soon as you see it, not at the deadline. **And an opportunity alongside the risk:** building on CIP-0113 now makes you an alpha user of the standard. You'll be exercising it against real requirements before most of the ecosystem touches it, which means you're better placed than anyone to find where it breaks. Separately from this pilot, a bug bounty program for CIP-0113 may be active during your build, run by the workstream that maintains the standard. Real bugs uncovered in the course of your own integration work may qualify for rewards there, under that program's own terms and on top of your grant. Watch the relevant channels for announcements, and report what you find either way.\
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.projectcatalyst.io/open-funding/funding-basics/integration-guides/programmable-tokens-cip-0113.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.