Libertum is now live on Cardano mainnet with CIP-113, on the Cardano Foundation’s canonical CIP-113 deployment. Issuers on T-Suite can tokenize real-world assets as programmable tokens whose compliance rules are checked by the Cardano ledger on every transfer, not only by an application in front of it.
Our live test token is the first token registered in the Cardano Foundation’s canonical CIP-113 registry on mainnet, the registry that explorers, wallets and other ecosystem services index. We took it through its full lifecycle there: deploy, buy, mint, freeze, unfreeze, seize and a NAV update. We also wrote an investor’s on-chain KYC record and then revoked it. Every step is a public transaction, listed in full below so you can check each one yourself.
Why this matters for issuers and institutions
On most chains, a “compliant token” is an ordinary token with a compliance check somewhere in a backend. If a transfer happens outside that backend, the check doesn’t run.
CIP-113 moves the rules to where the asset lives. A token’s transfer logic is registered on-chain against that token, and the ledger runs it on every transfer. A transfer to a wallet without a valid KYC record isn’t blocked by our app. The Cardano ledger refuses it.
For an issuer of tokenized securities, a fund or a stablecoin product, that is the difference between a policy and a guarantee.
The standard: CIP-113
Libertum is built on the audited CIP-113 v0.0.1 release.
- Programmable tokens sit at a shared programmable address, under each holder’s own stake key.
- Every transfer runs the token’s registered transfer logic, so the ledger enforces it.
- Each token gets its own minting policy, registry entry and on-chain state record.
- Tokens are registered in the Cardano Foundation’s canonical CIP-113 registry, the one explorers and wallets index.
- The canonical core is governed by the Cardano Foundation’s upgrade authority. Libertum holds no key.
CIP-113 is live on both Cardano mainnet and Cardano preview on the canonical deployment, so issuers can rehearse an offering on preview before taking it to mainnet.
The Libertum compliance layer
On top of the CIP-113 core, Libertum adds its own on-chain compliance modules. They are our own code (version 1.0.0-rc1). The audit covers the CIP-113 core release, and we describe our modules separately for that reason. Every transfer of a Libertum CIP-113 token is checked against:
- An on-chain KYC list, with claim topics, country and expiry, attested by a trusted issuer. Records can be revoked.
- Country allow and restrict lists per token
- Lock-up periods before tokens can move
- Pause, to halt all transfers of a token
- Supply caps and per-holder caps
- Full and partial freezes, so an issuer can freeze an amount rather than a whole position
Issuers also get the actions a regulated product needs: freeze, unfreeze, seize and forced transfer, through Libertum’s third-party module.
On preview, we confirmed the negative case as well: a transfer to a holder with no KYC record was refused by the ledger.
NAV, on-chain
When an issuer updates NAV in T-Suite, the update is anchored in Cardano transaction metadata under label 674. The record carries:
| Field | Value in the mainnet test |
|---|---|
| Tag | Libertum NAV |
| Token policy | b025efe5b44b43ed154419c66b0efc9cf148fd98f464e261018c89e8 |
| NAV (USD) | 1.2 |
| As of | 2026-10-05T12:50:08.329Z |
| SHA-256 of the NAV record | 7628b39858e8c57b5ee24bf058bc21cde9555a607626bb83932f6790602e7334 |
If the anchor can’t be written, the update is refused. The NAV investors see on the platform can never get ahead of the NAV on the chain.
Proven on mainnet: every transaction
On 5 October 2026 we ran a live test offering through T-Suite’s normal product flow on Cardano mainnet, on the Cardano Foundation’s canonical deployment. The three deploy transactions took about one minute, and the network fees from deploy to NAV update came to about 5 ADA.
| Step | What happened | Transaction |
|---|---|---|
| Deploy | On-chain state record created | 3e19b3b0…78a32a37 |
| Deploy | Minting logic registered | 366bfae9…a044f9e1 |
| Deploy | Registry entry in the Cardano Foundation’s canonical mainnet registry: token live, bound to Libertum’s transfer and issuer-action logic | 4e468a9d…6d80bb1e |
| KYC write | An issuer approves an investor’s KYC, and the record is written to the on-chain KYC list | f05d9761…4301c7b8 |
| KYC revoke | The issuer then rejects that investor, and the record is removed, so they can no longer receive the token | de148e81…9a522e80 |
| Buy → mint | Investor buys, the issuer accepts, tokens minted at settlement after a check against the investor’s on-chain KYC record | 26ec45ec…43cbc9c8 |
| Freeze | Holder’s position locked | 38293731…30d0434e |
| Unfreeze | Lock lifted | 22191a41…708c5b16 |
| Seize | Issuer moves the position to a destination wallet through Libertum’s third-party module | 95020f08…a9f3637b |
| NAV | NAV of $1.20 anchored on-chain | bf6e5876…732f8256 |
Each link opens the transaction on Cardanoscan.
Cardanoscan also recognises the token as a CIP-113 programmable token. Its token page decodes the registry entry, the transfer and issuer-action rules, and the canonical deployment the token runs on: view the token on Cardanoscan.
Deployed on Cardano mainnet
CIP-113 core: the Cardano Foundation’s canonical deployment
The canonical core was created on 2 October 2026 from the audited v0.0.1 commit (6b75ba32, Aiken 1.1.23). All eight scripts are verified on uplc.link.
| Component | Hash |
|---|---|
| Protocol genesis | bfefbd22…650cdb72 |
| Registry | 484e733d122af44e6101988bcc47ed261a7af5c43c797e89d60e3075 |
| Programmable logic base | d91d08e381f8ef95ffbb3f8048f020d7361ded8f3abfdf66c25fa838 |
| Programmable logic global | 46b61f0584f21481b22ea18f945e48ac4148f50fc3ade494a7762440 |
| Protocol parameters NFT | 3a511ec25af655c1aef31d0d9c0c6154eae7321045b1fa46fac55ecd |
| Upgrade authority | Cardano Foundation multisig, Libertum holds no key: 2ab871806b01d07fe7d93bf45ff4ce97bd156d168d7a08078ac8a517 |
Libertum compliance modules on the canonical core (1.0.0-rc1)
| Module | Hash |
|---|---|
| KYC list | b606e28851a2c863c5c06037173afe6438b1df1f5145be36b2d53c91 |
| Trusted-issuer list | 271a82d6321f6d10d70b4bfed7ccbe4715418d22743ba41b2520e905 |
| Transfer logic | 62b98b0894870aadfba1a7fd1b368c56aa91caa2701fb7e92a3f1bf1 |
| Issuer-action (third-party) logic | 1e17ac8b06f5f891d65923dee46e85a71e19deb401c8650e0401a3f0 |
| Logic stake registrations | 7096644d…d54fbea5 |
| Reference scripts | 77ed62cd…b5627415 |
Who this is for
- Issuers tokenizing real estate, private credit, funds, equity or other real-world assets who need transfer restrictions that hold at the protocol level
- Institutions evaluating tokenized securities and stablecoin products on Cardano
- Asset managers who need NAV that investors and auditors can verify on-chain
Cardano offerings on T-Suite settle in ADA, with USDC as the order currency. USDT is not offered on Cardano because Tether has no native issuance there.
Let’s talk
If you’re considering tokenizing real-world assets, tokenized securities or a stablecoin product, we’d like to hear what you’re building.
- Book a CIP-113 session
- Read about the CIP-113 standard at Libertum
- Explore Cardano RWA tokenization and stablecoin solutions
- Or email [email protected]
Libertum, S.A. de C.V. holds Digital Asset Service Provider licence PSAD-0094 from El Salvador’s Comisión Nacional de Activos Digitales (CNAD). The licence is Salvadoran and gives no authorisation in the European Union, the United Kingdom or the United States. Issuers using T-Suite remain responsible for obtaining their own permissions in the markets where they operate. Nothing in this post is an offer of securities or investment advice.