What do you hold in an OFT token or bridge-wrapped copy?
Omnichain token vs wrapped bridged token difference: an OFT burns and mints the issuer’s token; a wrapped token is backed by originals locked in a bridge vault.
2 min read

An omnichain token is the issuer’s token on each supported chain; a wrapped bridged token is a bridge-issued copy backed by originals locked elsewhere.
Say you send a LayerZero OFT from Ethereum to BNB Chain. The OFT standard burns the token on Ethereum, then the issuer’s contract mints it on BNB Chain. The token in your destination wallet is the issuer’s token, issued on that chain.
With cBridge xAsset, the Ethereum original stays locked and BNB Chain receives a pegged version. The cbridge tokens are a useful reference for the assets involved; cBridge xAsset uses this wrapped model.
What does the holder own?
An OFT holder owns the issuer’s token on the destination chain, while an xAsset holder owns a pegged token whose backing is held on the source chain.
- OFT: the source token is burned and the issuer mints the destination token.
- xAsset: the original is locked and a pegged token is minted on the destination.
Both routes put a token in your destination wallet, but the path determines what supports it. In the OFT case, the issuer’s contracts coordinate the supply across chains. In the wrapped case, the locked original backs the destination copy.
Where does the risk sit?
Wrapped-token risk is concentrated in the vault holding the original. If that vault is drained, the wrapped copies it backs lose their backing at once, even if those copies remain visible in wallets on destination chains.
That makes the vault part of what you are relying on when you hold a wrapped token. The token’s value depends on the original still being available to support it; a pegged label alone does not provide that backing.
OFT risk sits with the issuer’s setup: the contracts and process that burn tokens on one chain and mint them on another. The holder relies on that setup to issue the same token across supported networks. The arrangement avoids a bridge vault backing the destination copy, but it does not remove reliance on the issuer.
Before bridging, check whether the destination token is the issuer’s OFT or a bridge-wrapped copy, then consider whether you’re comfortable relying on the issuer’s setup or the bridge vault.