> For the complete documentation index, see [llms.txt](https://crypto-glossary-hub.gitbook.io/crypto-glossary-hub-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://crypto-glossary-hub.gitbook.io/crypto-glossary-hub-docs/mantle-bridge-move-assets-with-fewer-steps.md). # Mantle Bridge: Move Assets With Fewer Steps A Mantle bridge moves supported assets between Mantle and another blockchain. The fewest steps come from choosing a route that delivers the token you need on the destination chain, with enough MNT to pay for your next Mantle transaction. If you also need to change tokens, compare a bridge-and-swap route with bridging first and swapping afterward. ### What Does a Mantle bridge Move? It transfers value between chains so you can use it in the destination network’s apps. On a canonical Ethereum-to-Mantle deposit, the asset is held on Ethereum and a mapped representation becomes available on Mantle. A bridge does not automatically turn ETH into MNT or USDC into another token; that takes a swap. Check the destination asset by its network and token contract, not its ticker alone. Two tokens labelled USDC can have different issuers or bridge mappings, and an app may accept only one of them. Before transferring, identify the token the destination app accepts and make sure the route delivers that version. Mantle uses MNT for gas, including approvals, swaps and withdrawals. Receiving ETH or USDC on Mantle does not by itself fund those transactions. Arrange a small native MNT balance before you need to use the bridged asset; keep enough for more than one transaction if you expect to trade and later exit. ### Which Route Fits Your Source Chain? Use a canonical bridge when its supported Ethereum-to-Mantle asset is already the asset you want to hold. It follows Mantle’s settlement path and generally keeps the transfer separate from any trade. If your funds start on another chain, or you want a different token on arrival, compare cross-chain routes that include a swap. A Mantle Network bridge route from another chain may use liquidity already available near the destination, then settle the transfer behind the scenes. That can avoid sending funds through Ethereum yourself, but its quote depends on available liquidity and may include a provider fee or exchange-rate spread. Check the receiving token and estimated completion time for each route, especially when speed matters more than preserving the same token. Say you hold USDC on another layer-2 network and need USDC for a Mantle app. A direct route that delivers the accepted USDC version can save an intermediate Ethereum transfer. If instead you hold ETH and need USDC on Mantle, compare a combined transfer and swap with the cost of bridging ETH and trading it after arrival; count the extra Mantle transaction and its MNT gas. ### How Do You Bridge to Mantle? Start by specifying the source chain, Mantle as the destination, the asset you have, and the asset you want to receive. Use a wallet that can sign on the source chain and an address you control on Mantle. An EVM wallet such as MetaMask can use the same address across Ethereum and Mantle, but you still need to select the correct network to see and spend the arriving balance. Next, inspect the route before signing: source amount, destination token, minimum amount received, estimated time and every transaction you must make. To swap to Mantle in the same flow, pay particular attention to the minimum received; it accounts for price movement within the route’s slippage allowance. A quoted amount is an estimate until the transfer completes. If you send an ERC-20 token, you may first sign an approval that lets the route’s contract spend a specified amount. Approval alone does not bridge anything. Confirm the transfer transaction separately, retain its hash, and check that it succeeds on the source chain before looking for the destination transfer. Finally, check the destination chain’s explorer or your wallet on Mantle. If a confirmed transfer is absent from the wallet display, check the receiving address and token contract before assuming it failed; wallets do not always show a bridged token automatically. Do not send the result to an exchange deposit address unless that exchange explicitly accepts that token on Mantle. ### What Will It Cost, and How Long Will It Take? Count source-chain gas, any bridge or liquidity fee, swap spread or price impact, and the gas needed after arrival. Ethereum transactions use ETH for gas; Mantle transactions use MNT. Fees and available routes change with network congestion, liquidity and transfer size, so compare the amount you can actually use at the destination. A Mantle bridge quote can look cheaper until source gas is included. For example, on a $1,000 transfer, a route delivering 994 USDC after route fees with $2 of source gas leaves about $992 in value. Another delivering 997 USDC but requiring $8 of source gas leaves about $989. Those figures are illustrative; use live quotes for the transfer you intend to make. For the canonical bridge, Mantle’s bridge FAQ gives around two minutes as the typical time to initiate a deposit, while an Ethereum withdrawal can take up to 12 hours because it must pass the network’s settlement process. Allow extra time for source-chain inclusion and confirmation. A liquidity route may arrive sooner on an exit, but compare its fee and available depth against the time saved. ### How Do You Exit and Confirm the Result? To leave Mantle, first choose the destination chain and the token you need there. On a canonical withdrawal to Ethereum, you initiate the exit on Mantle with MNT for gas, wait until the withdrawal is ready to claim, then use ETH for the Ethereum claim transaction. Starting the withdrawal does not immediately place the asset in your Ethereum wallet. If you need funds on another chain promptly, compare a quoted cross-chain exit with the canonical withdrawal’s wait and claim cost. Before signing either route, confirm the destination address, token contract and minimum received. Afterward, verify the destination transaction or balance; a successful source transaction proves the transfer started, not that the receiving asset has arrived. The practical choice is the route that delivers the right token, usable gas and acceptable net value by the time you need them. For a Mantle bridge that also requires a token change, [mantlebridge.us](https://mantlebridge.us) lets you arrange the cross-chain transfer and swap in one flow when your exact chain and asset pair is available. Compare that result with a same-asset bridge before signing, then verify the balance on the destination chain. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://crypto-glossary-hub.gitbook.io/crypto-glossary-hub-docs/mantle-bridge-move-assets-with-fewer-steps.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.