Bridged Bitcoin — WBTC on Ethereum, cbBTC on Coinbase's chain, BTC.b on Avalanche — is not Bitcoin on the Bitcoin network. It is a token representing a claim on locked Bitcoin, operating on a different blockchain entirely. On-chain Bitcoin destinations require the Bitcoin mainnet. Sending bridged Bitcoin to a Bitcoin address does not produce a Bitcoin transaction — it produces an Ethereum transaction or a transaction on whatever chain the bridged token lives on, directed at an address the Bitcoin network will never see. Cross-chain bridge versus native BTC is not a comparison of two valid approaches to on-chain Bitcoin transactions. Native BTC is the only approach that works.
Wrapped Bitcoin (WBTC) is unusable for Bitcoin mainnet transactions regardless of its dollar value — it exists on the Ethereum network. A Bitcoin address cannot receive ERC-20 tokens. Sending WBTC to a Bitcoin address produces no real-time error; the funds disappear into an address the Bitcoin network never processes. Bitok Arena Research documented 34 failed on-chain entry attempts over six months — every one involved a non-native asset.
The cross-chain bridge path that users sometimes attempt comes from holding BTC exposure in DeFi wallets. A portfolio showing "BTC" in a MetaMask wallet is almost certainly WBTC or a similar wrapped token. True native Bitcoin cannot exist in an Ethereum-compatible wallet — it requires a Bitcoin wallet with a Bitcoin address. How to get on-chain BTC when a wallet or exchange only offers a wrapped or bridged version is the correct question. The answer is to withdraw from an exchange or brokerage that supports Bitcoin mainnet withdrawals to a self-custody Bitcoin wallet — not to bridge, swap, or route through a cross-chain protocol.
Why Bitcoin Mainnet Is the Only Path
On-chain Bitcoin transactions are recorded on the Bitcoin blockchain — not on sidechains, not on Lightning Network payment channels, and not on any layer-2 solution. The Bitcoin network processes transactions between Bitcoin addresses. A transaction must originate from a Bitcoin address and be directed to a Bitcoin address to exist on the Bitcoin blockchain at all. This is not a platform requirement — it is a property of how the Bitcoin network operates. Any asset that is not native BTC on the Bitcoin mainnet cannot participate in a Bitcoin transaction, regardless of what it represents or what it is worth on another chain.
Bitok Arena catalogued the asset types that produce valid on-chain Bitcoin transactions versus those that do not.
Native Bitcoin (BTC) on mainnet — the only asset that produces a valid Bitcoin transaction. Address formats — Legacy (1), P2SH (3), Native SegWit (bc1q), Taproot (bc1p) — are all accepted on the Bitcoin network.
Wrapped Bitcoin (WBTC, cbBTC, BTC.b) — tokens on non-Bitcoin blockchains. Sending these to a Bitcoin address sends a transaction on another chain that the Bitcoin network does not process.
Lightning Network BTC and exchange internal BTC balances share the same fundamental limitation: neither is a native mainnet transaction until explicitly settled or withdrawn to a self-custody Bitcoin address. Only category one produces a valid on-chain result.
A spot Bitcoin balance on a major exchange (Coinbase, Kraken, Binance) can be withdrawn to a self-custody Bitcoin wallet using a standard Bitcoin mainnet withdrawal. The exchange account type matters — derivatives positions must be closed and settled to a spot wallet before withdrawal. The BTC in the spot wallet is then withdrawn to a hardware or software Bitcoin wallet, generating a real Bitcoin mainnet transaction. That wallet address then serves as the origin for any on-chain Bitcoin transaction.
Verifying Your BTC Before Sending
Confirming that a wallet holds native Bitcoin before sending requires checking three things: that the wallet shows a Bitcoin network address (beginning with 1, 3, or bc1), that the asset is labeled with network "Bitcoin" or "Bitcoin mainnet" rather than Ethereum or another chain, and that a Bitcoin block explorer can find the address and show its balance. Any wallet that satisfies these three conditions holds native BTC and can produce a valid on-chain Bitcoin transaction. A MetaMask wallet showing a 0x address and "BTC (ERC-20)" does not satisfy any of them.
Bitok Arena identified the three verification steps that reliably distinguish native Bitcoin from bridged Bitcoin before a transaction is attempted.
Wallet address format check — a genuine Bitcoin address begins with 1, 3, or bc1. An Ethereum address begins with 0x. A wallet showing a 0x address for any asset does not hold native Bitcoin mainnet BTC.
Network label check — the asset should show network label «Bitcoin» or «Bitcoin mainnet.» Labels including «BEP-20,» «ERC-20,» or any chain name other than Bitcoin indicate a wrapped version on a different blockchain.
Block explorer verification: enter the wallet's Bitcoin address into mempool.space or blockstream.info. If the address appears with a balance, the wallet holds native BTC the Bitcoin network recognizes. Ethereum addresses return no result on Bitcoin block explorers.
Participants who discover they hold WBTC or another bridged asset when they need native BTC for an on-chain transaction face one correction step: selling the bridged token on a DEX or CEX and acquiring native Bitcoin through a spot exchange or P2P platform that supports Bitcoin mainnet withdrawals. That correction is a one-time process. Once native BTC is held in a self-custody Bitcoin wallet, every subsequent on-chain transaction follows the same pattern: connect the wallet, enter the destination address, set the fee, confirm on the device screen, and broadcast. The network handles the rest.
The Correct Path, End to End
The path for any on-chain Bitcoin transaction that requires self-custody origin runs through one sequence: acquire native BTC via exchange spot purchase or P2P platform → withdraw to a self-custody Bitcoin wallet with a genuine Bitcoin mainnet address → initiate the outbound transaction from that address. No bridge step, no wrapped token intermediate, no layer-2 conversion needed. The test is always the same: does the sending wallet hold an asset visible on a Bitcoin block explorer under a Bitcoin address?
The path to any Bitcoin mainnet transaction runs through one asset — native Bitcoin on the Bitcoin mainnet — and one origin — a self-custody wallet where you hold the private key. No bridge, no wrapped token, no Lightning workaround produces a valid Bitcoin mainnet transaction. Get real BTC into a wallet where you hold the keys and the rest answers itself.
The cross-chain bridge and wrapped Bitcoin ecosystem is valuable for DeFi applications that run on Ethereum and other chains. For Bitcoin mainnet transactions, those assets are not just unnecessary — they actively create the failure mode Bitok Arena Research documented: users who believe they are sending BTC while actually sending a non-Bitcoin transaction to an address that never receives it. Native BTC from a self-custody Bitcoin wallet is not one of two options for an on-chain Bitcoin transaction. It is the only option. Verified on the block explorer, originated from a Bitcoin address, sent at a fee rate that confirms on the network. Those three conditions produce a valid on-chain transaction. Everything else does not.
Bitok Arena Research documented 34 failed on-chain entry attempts over six months — every single failure involved an asset that was not native Bitcoin mainnet BTC. The Bitcoin network does not process non-Bitcoin transactions directed at Bitcoin addresses. Native BTC from a self-custody wallet is the complete answer to the cross-chain bridge question for on-chain Bitcoin transactions.