OFT Tokens on LayerZero Keep Supply Unified Across Chains
What is an OFT token on LayerZero? It burns tokens on one chain and mints them on another, keeping supply unified while shared decimals leave dust behind.
The Tareom Editors4 min read

An OFT token is a fungible token built on LayerZero’s Omnichain Fungible Token standard, which moves supply between chains by burning tokens on the source and minting them on the destination. The burn and mint keep the token’s total supply unified across its connected chains, without a liquidity pool or a wrapped copy for each route.
You might meet an OFT when moving assets into Berachain’s DeFi ecosystem. A Berachain bridge route can use an OFT to mint the arriving amount on Berachain without pool slippage; the linked page explains how assets move across chains into that ecosystem.
- Each chain has an endpoint ID, or EID, that identifies it as the destination.
- By default, sharedDecimals is 6, which affects the precision of transfers.
- USDT0 is built on the OFT standard.
OFT transfers burn on the source and mint on the destination
An OFT transfer burns tokens on the source chain and mints the corresponding amount on the destination. The total supply across the connected deployments stays constant, aside from any amount removed as dust by decimal conversion.
Say you hold an OFT on one chain and want it on another. You call send() with the destination EID and recipient address. The source OFT burns the transferable amount and sends a message through its LayerZero endpoint. The destination endpoint processes the message after verification, and an executor calls lzReceive on the destination OFT. That contract mints the amount to the recipient.
The endpoint ID tells the sending contract which chain should receive the message. It is a LayerZero identifier, not necessarily the chain’s familiar network ID. For a transfer to work, the source and destination deployments must also be linked: an owner sets the destination as a peer with setPeer. An unlinked deployment cannot receive messages from that source.
Amount precision matters because chains may use tokens with different local decimal counts. OFTs convert transfers to a shared decimal precision. The default sharedDecimals value is 6, so the transferable amount is rounded down to a multiple that can be represented at that precision. Any remainder below that unit is dust: it stays in your wallet and is not included in the burn or destination mint.
For instance, if the local token uses 18 decimals, a transfer can include only amounts aligned to the six shared decimal places. The destination receives the equal amount represented there; the tiny remainder stays on the source chain. So the amount credited can be slightly lower than the amount you entered, even though the OFT route itself does not use a pool to set a swap price.
An OFT Adapter locks an existing token instead of burning it
An OFT Adapter connects an existing ERC-20 to LayerZero by locking tokens on their home chain when they leave it. This differs from a native OFT, which burns its own token on the source chain. On the destination, the route creates or releases the corresponding representation; when tokens return home, the adapter unlocks the original ERC-20.
The distinction matters when you look at supply. A native OFT’s source balance falls because tokens are burned, while an adapter’s home-chain balance is held in custody. Both designs can move value between chains, but the adapter relies on the locked tokens and the contracts that control them. You should check which variant a project uses before assuming its transfer has the same supply and custody model as a native OFT.
Neither design makes the message route trustless by default. LayerZero’s Decentralized Verifier Networks, or DVNs, verify messages according to the route’s configuration. An executor handles delivery by calling the destination receiver. The selected DVNs, peer settings, contract permissions, and upgrade controls all affect the route’s security. An OFT can avoid pool slippage, but that does not remove bridge and contract risks.
Related
How is an OFT different from a wrapped token?
A wrapped token is usually a separate token backed by assets held elsewhere, often through a custodian or a bridge contract. An OFT route instead uses a linked burn-and-mint system, or an adapter that locks the original asset and coordinates its representation across chains. The difference you can observe is whether the destination asset is a wrapped copy backed by a pool of collateral, or part of a supply system managed by the OFT deployments.
Is an OFT token safe to hold?
An OFT’s safety depends on the token contract and its cross-chain setup. Check that the deployments are the project’s intended contracts, that peers are correctly linked, and which DVNs verify the route. Also consider whether the token uses an adapter, who controls upgrades, and whether a transfer’s shared-decimal rounding affects the amount you need. The standard describes how tokens and messages move; it does not guarantee every deployment’s configuration or security.