Cardano Native Tokens just got a ticket onto the rails institutions already use.
The Cardano Foundation announced that Fireblocks will add full native support for CNTs.
It means hat banks, exchanges, payment firms, and fintechs on Fireblocks will be able to custody, send, and receive those tokens with the same policy controls they already use for everything else.
To be clear, it is more than an integration announcement.
Fireblocks is the institutional plumbing layer: MPC wallets, treasury ops, policy engines, and a transfer network that banks and fintechs sit on top of.
Clients include names like BNY, Revolut, Galaxy, and Worldpay.
If an exchange lists an asset, a bank issues a token, or a fintech moves stablecoins at scale, Fireblocks is often the system that actually signs and gates the transaction.
Until now, CNTs sat in a gray zone. ADA could move through Fireblocks. Tokens issued on the same chain needed extra manual steps or RAW-signing workarounds.
It was the kind of setup compliance teams quietly refused. Native support means CNTs become standard assets inside the existing console, not a special project.
For issuers, the practical meaning is simple: if you mint a stablecoin or a tokenized asset on Cardano, the desks that already run BTC, ETH, and USDC through Fireblocks can now treat your token as another line item, meaning same vaults, same approvals, same audit trail.
Long story short, this opens the doors to institutions for Cardano.
Cardano Native Tokens (CNTs) will be supported on
@FireblocksHQ.
That means every exchange, bank, and fintech using Fireblocks will be able to custody, send, and receive CNTs with the same policy controls they already use for every other asset.
Special thanks to
@emurgo_io and the Pentad as well as
@IagonOfficial for helping on this journey.