The Cardano Foundation said on October 7 that CIP-0113 programmable tokens are live on Cardano mainnet, introducing issuer-configurable rules for token transfers, minting, and burning. Its announcement presents the launch as infrastructure for controlled tokenized assets. For issuers and users, the practical question is how those rules will work in the wallets and applications they use.
The accompanying implementation documentation describes integration work still needed across wallets, explorers, and decentralized exchanges. It also records a proposal awaiting merge. Those qualifications concern ecosystem support and formal documentation; they do not independently establish whether the announced code has been deployed.
What the token rules control
According to the Foundation’s implementation repository, programmable tokens use validation logic when assets are transferred, minted, or burned. In plain language, a transfer moves tokens, minting creates them, and burning removes them. The design puts checks at those operations, allowing an issuer to define conditions that must be satisfied when the token is used.
The Foundation says modular rules can include know-your-customer and anti-money-laundering checks, sanctions screening, transfer restrictions, and freeze or seize controls. That changes the question for a prospective holder: understanding the token includes understanding which issuer-defined conditions govern its movement and which controls may affect access to it.
These are the Foundation’s descriptions of technical capabilities. A rule that enforces a configured condition does not establish that the condition satisfies the law, that screening information is accurate, or that an issuer’s entire operation meets regulatory obligations. The announcement should therefore be read as a claim about configurable token controls, rather than a legal compliance guarantee.
The Foundation says the standard uses Cardano’s existing native-asset infrastructure and required no hard fork. The repository describes an Aiken on-chain implementation, with shared-script custody and stake-credential ownership forming part of the design. Those technical descriptions explain the proposed structure; they do not supply evidence of a particular live token’s behavior.
Mainnet announcement and proposal status are separate
When checked on October 8 KST, the repository README said CIP-0113 had been accepted by CIP editors but was awaiting merge. The linked CIP pull request #444 appeared open at that check. The retrieved README view did not show a publication or update timestamp.
That leaves two distinct records: the Foundation’s October 7 statement that programmable tokens are live on mainnet, and repository material showing a pending formal proposal merge. An open proposal is not proof that implementation code is absent from mainnet. Conversely, a launch announcement does not demonstrate that the formal proposal process is complete.
The difference may reflect separate release layers or documentation that has not caught up with the announcement. The reviewed evidence does not resolve which explanation applies. Keeping both records visible avoids turning either proposal status or a press release into a broader technical conclusion than it supports.
Integration and security remain practical checks
The repository says wallets, explorers, and decentralized exchanges require integration work to support programmable tokens. For an issuer considering the infrastructure, compatibility is therefore an operational requirement: the relevant services must support the token’s validation model. The research did not establish an inventory of compatible products, so this is not a finding that no wallet integrations exist.
The Foundation says multiple independent security audits were completed, and the repository says the code underwent professional audits. The repository also cautions that an audit does not guarantee production safety. Specific reports, audit scope, and residual findings were not reviewed for this article, so the audit statements cannot be treated as an independently assessed security result.
The next useful evidence would connect the announcement to observable use: a deployment address or transaction, a live issuer or token example, and named wallet, explorer, or exchange support. Updated proposal documentation would clarify the formal status. Until those details are established, the news is the Foundation’s announced mainnet availability, with adoption, compatibility, and deployment evidence remaining separate questions.
Sources
- Cardano Foundation mainnet announcement — dated October 7, 2026; publication hour not shown. Supports the attributed launch, rule capabilities, design, and audit statements.
- Cardano Foundation implementation repository — validation design, integration requirements, pending-merge note, and audit safety caveat.
- CIP pull request #444 — proposal appeared open in the October 8 research check.
Source check: October 8, 2026 KST. No independent on-chain deployment or live-token verification was established.
Investment disclaimer: This article is provided for general information only and does not constitute investment, financial, legal or tax advice. Digital assets are volatile, and all investment decisions and their consequences are your own responsibility.