How do bridges handle token standards that don't match across chains?
When you bridge a token from one chain to another, the receiving chain almost never supports the exact same token standard as the source. Bridges handle this mismatch by either wrapping the token into a standard the destination chain understands, or by minting a version of the token that conforms to the destination's native standard. The exact method depends on the bridge architecture and the specific token standards involved.
Why token standards differ between chains
Each blockchain defines its own token interface. Ethereum and its EVM-compatible chains use ERC-20 for fungible tokens. Solana uses SPL Token. Bitcoin uses UTXOs with no native token standard at all. Even within EVM chains, standards like ERC-721 (NFTs) and ERC-1155 (multi-token) don't map cleanly to non-EVM chains.
A bridge cannot simply copy a token's bytecode across chains because the virtual machines are incompatible. The bridge must produce a token on the destination that preserves the original's value and, ideally, its functionality.
The two main approaches: wrapping and native minting
Wrapping (Lock and Mint)
This is the most common method. The bridge locks your original token on the source chain and mints a wrapped version on the destination chain. The wrapped token is a new contract that implements the destination chain's standard. For example:
- You bridge USDC from Ethereum to Solana.
- The bridge locks your ERC-20 USDC in a contract on Ethereum.
- It mints a Solana SPL Token version of USDC (often called "wormhole USDC" or "portal USDC").
- The wrapped token can be used, traded, or bridged again.
The wrapped token's value is backed 1:1 by the locked original. Anyone can burn the wrapped token on the destination to unlock the original on the source - that is the reverse bridge process.
Native Minting (Burn and Mint)
Some bridges work directly with the token issuer. The issuer gives the bridge permission to burn tokens on one chain and mint native tokens on another. No wrapping occurs. The destination token is the issuer's official contract, not a bridge-specific wrapper.
Example: Circle's official USDC on Avalanche is a native mint, not a wrapped version. The bridge (or a cross-chain messaging protocol) tells Circle's contract to mint or burn USDC as needed.
Native minting avoids the liquidity fragmentation problem of wrapped tokens. You don't end up with "USDC" and "Wormhole USDC" competing on the same chain. But it requires the token issuer to trust and actively manage the bridge.
Handling non-fungible tokens (nfts)
NFTs are trickier because each token is unique. A bridge must preserve the metadata and ownership across chains.
- EVM to EVM: The bridge locks the ERC-721 on the source and mints a wrapped ERC-721 on the destination. Metadata (image URL, attributes) is usually copied to a new contract, but the original contract's metadata source may not be accessible on the new chain. Some bridges store a hash of the metadata on-chain to verify authenticity.
- EVM to non-EVM (e.g., Solana): The bridge creates a Solana Metaplex NFT that mirrors the original ERC-721. The metadata is embedded in the Solana NFT's off-chain JSON, pointed to by an on-chain URI. Ownership history is typically lost.
- Non-EVM to EVM: The reverse - the bridge mints an ERC-721 with metadata pulled from the source chain's format. This often requires manual mapping of metadata fields.
What happens when the standards are fundamentally incompatible?
Some standards have features that the destination chain cannot replicate. For example:
- Fee-on-transfer tokens: These deduct a fee on every transfer. An EVM bridge can detect this behavior and lock the full amount, but on a chain without fee-on-transfer logic (like Solana), the wrapped token cannot charge fees. The bridge either ignores the fee mechanism (losing it in the process) or refuses to bridge the token.
- Rebasing tokens (e.g., stETH): These automatically adjust supply based on interest. A bridge can only lock the static balance. The wrapped version on the destination will not rebase. Users get a static representation that does not accrue value.
- Governance tokens with voting power: Bridged versions usually carry no voting rights. The voting power stays with the locked tokens on the source chain. Some bridges offer "cross-chain governance" wrappers, but these are rare and complex.
In all these cases, the bridge documents the limitations. You should read the bridge's documentation for any token you plan to bridge, especially if it has unusual mechanics.
How to check what you are getting
Before you confirm a bridge transaction:
- Look up the destination token contract address on the bridge's interface or block explorer. The bridge should show the exact contract it will mint.
- Check the token's name and symbol on a block explorer like Etherscan or Solscan. Wrapped tokens often include the bridge name (e.g., "Wormhole Wrapped USDC").
- Verify the token's total supply against the source chain's locked amount. If the wrapped supply exceeds the locked amount, the bridge is insolvent - do not use it.
- If the token claims to be a native mint, confirm on the token issuer's official site. Circle publishes a list of native USDC chains and contracts.
Practical Advice
- Prefer native mints when available. They avoid liquidity fragmentation and are usually more widely accepted by apps.
- If you must use a wrapped token, understand that you may need to swap it back to the native version later. Check whether the destination chain has a liquid market for the wrapped token.
- For NFTs, expect metadata and provenance to degrade across chains. A bridged NFT is rarely identical to the original in terms of marketplace recognition.
- Never assume a token works the same on the destination chain. Test with a small amount first.
Bridges do not magically translate token standards. They produce a close approximation that works within the destination chain's constraints. The approximation is good enough for most use cases, but the differences matter.
Not financial advice. basedbratt.xyz publishes market data and general information about digital assets. Crypto assets are volatile and you can lose everything you put in. Nothing here is a recommendation to buy, sell or hold, and we make no price predictions.
Prices are sourced from third parties and may be delayed or wrong. Verify anything you intend to act on against a primary source.