Lightning Network withdrawals are faster and cheaper than on-chain Bitcoin withdrawals — which is why some exchanges default to Lightning or offer it as their primary withdrawal option. If your application or recipient address requires on-chain Bitcoin mainnet transactions, a Lightning withdrawal will not work. The base layer and the Lightning Network are different layers of the Bitcoin protocol stack. A Lightning payment settles inside a payment channel network; an on-chain transaction is confirmed by Bitcoin miners and recorded permanently on the blockchain. When you need on-chain BTC and your exchange only shows Lightning, you need one conversion step in the middle. Bitok Arena Research reviewed the available paths and their practical trade-offs.
Lightning for fast payments, base layer for permanent records — these are different tools for different functions. An exchange that defaults to Lightning is optimizing for payment cost and speed, which is the right choice for small, frequent transfers. When you need a mainnet Bitcoin transaction — one confirmed by miners, verifiable in any block explorer, permanently on the chain — Lightning is the wrong layer and there is no workaround that changes that.
How to get on-chain BTC when your exchange only offers Lightning withdrawal involves one extra routing step. The direct solution is to receive the Lightning withdrawal in a wallet that supports conversion from Lightning to on-chain BTC — wallets like Phoenix, Aqua, or BlueWallet with both wallet types enabled — and then initiate a submarine swap from Lightning BTC to an on-chain address. Alternatively, a second exchange that accepts Lightning deposits and allows on-chain BTC withdrawal acts as a conversion bridge. Both paths add one step and a small fee — typically under $2 for amounts in the range of $50–$500 — and the result is standard on-chain BTC in a self-custody wallet you control.
Why Exchanges Move to Lightning-First
Exchange Lightning-only withdrawal architectures tend to appear in platforms that prioritize low-fee small-amount transfers — particularly in markets where retail Bitcoin use involves amounts well under $100. On-chain BTC withdrawals require the exchange to open, batch, and broadcast mainnet transactions with miner fees; Lightning payments settle off-chain and cost the exchange almost nothing to process. The exchange is making the technically correct optimization for the majority of their users. The user who needs on-chain BTC for a specific recipient address is a routing problem, not a product problem — and the routing problem has multiple established solutions.
Bitok Arena reviewed three established paths from Lightning-only exchange withdrawal to confirmed on-chain BTC.
Submarine swap service — services like FixedFloat or SideShift convert Lightning BTC to on-chain BTC trustlessly; receive the Lightning withdrawal, input a target on-chain address, and the service delivers confirmed mainnet BTC. Conversion fee: approximately 0.5–1.5% of amount.
Dual-mode wallet swap — wallets including Phoenix, Aqua, and BlueWallet support both Lightning receive and on-chain BTC in the same application; receive Lightning, initiate the in-app swap to on-chain, and send the result from the on-chain wallet. Fee structure varies by wallet but is typically competitive with swap services.
CEX bridge — deposit via Lightning to a second exchange that accepts Lightning and allows on-chain BTC withdrawal; withdraw on-chain from the second exchange. Adds KYC friction if the bridge exchange requires it for withdrawal.
DEX versus CEX for the Lightning-to-on-chain conversion step is a relevant consideration for users who prioritize self-custody throughout the process. A submarine swap service handles the conversion without requiring any exchange account or custodial deposit — the swap is atomic, meaning funds do not leave your control until the on-chain output is confirmed. A CEX bridge requires depositing to a second exchange, which reintroduces custodial risk for the conversion period. For most users, the CEX bridge is operationally simpler. For privacy-conscious users or those moving larger amounts, the submarine swap path is the cleaner option from a self-custody standpoint.
Why On-Chain Transactions Have Different Properties
The reason some applications require specifically on-chain Bitcoin — rather than Lightning — is the difference in what each layer records and guarantees. An on-chain Bitcoin transaction is confirmed by miners, included in a block, and permanently recorded in a distributed ledger that any node in the Bitcoin network can verify independently. The transaction hash is publicly visible, the sending and receiving addresses are readable by any block explorer, and the confirmation status cannot be reversed after sufficient block depth. A Lightning payment is a channel update — it settles inside a payment network and appears on-chain only when a channel closes. Bitok Arena Research on transaction verification confirms that on-chain properties are the basis for applications requiring permanent, publicly verifiable records of BTC transfers.
Bitok Arena compared on-chain Bitcoin transaction properties with Lightning Network payment properties across dimensions relevant to external recipient requirements.
Public verifiability — on-chain transactions appear in every block explorer immediately after broadcast and are permanently readable; Lightning payments are private channel updates invisible to external observers.
Confirmation finality — on-chain transactions achieve irreversibility after sufficient block depth (typically 3–6 confirmations for most applications); Lightning payments are final within the channel network but depend on channel state.
Address compatibility — on-chain transactions work with any standard Bitcoin address format (bc1q, bc1p, 3xxx, 1xxx); Lightning requires a Lightning invoice or Lightning-compatible address, which is a different format entirely.
When a recipient specifies a bc1q or other standard Bitcoin address, they require an on-chain transaction. A Lightning payment to that address will fail or not arrive.
Crypto broker versus exchange for sourcing on-chain BTC is the upstream question that determines whether you face this routing problem at all. Some platforms — eToro, Revolut, PayPal — do not support on-chain Bitcoin withdrawal of any kind. Their Bitcoin is a balance entry, not a UTXO you control. These platforms cannot produce an on-chain Bitcoin transaction regardless of conversion attempts because there is no mechanism that releases actual BTC from their custody to an external address. The Lightning-only exchange is in a different category — the BTC is real, it leaves the exchange, it just leaves on the wrong layer for recipients requiring mainnet transactions. One conversion step solves the routing problem.
Running the Path Before You Need It
The practical recommendation for users who hold BTC on a Lightning-only exchange and need on-chain withdrawals is to run the conversion path once as a test with a small amount before depending on it for a time-sensitive transaction. A submarine swap typically completes in 10–30 minutes from Lightning receipt to confirmed on-chain transaction, depending on swap service liquidity and current mempool conditions. A CEX bridge adds the deposit confirmation time at the second exchange, which can vary from minutes to hours depending on the exchange and Lightning confirmation requirements.
The Lightning Network is excellent for fast, cheap Bitcoin payments. When you need a base-layer mainnet Bitcoin transaction — one that will be confirmed by miners, readable in a block explorer, and permanently on the chain — Lightning is the wrong layer and a conversion step is the only path. That step takes minutes and costs under $2 for most amounts.
Once the Lightning-to-on-chain path is established and tested, subsequent withdrawals use the same routing. The submarine swap service saves the workflow, the dual-mode wallet already has both balance types visible, and the process becomes a repeatable two-step: receive Lightning from the exchange, initiate swap to on-chain, send from the on-chain wallet. The extra step is a one-time routing discovery. After the first successful run, the path is known and the timing is predictable for any future on-chain transaction requirement.
Bitok Arena's review of Lightning-to-on-chain conversion paths finds three reliable options: submarine swap services (self-custody throughout, approximately 0.5–1.5% fee), dual-mode wallet swaps (in-app, slightly simpler operationally), and CEX bridge (simplest but introduces a temporary custodial step). The underlying reason the conversion is necessary — on-chain and Lightning are different Bitcoin protocol layers with different properties — is not a problem to solve but a distinction to understand. When the recipient requires a mainnet Bitcoin address and your exchange delivers Lightning, a conversion step is the complete and sufficient answer.