Metis
Metis bridging routes differ in supported tokens, transfer costs and delivery conditions.
Metis bridging moves supported tokens into Andromeda through its canonical Ethereum bridge or an available third-party route. The suitable choice depends on the destination token, starting network, total costs and withdrawal conditions. An app may accept only a particular token contract, so the asset that arrives matters.
Canonical Backing and Token Representation
The canonical bridge links Ethereum and Andromeda by locking supported assets on Ethereum and crediting their mapped forms on layer 2. That backing relationship explains why the destination token can have a different contract and symbol. Returning through the canonical route reverses the relationship. The bridge burns the corresponding layer 2 tokens and releases the underlying Ethereum assets after withdrawal requirements are met.
USDC deposits produce m.USDC, while USDT deposits produce m.USDT on Andromeda. Ethereum ETH deposits produce WETH there; WETH does not replace METIS as the destination network's gas token. Each mapping connects a specific Ethereum asset to a specific destination token contract. An app that accepts one contract need not accept another representation with a similar name.
Third-Party Liquidity and Message Routes
Third-party routes can use liquidity pools or separate cross-chain message systems, so their availability follows the selected bridge's rules. A liquidity-based route releases assets from a destination pool against funds supplied on the source network. This can shorten the delivery wait when liquidity is available. Its fee or exchange rate can change with pool balances. The supported token pairs limit which transfers the route can serve.
Message-based token transfers depend on the issuing project's contracts and the services that verify and execute messages. The replacement LayerZero V2 infrastructure requires enabled application pathways with matching source send and destination receive settings. Returning assets also requires the reverse pathway to be enabled and configured. Support for a chain alone does not make every token transferable. The token's issuing project controls which integrations it enables. A route's speed also says little about its contract permissions or upgrade controls.
October 2026 Bridge Service Changes
Stargate support for Andromeda is scheduled to end on October 23, 2026, covering its V1 and V2 integrations. Liquidity providers need to unstake any staked pool tokens before withdrawing the underlying liquidity by that date. Withdrawals depend on available liquidity. Leaving funds in those pools past the cutoff can make withdrawal through the normal interface difficult or impossible.
LayerZero Labs' default decentralized verifier network and executor stop serving Andromeda on October 30, 2026. Replacement V2 infrastructure covers pathways between Andromeda and Ethereum, BNB Chain or GOAT Network. Applications must have those pathways enabled and update their send and receive configurations. Other pathways fall outside that replacement infrastructure's coverage. LayerZero V1 integrations cannot use that V2 configuration.
Canonical m.USDC, m.USDT, WETH and METIS balances on Andromeda are unaffected by these changes. Holding those tokens in a wallet creates no deadline to move them because of the Stargate sunset.
Which Costs Change a Bridge Quote?
A bridge quote changes with the selected network, asset, transfer amount and route, while wallet gas estimates depend on the proposed transaction and current network fees. Ethereum gas pays for source-chain execution, including any approval transaction that the token requires. The canonical bridge also accounts for cross-chain execution costs; user withdrawals require the configured minimum relaying fee and revert if the supplied fee is too low. For an ETH deposit, the canonical bridge deducts its cross-chain execution fee from the ETH sent. Successful finalization credits the remainder as WETH.
Liquidity routes can deduct fees from the transferred token or adjust the exchange rate that determines destination output. The displayed amount to receive therefore needs its own unit and token identity. A gas estimate in ETH cannot be subtracted directly from a quote expressed in another asset. Comparing both costs in money terms also requires a conversion price, which changes independently of bridge mechanics.
An extra network hop adds its own transactions and potentially another route fee. Low destination gas does not establish a low total transfer cost. Retain any approval cost, relay charge and final claim cost that the selected route actually requires when comparing its complete quote.
Destination Gas and App Compatibility
A delivered token becomes usable in an app only when its network and contract match the app's accepted assets. METIS pays native transaction fees on Andromeda. A WETH or stablecoin balance does not supply that native gas balance automatically. Receiving a transfer and initiating an app transaction impose different requirements. The bridge performs delivery, while the account pays for its own subsequent transactions.
The token contract that an app accepts determines whether bridging alone completes the funding task. A different representation may require a supported swap before the app can use it, adding cost and liquidity dependence. Bridging also does not create a sequencer staking position. Sequencer staking uses its own locking contracts and eligibility requirements, separate from a wallet's bridged balance.
Why Can a Canonical Withdrawal Take Longer Than a Deposit?
A canonical withdrawal can take longer because Ethereum delivery requires an eligible layer 2 state commitment and a valid withdrawal message. Deposits travel from Ethereum into layer 2 processing; withdrawals must satisfy the return path's settlement requirements. The withdrawal verifier checks whether the relevant state commitment lies outside its configured challenge window. A state dispute can also block affected withdrawal messages. Eligibility relates to the state batch behind the withdrawal, beyond the time needed to sign a transaction.
Settlement eligibility and actual delivery are separate states. A route can require further message execution after its waiting condition ends. Its completion estimate must account for settlement processing as well as the destination transaction. Different bridges can handle relaying or final claims differently, so a timing estimate for one route cannot establish another's duration.
Transfer Records and Delivery States
A source transaction receipt establishes what executed on the starting network. Token approval grants spending permission; a deposit transaction actually enters the bridge flow. For the canonical route, an initiation event records the recipient and amount; an ERC-20 deposit event also records the token pair. It does not establish that the corresponding destination credit has happened.
The canonical deposit flow distinguishes DepositFinalized from DepositFailed. A mined destination transaction can therefore represent unsuccessful deposit handling. Successful delivery requires the finalization event and the intended recipient's token credit.
Transfer amounts belong to specific stages. An input amount, quoted output and credited balance change describe different stages and may differ, especially on routes with deductions or conversion. Existing wallet holdings also make the final total balance different from the amount just delivered.
A pending delivery, a failed source transaction and a completed transfer hidden by the wallet require different responses. Track the existing transfer through its relevant network records before submitting another deposit. A retry or refund depends on the bridge's actual failure state and supported recovery mechanism.
A Canonical Deposit Hidden by the Wallet's Network View
In this hypothetical case, a reader wants to use a supported token in a Metis app. A canonical deposit has confirmed on the source network, but the wallet still displays that network. The quote covers the chosen token, amount and route; network execution determines the separate gas charge.
The reader checks the same recipient on the destination network without submitting another deposit. Displaying the mapped token using its destination contract reveals the credited balance in this case. The destination record also shows DepositFinalized for the requested recipient and transfer amount.
The existing transfer has delivered its token, so no repeat deposit is needed. App use still requires the matching token contract and native gas. Switching the wallet display adds no network transaction fee. If no matching credit exists on the destination network, that display change cannot establish delivery; the original transfer remains the item to investigate.
Contract Recipients and Bridge Controls
Recipient control affects whether a successful bridge delivery becomes usable funds. Ethereum accounts controlled by a private key can use the same address on compatible networks. Each chain records its balances separately. Contract wallets need their own destination deployment and receiving capability. An address with the right format does not establish that its controller or contract can use the asset on Andromeda.
Bridge custody and message permissions also affect route choice. The canonical bridge holds backing assets and relies on its bridge and messaging contracts. Third-party routes add their own pools, verifiers or token adapters, depending on the design. Administrative powers to pause messages or upgrade contracts affect availability and trust assumptions. If an app changes its accepted token contract, a previously suitable route may no longer supply usable funds.
Quick answers about Metis
Is METIS on Another Chain Affected by the October 2026 Changes?
METIS bridged out through LayerZero V1 is subject to the October 23, 2026 return deadline. The same deadline applies to the V1 bridged versions of HERA, QI and MTVT. Holders need to use the route that carried those assets out to return them before that date. Those V1 routes are no longer supported afterward. This requirement does not apply merely because someone holds native METIS on Andromeda.
Can I Bridge Directly to an Exchange Deposit Address?
A bridge can use an exchange deposit address only when the exchange accepts the destination network, token contract and delivery method. Support for trading METIS alone does not establish deposit support on Andromeda. An on-chain credit and an exchange account credit are separate outcomes. The exchange's receiving rules determine whether it recognizes the bridged deposit.
Is Gas Charged When a Metis Bridge Transaction Fails?
A bridge transaction that executes and reverts still consumes gas on the network where it runs. Ethereum fees use ETH; Andromeda uses METIS. A transaction rejected before inclusion is different, with no on-chain computation. Pending cross-chain delivery after successful execution is also a separate state.
Does Closing the Bridge Tab Cancel My Transfer?
Closing the bridge tab does not cancel a transaction already submitted to the blockchain. The interface displays progress, while network contracts process the transfer independently. Closing the tab also does not complete a remaining claim or relay action. Keep the transaction identifier so the existing transfer can be located again.
How Long Does a Token Approval for Bridging Remain Active?
An ERC-20 approval authorizes the selected spender up to its remaining allowance until that permission is consumed or changed, and the standard does not give every allowance a universal expiry time. Disconnecting a wallet does not revoke that permission. A completed bridge transfer can leave an unused allowance available to the same spender.