Merlin Bridge emblem Merlin Bridge

Merlin Bridge

Transfer supported assets across major blockchains and Merlin through a transparent, self-custodial interface.

Bridge assets Active pathway
From
To
Ethereum → Merlin 1 ETH ≈ 1 ETH

Exchange rates and fees appear for confirmation before you authorize.

Understanding Merlin Bridge

1. Establish connection and select pathway

Link a supported EVM wallet and define your transfer: source network, target network and digital asset. In the default configuration, Merlin serves as the target, with Ethereum, Arbitrum, Base, Polygon and BNB Chain available as source options for this demo.

2. Examine details prior to transfer

Specify the quantity and examine the conversion ratio, predicted gas expenses, receiving token representation and account destination. Entry transactions and exit transactions operate differently due to contrasting finality mechanisms and security protocols.

3. Authorize and complete

When moving an ERC-20 asset, an initial authorization transaction may be needed to permit the bridge contract to spend tokens. Following approval, a secondary wallet confirmation commits the transfer. Direct ETH transfers bypass the ERC-20 authorization step but still require wallet signature verification.

4. Await finalization

After the originating network commits the transaction, the bridge validates block confirmations and processes delivery on the receiving end. Maintain wallet accessibility or store both transaction hashes for reference using the respective blockchain explorers; never approve unsolicited signature requests.

Inbound transfers

What traverses the pathway

An inbound transfer secures or moves the chosen asset on the originating network, allowing a corresponding token representation to manifest on Merlin. The originating transaction remains viewable via the originating blockchain explorer; the destination transaction surfaces after processing concludes.

ERC-20 inbound transfers, including USDC, USDT and WBTC, demand sufficient originating network native currency for authorization and transaction processing. The received quantity may fall below your input amount if network or pathway charges are assessed; verify the final quote presented before signing.

Timeline and receiving-network gas requirements

Most inbound transfers hinge on source confirmation counts, operator activity and prevailing network utilization. Heavy load on the originating network may cause delays even after the bridge mechanism has captured the transaction.

Asset arrival does not furnish the resources for subsequent interactions. Maintain the native currency of the destination—whether BTC, another required Merlin resource, or ETH where an ETH-centric pathway explicitly mandates it—to enable future activity with your delivered funds.

Outbound transfers

Standard departure procedure

An outbound transaction from Merlin unfolds in phases instead of instantly. The exit triggers on Merlin, receives recognition from the bridge infrastructure, and then enters an observation window designed to permit the framework to recognize problematic state shifts.

Following expiration of this validation interval, confirmation documentation may require creation and delivery. The final redemption action unlocks the asset on the recipient network. These documentation and redemption operations extend outbound durations relative to inbound operations.

Arrange sufficient transaction resources

Ensure adequate native currency exists on both networks: resources on Merlin for the exit action and resources on the destination network for proof, redemption or supplementary interactions. Refrain from moving your complete balance if the wallet must execute subsequent procedures.

Substitute liquidity routes from independent providers may expedite outbound transfers by dispensing from existing reserves and reconciling through independent pathways. They may carry distinct expense structures, transfer thresholds, custody frameworks and smart-contract considerations, so review the pathway specifics prior to selection.

Available assets and networks

Regularly supported digital assets

Support accessibility varies by pathway and deployment status. Regularly supported selections span ETH, USDC, USDT, WBTC, BTC, DAI, LINK, ARB, OP, MATIC, POL, AVAX, SOL and BNB. A shorthand designation cannot sufficiently establish asset uniqueness: authenticate its deployment address and target representation preceding authorization.

ETHUSDCUSDTWBTCBTCDAILINK

Available networks and identifiers

The EVM chains commonly used in this interface are Ethereum Mainnet (chain ID 1), Arbitrum One (42161), Base (8453), Polygon PoS (137), BNB Smart Chain (56) and Merlin Mainnet (4200). Wallet software may render names inconsistently, so validate the chain ID during network attachment or transition.

Network offerings and asset availability evolve as systems receive improvements. Reference the live interface pathway display as your authoritative source and consult official Merlin resources for accurate deployment specifications.

Privacy, safety and asset management

Assets remain yours

Merlin Bridge operates through non-custodial protocols: digital holdings depart your custody solely through transactions you explicitly confirm, and this interface never requests recovery phrases or cryptographic keys. Each authorization, deposit, withdrawal and redemption generates a recognizable wallet notification.

Verification checklist before authorizing

  • Validate the domain name, active wallet profile, originating network and target network.
  • Verify the asset contract information, recipient account, transfer amount, minimum receipt quantity and stated expenses.
  • Opt for constrained token permissions rather than unrestricted access when your wallet permits this alternative.
  • Disregard requests for recovery phrases, private credentials or unrelated authorizations.
  • Preserve transaction identifiers and leverage the appropriate blockchain explorer if verification becomes necessary.

Bridges incorporate smart contracts, relayer services, decentralized ledgers and signing applications. No platform eliminates code, legal, market or execution risks; use quantities reflecting your comfort level and independently authenticate official deployment information.

Questions and answers

How long does a transfer to Merlin take?

A deposit usually completes after the source-chain transaction receives enough confirmations and the bridge relayer processes it. Timing varies with network congestion and can range from a few minutes to longer during busy periods.

Which wallet can I use with Merlin Bridge?

You can use a compatible EVM wallet such as MetaMask, Rabby or another wallet that supports the selected source and destination networks. The same wallet address can be used across EVM chains, but the network must be switched before signing.

Why do I need native gas on Merlin?

Receiving an asset does not automatically fund future transactions. Keep the native gas asset required by the Merlin environment in your wallet so you can approve, swap or move assets after they arrive.

Are bridge transfers reversible?

Confirmed blockchain transactions generally cannot be reversed by the interface. Check the destination, token and amount before signing, and contact the relevant protocol support channel if a transfer does not arrive.

Why is a withdrawal from Merlin slower than a deposit?

The native withdrawal path may include a challenge period before a proof can be finalized and claimed on the destination chain. This security window makes native exits slower than many deposits or third-party liquidity routes.