What happened.

A [merged repository commit](https://github.com/cardano-foundation/CIPs/commit/e759a4a56c03c87175f3561b136283398fefccfe) dated September 29 adds CIP-0113, a specification for programmable token-like assets. The proposal began as a 2023 draft called “meta-assets (ERC20-like assets)” and was rewritten during PR #444.

Its history shows an “Admin” role generalized into a third party that can transfer or seize tokens. The spec also gained wallet-integration and DeFi sections. The final change updated its preamble to pass the repository’s newer header validator.

Why it matters.

The document gives builders common transfer, redeemer and datum definitions to review. For a token built to this spec, the third-party role makes the token’s particular setup consequential: it may allow someone other than the holder to move or seize balances.

The history also corrects the description of ThirdPartyTransferAct indexing. It says input_idxs are relative to all script inputs, and corrects the input and output pairing description. Builders using an earlier draft have a specific change to check.

What remains open.

This commit adds a document, not a ledger change or mainnet deployment. The cited implementation is a proof of concept. The commit title still includes a question mark after “CIP-0113,” and the supplied record states neither the CIP’s status nor adoption by a wallet, DEX or issuer.

What to watch

Watch for a stated CIP status and a named implementation that shows how third-party transfers and seizure are configured.

Sources and limits

Upstream references and independent checks

Digest dated 2026-09-30 · upstream model sonnet. Direct links are matched to all 1 upstream source IDs.

  1. 1
    CIP-0113? | Programmable token-like assets (#444)Direct upstream source · 62b32a4817449db803f79cb8147e61a3e0dee4c1

This Research brief was generated by GPT-6 Sol from a dated upstream research digest. It has not received the source-by-source human review required for Reviewed analysis. Material limit: The material limit is that one repository commit supports the spec’s arrival, but the supplied record shows no production deployment or named adopter.