Universal Bridge works only with an asset, network, and receiving wallet that its live quote supports; it will not accept arbitrary deposits, unlisted token contracts, exchange accounts as wallets, or recovery phrases.
Universal Bridge accepts a quoted route, not an arbitrary deposit
Universal Bridge accepts a quoted route, not an arbitrary deposit.
That distinction saves time and prevents the usual cross-chain mistake: treating a bridge like a wallet address. A bridge route is a specific instruction set—input token, source network, amount, recipient, and output asset. Change one element and the route may no longer exist.
Bridges do not move coins in the way a bank wire moves cash. Depending on the design, they lock and mint, burn and mint, or settle an atomic swap; each model has different limits, fees, and settlement assumptions. Ethereum’s bridge documentation sets out those three common mechanisms.
| Input | What must be true | What it will not take |
|---|---|---|
| Asset | The exact token must appear in the route or produce a quote. | A random ERC-20 contract, NFT, or token sent directly to a contract address. |
| Network | The source chain and destination chain must both be selectable for that route. | An unsupported chain, or an address copied from the wrong network without checking it can receive the output. |
| Wallet | The wallet must control the sending address and sign on the selected source chain. | An exchange login, a custodial balance, a seed phrase, or a private key entered into a website. |
For assets, the useful unit is the displayed token and its contract—not its ticker alone. Universal Protocol documentation describes more than 80 wrapped uAssets, including uBTC, uETH, uSOL, uXRP, and uDOGE. Its published uAsset list is a better starting point than assuming every familiar ticker has a route.
For networks, use the route picker as the final authority. The protocol’s published FAQ names Base, Polygon, Arbitrum, Solana, and World as supported networks, while describing Katana as forthcoming. That current network statement is useful context, but a live quote decides whether a particular asset pair is available now.
For wallets, an EVM route needs a wallet that can expose an EIP-1193 provider —the standard interface through which a web application requests accounts, network changes, and transaction signatures. MetaMask, Rabby, Coinbase Wallet, and a hardware wallet used through a compatible browser wallet are examples of wallet setups, not a promise that every connector is enabled in every interface.
Universal Bridge output is the quoted asset at the quoted address
Universal Bridge output is the quoted asset at the quoted address.
The expected result is not simply “the same coin on another chain.” It is the asset name, token contract, network, estimated amount, and receiving address shown before signing. If the output says uSOL on Base, the wallet should receive uSOL on Base—not native SOL on Solana. That is the shortest way to read a route correctly.
A wrapped token is a token on one network that represents an asset from another network. The original asset is held or otherwise accounted for under the protocol’s design while an equivalent representation is issued for use on the destination chain. A wrapped version can be useful in DeFi, but it is not interchangeable with the native asset outside the network and redemption path named by the protocol.
This is why native BTC, native SOL, XRP Ledger XRP, and their onchain representations should never be conflated. A route can provide exposure to an asset without delivering the original asset on its home network. Readers who need the native asset should choose an output explicitly labelled native and a receiving address on that native network.
Fees also change the output. The wallet pays network gas for the source-chain transaction, while the route may include a bridge, swap, relayer, liquidity, or spread component. Bridges commonly price fees according to gas costs and route liquidity. Ethereum’s bridge overview explains why tokens cannot move freely between isolated chains and why the destination route matters as much as the source asset.
Use the live quote before making a transfer
-
Connect the self-custody wallet that holds the source asset on the source network.
-
Open the Universal Bridge quote screen and check the available asset, network, output token, expected amount, fees, and recipient address.
-
Keep enough of the source network’s native gas token to approve and submit the transaction.
-
Enter the amount and compare the minimum received with the amount needed at the destination.
-
Confirm the token contract, selected chain, and receiving address in the wallet before signing.
-
Wait for the submitted transaction and destination settlement to complete before using the output.
The default I always change, when it is offered, is an unlimited ERC-20 approval; the exact trade amount is enough, while leaving a broad allowance lets the approved contract spend more of that token later.
When the route stops working, the fastest response is to stop
A missing quote is information, not a prompt to improvise. It usually means the input token, amount, chain, or destination combination is unsupported at that moment. Do not send the asset manually to a router, relayer, merchant, or token contract in an attempt to force the route.
Very small amounts can fail the practical test even if a token is listed: gas and route fees can consume most of the value. Fee-on-transfer tokens, rebasing assets, non-fungible tokens, and tokens with unusual transfer hooks also require explicit support. If the route does not name them, assume they are excluded.
Wallet mismatch is another hard stop. An exchange can send a withdrawal, but it cannot act as the connected wallet that approves and signs an onchain route. Withdraw to a self-custody address first, verify the network, then connect the wallet that controls that address.
Finally, do not use a destination address merely because its characters look valid. Ethereum-style addresses can have the same format across EVM networks, while the asset and application support behind them differ. The route must identify both the network and the output token before the transaction is signed.
FAQ: the remaining compatibility questions
Can any token be used with Universal Bridge?
No. Only a token, chain, and amount that produce a live route are eligible.
Can an exchange account be connected as the wallet?
No. A connected wallet must control the address and sign the transaction; an exchange balance cannot do that.
Will a uAsset arrive as the native coin?
Not unless the route explicitly says the output is native on that chain. A uAsset is a wrapped onchain representation.
Is a seed phrase ever required?
No. A legitimate wallet connection asks for a signature or transaction confirmation, never a recovery phrase or private key.
What should happen if the desired route is not shown?
Stop and use another supported route or platform. Manual deposits do not create compatibility.