BCH → BTC
| # | Exchange | Tier ⇅ | Score | No-KYC record? | Rate | You receive (1 BCH) | Limits (BCH) |
|---|
Swapping BCH to BTC is one of the oldest 'fork-back-to-parent' trades in crypto. Holders who received Bitcoin Cash from the 2017 fork, miners paid in BCH, or users who picked it up for cheap on-chain payments often want to consolidate into BTC for deeper liquidity, custody support, and long-term storage. No-KYC routing lets you do that without surrendering ID for a swap between two assets you already self-custody.
What makes BCH -> BTC specific
BCH and BTC share a common ancestor, so the UX feels familiar - both use UTXO models, similar address derivation paths, and comparable confirmation logic. But they are separate chains with separate mempools. A BCH transaction confirms in roughly 10 minutes per block at a fraction of a cent in fees, while the receiving BTC leg lands on a chain where fees fluctuate from a few sats/vB during quiet hours to 100+ sats/vB during congestion. The swap itself is essentially: cheap, fast deposit on BCH; variable-cost settlement on BTC.
Liquidity for this pair is solid across aggregated venues because BCH still sits in the top 25 by market cap and most desks quote it directly against BTC rather than routing through a stablecoin. That means tighter spreads than minor altcoin pairs, but watch for rate drift on floating quotes if BTC moves during your BCH confirmation window.
Choosing a route for this pair
- Network match: confirm the BCH deposit address is native BCH (CashAddr or legacy P2PKH), not BSV or BTC. Sending BCH to a BTC address is unrecoverable on most providers.
- Rate type: fixed rate locks the quote but adds a margin; floating rate gives you market price but exposes you to the 1-3 confirmation wait on BCH.
- Min/max: most desks set BCH minimums around 0.01-0.05 BCH and caps that scale with their BTC inventory.
- Refund address: always provide a BCH refund address you control, in case the swap expires or underpays.
Practical tips: size your trade so the BTC network fee is under 1% of output, swap during low BTC mempool periods (weekends, late UTC), and verify the receiving BTC address format (bech32 vs legacy) matches what the provider supports before broadcasting the BCH deposit.