BCH → SUI

BCH -> SUI: what makes this pair specific

BCH and SUI run on completely incompatible networks. BCH uses a UTXO model with roughly 10-minute blocks and median fees under a cent; SUI uses an object model with checkpoint finality measured in hundreds of milliseconds and gas paid in MIST (1 SUI = 1,000,000,000 MIST). There is no bridge between them - every swap routes through a liquidity provider that takes BCH on the Bitcoin Cash chain and pays out native SUI to a Sui address (typically a 0x-prefixed 32-byte address, not an EVM address).

Liquidity for this pair is thinner than BCH -> BTC or BCH -> ETH, so quoted rates vary more across providers. BCH itself sees lower volume than its market cap suggests, and SUI order books cluster on a handful of venues. Expect spreads to widen on amounts above a few thousand dollars.

Choosing a route and sizing the trade

• Confirm the destination is a native Sui address, not an Aptos or EVM address - they look similar but funds sent to the wrong chain are unrecoverable.
• Check whether the quote is float or fixed. Float follows the market until execution; fixed locks a rate for a short window (usually 5-15 minutes) but bakes in a wider spread.
• Review the minimum and maximum - SUI payouts often have a higher floor than BTC or ETH pairs because providers hedge in larger SUI lots.
• Read the refund policy: if BCH arrives after the rate-lock expires, some routers auto-refund minus network fees, others re-quote.

Practical tips: send a small test amount first if the trade is meaningful. BCH confirmations are usually fast but mempool congestion or low-fee transactions can delay credit. Time larger swaps during overlapping US/Asia hours when SUI liquidity is deepest. Generate a fresh Sui receive address for each swap to keep on-chain history clean.