What moves your BTC spread between chains

Bitcoin is the most liquid cryptocurrency and the hardest one to move. Every swap that involves Bitcoin inherits the constraints of its network: block times, fee auctions, address formats, and the fact that a transaction, once sent, cannot be recalled. Understanding those constraints is the difference between a swap that completes in minutes and one that lingers for hours or fails entirely.

This page explains what actually happens when you send Bitcoin into a swap and what you should check before you click confirm.

The basic mechanism: custody, not magic

When you swap Bitcoin for another asset, the exchange does not happen on a single ledger. Bitcoin and the destination chain are separate networks that cannot talk to each other. The service must receive your Bitcoin on one side, then send the other asset on the other side. Between those two events, the service holds your Bitcoin.

The process is always three steps:

1. You send Bitcoin to an address the service controls.
2. The service waits for confirmations on the Bitcoin network.
3. The service sends the destination asset to the address you provided.

Nothing happens in step 2 until step 1 is irreversible enough. "Irreversible enough" is defined by the number of Bitcoin network confirmations the service requires. Most services wait for one confirmation; some wait for three. During that wait, your Bitcoin is in the service's wallet, not yours.

Can I swap BTC directly from my wallet without depositing to an exchange first

Yes. That is the entire point of a non-custodial swap service. You send from your wallet to the swap address, and the service sends the result back to your wallet. There is no intermediate account, no login, no deposit balance. You control your keys throughout. The only moment you do not control the Bitcoin is during the confirmation window, when the service holds it.

This is different from a centralized exchange, where you first deposit Bitcoin into an exchange wallet, then trade, then withdraw. That process involves two on-chain transactions from your wallet (deposit and withdrawal) plus whatever internal bookkeeping the exchange does. A direct swap compresses that into one outbound transaction from you and one inbound transaction to you on the destination chain.

How does a Lightning swap skip the Bitcoin mempool

Lightning Network transactions do not go through the Bitcoin mempool at all. They are off-chain updates to a channel state, not on-chain transactions. When you swap using Lightning, you pay an invoice from your Lightning wallet. The service receives the payment through its Lightning node, then sends the destination asset on the other chain.

The Bitcoin network never sees that payment. No mempool, no fee auction, no confirmation wait. The swap completes as fast as the Lightning payment routes, which is usually a few seconds. The trade-off is that you need a Lightning wallet with inbound liquidity, and the swap size is limited by channel capacity. Large amounts still require on-chain Bitcoin.

How to move BTC into a stablecoin without using a centralized exchange

You send Bitcoin to a swap address and receive USDT, USDC, or another stablecoin on a network you specify. The service handles the conversion. The stablecoin arrives in your wallet on the destination chain. No exchange account, no KYC, no withdrawal delay.

The important detail is that you must choose the destination network correctly. Stablecoins exist on Ethereum, BSC, Polygon, Solana, and many others. If you give the service an address on one network but expect the stablecoin on another, the funds will be unrecoverable. Always verify the network field matches the address you provide.

What causes Bitcoin network fees to spike during a swap

You pay the Bitcoin network fee when you send your transaction. That fee is set by you, not by the service. The fee goes to miners, and it determines how quickly your transaction enters a block. If the mempool is congested, miners prioritize transactions with higher fees per byte. A low fee means your transaction sits in the mempool waiting.

The service cannot control this. It sees your transaction only after a miner includes it in a block. If you set a fee that is too low for current conditions, your swap does not start until the transaction confirms. That delay is entirely your responsibility.

What happens if I send Bitcoin with a low miner fee to a swap address

Your transaction enters the mempool and waits. The service does not see it until it confirms. If the mempool clears and your transaction eventually confirms, the swap proceeds normally, just later than expected. If the mempool remains congested and your transaction is dropped from the mempool, the Bitcoin returns to your wallet after a timeout. The swap never starts.

You can accelerate a stuck transaction using Replace-by-Fee (RBF) if your wallet supports it and you enabled RBF when creating the transaction. Without RBF, you can only wait. The service has no mechanism to speed up your transaction. It cannot pay a fee on your behalf because the transaction is not theirs.

Which Bitcoin address type should I use to avoid swap delays

Use the address type the service displays. The swap page generates an address for you. Send to that exact address. Do not send to a different address type and expect the service to adapt.

If the service shows a SegWit address (starting with bc1), send from a SegWit wallet. If it shows a legacy address (starting with 1), send from a legacy wallet. Sending from a mismatched address type works technically, but it may cause the service's wallet to take longer to detect the transaction or require additional confirmations. Some services reject non-standard address types outright.

The safest approach: copy the displayed address, paste it into your wallet, and send. Do not transform it. Do not guess.

Why does a Bitcoin swap take longer than swapping other coins

Bitcoin blocks come every ten minutes on average. Other chains produce blocks every few seconds. A Bitcoin swap requires at least one Bitcoin block confirmation before anything happens. That is a minimum of ten minutes, often more if you hit the tail of a block interval.

Other coins confirm in seconds. A swap between two fast chains can complete in under a minute. Bitcoin's block time is the bottleneck. There is no way around it except Lightning, which bypasses the block time entirely but has its own constraints.

Why does the final BTC amount I receive differ from the swap preview

The preview shows an estimate based on current rates. The actual rate is locked when the service receives your Bitcoin and checks the market. If the market moves between the preview and the confirmation, the rate changes.

More commonly, the difference comes from network fees. The preview may include an estimated network fee for the destination transaction. The actual fee depends on network conditions when the service sends. If the destination network is congested, the service pays a higher fee and passes that cost to you. The result is a slightly lower final amount.

Another cause: the service deducts a fixed or percentage fee that the preview did not clearly separate from the rate. The preview shows the gross amount; the final amount is net of fees. Always check the fee breakdown on the swap page before you send.

What you should check before you send

• The address matches exactly. One wrong character and the Bitcoin is gone.
• The destination address and network are correct. Sending to an Ethereum address on a BSC network loses funds.
• The miner fee is appropriate for current mempool conditions. Check a fee estimator before you send.
• Your wallet supports RBF if you want the option to accelerate a stuck transaction.
• The swap expiry time. If you send after the expiry, the service may not process the swap, and you will need to contact support to recover your funds.

Bitcoin swaps are not instant. They are not magic. They are a mechanical process with clear steps and clear risks. Understanding each step makes the process predictable. Ignoring a step makes it a gamble.