A centralized stablecoin issuer usually handles cross-chain minting in one of two ways, and many combine them. It can mint the stablecoin directly on each network against its reserves, so every deployment is issued natively. Or it can connect its deployments so that tokens burned on one network are minted on another, which moves supply between chains without changing the total. In both cases the issuer controls the token contracts and decides which networks it supports.
Last updated: September 28, 2026.
How does direct minting on each network work?
The issuer deploys its token contract on each network it supports. When a customer sends funds through the issuer's onboarding, the issuer mints the matching amount on the network the customer chooses. When a customer redeems, the tokens are burned on that network.
Each deployment is the issuer's own token, but the deployments are not linked. Moving value from one network to another usually means redeeming on one and minting on the other through the issuer, or trading through a venue that holds both.
How does burn and mint between networks work?
The issuer connects its deployments so that each contract accepts a mint instruction only from the other deployments it has been set to trust. A holder sends tokens to another network, the tokens are burned on the source chain, a cross-chain message reports the burn, and once the message is verified and delivered on the destination, the contract there mints the same amount.
The reserves do not move and the total supply does not change. Only the split of supply between networks changes. LayerZero's OFT standard is one implementation of this model. With it, the issuer as the contract owner configures which verifiers check its messages and which executor delivers them, and keeps control of its token contracts.
| Approach | How supply reaches a network | Moving between networks | Who issues the token on that network |
|---|---|---|---|
| Direct minting on each network | The issuer mints against reserves | Redeem on one and mint on another | The issuer |
| Issuer burn and mint | Supply moves from another deployment | Burn on source, mint on destination | The issuer |
| Third-party wrapped version | A bridge locks tokens and mints a version | Through the bridge | The bridge |
What about bridged versions?
A stablecoin can also appear on a network the issuer does not support, through a third-party bridge. The bridge locks the issuer's tokens on one chain and mints its own version on another. That version is not issued by the stablecoin issuer, and whether and how it can be redeemed depends on the bridge.
The same symbol on two networks can therefore mean different assets, and native vs bridged tokens explains how to tell them apart.
What happens to total supply?
With direct minting, total supply rises and falls as customers subscribe and redeem. With burn and mint, a transfer between networks leaves total supply unchanged, because every mint on one network matches a burn on another. With a bridged version, the wrapped tokens are backed by the issuer's locked tokens, so counting both would count the same supply twice.
Multi-chain stablecoin operations covers what running a stablecoin across networks involves for the issuer.
FAQ
Can an issuer add a new network later?
Yes. It deploys its contract on the new network and, in a burn-and-mint setup, connects it to the existing deployments. Stablecoin chain support covers what native support on a network means.
Does a holder see burn and mint happening?
Usually not directly. The holder sends tokens to another network and receives the same token there, while the burn and mint happen in the contracts.
Does burn and mint move the reserves?
No. The reserves stay where the issuer holds them. Only the amount of tokens on each network changes.
Plan the stablecoin's networks
For a stablecoin and the networks its holders need, request a custom briefing.