Bitcoin on Arbitrum: The Token Arrives, Not the Bitcoin

Moving Bitcoin to Arbitrum means using a route that converts or represents BTC as a token Arbitrum can process; Bitcoin itself does not pass through Arbitrum’s canonical bridge. Bitcoin records UTXO transfers on its own network. Arbitrum’s canonical token bridge handles ETH and ERC-20 tokens between Ethereum and Arbitrum. A route between them therefore needs an intermediary: a custodian, a bridge mechanism, or a service that combines a Bitcoin-side deposit with token delivery on Arbitrum.

The result is usually a balance of tokenized bitcoin, such as WBTC, or another BTC-linked asset supported by the destination application. It is an Arbitrum token balance, not a Bitcoin UTXO under the same wallet controls. Route designs and redemption rights differ, so check the target token and mechanism before sending funds. For the broader question of how applications choose routes, see Acrossbridge route selection for apps.

Can you send native BTC through Arbitrum’s canonical bridge?

No. The canonical bridge does not take a Bitcoin transaction as a deposit and issue native BTC on Arbitrum. Its token flow starts with an asset Arbitrum can represent through its Ethereum-based bridge contracts. Bitcoin’s network does not call those contracts or share Arbitrum’s execution environment.

A route can still begin with BTC. One design accepts a Bitcoin-side deposit and releases a tokenized asset on Arbitrum. Another first converts BTC into a bridgeable token on an EVM network, then moves that token to Arbitrum. A swap may happen before or after the cross-chain transfer. The interface can present these steps as one action, but the underlying route still has separate source-chain, bridge, and destination-chain operations.

Those operations matter because each changes what the user holds. If a service takes custody of BTC and issues a token, the token’s backing and redemption depend on that issuer’s rules and controls. If an intermediary bridge or liquidity provider delivers the destination token, the route depends on that component’s settlement and liquidity. The word “Bitcoin” in a token’s name does not establish that it is native BTC or specify how redemption works.

What happens during a Bitcoin-to-Arbitrum transfer?

The route records an input on Bitcoin, resolves how much value to deliver, and sends an eligible token to the chosen Arbitrum address. The precise sequence depends on the service, but the main stages are:

• Input: The user sends BTC to a route-specific Bitcoin address or uses a service that first holds BTC in an account. A Bitcoin transaction is confirmed according to that route’s requirements.
• Conversion or settlement: The route uses its stated mechanism to obtain or release the destination asset. That may involve custody and token issuance, a swap, or liquidity provided on the destination chain.
• Arbitrum delivery: A transaction transfers the selected token to the destination address. Arbitrum executes that token transfer; it does not verify or settle the original Bitcoin transaction as part of its rollup.
• Application use: The receiving contract or app accepts the token only if it supports that exact asset on that Arbitrum network.

Because the transfer crosses systems, a displayed quote is not the same as a guaranteed amount received. The route may account for fees, exchange rates, slippage, and the amount needed for destination execution. Some services return a token directly; others can bridge first and swap on Arbitrum. The latter can be convenient when an app needs a particular asset, but it adds another execution step and another point where the outcome can differ from the initial quote.

Which token arrives, and what should you check?

The token contract on Arbitrum determines what the destination wallet and app receive. Two tokens can both track bitcoin’s price while having different issuers, backing arrangements, redemption processes, and contract addresses. A familiar ticker alone is not enough to identify the asset. An application may accept one BTC-linked token and reject another.

Before confirming a route, check the destination network, recipient address, exact token contract, expected output, fees, and any minimum or refund conditions. Confirm what happens if the Bitcoin payment arrives late, is underpaid, or the destination transaction cannot complete. These checks matter most when the route uses a deposit address or an intermediary that must match the Bitcoin payment to a quote.

For most users moving value into an Arbitrum app, the right route is the one that delivers the exact token the app supports and clearly explains how BTC is converted, held, or redeemed. If the goal is to retain native Bitcoin, a token balance on Arbitrum is a different asset relationship. The bridge can make bitcoin-denominated value usable in Arbitrum contracts, but it cannot make an Arbitrum token transfer equivalent to a Bitcoin-network transfer.