BCH → NEAR

BCH -> NEAR: what makes this pair specific

BCH settles on its own SHA-256 chain with ~10 minute blocks and sub-cent fees, while NEAR uses Nightshade sharding with ~1.2 second block times and human-readable account IDs (yourname.near). There is no shared address format, no wrapped BCH on NEAR, and no native bridge - so a swap is the only realistic path. Most swap services internally route BCH -> BTC or BCH -> USDT -> NEAR, which means the rate you see already absorbs two legs of spread. Liquidity for BCH inputs is decent because it remains a top-30 asset, but NEAR depth varies more by venue.

Confirmation timing is asymmetric: BCH typically needs 1-2 confirmations (10-20 minutes) before the service releases NEAR, but the NEAR payout itself lands in seconds once triggered. Total wall-clock time is dominated by BCH-side confirmations, not NEAR.

What to check before locking a quote

• Rate type: floating rates track the market until execution; fixed rates lock a number but add a 0.5-1.5% buffer and often have tighter min/max bands.
• Destination format: confirm the service supports both implicit (64-char hex) and named (.near) account IDs - some only accept one.
• Minimums: BCH minimums are usually set in USD-equivalent (~20-50 USD), so small BCH amounts may be rejected after deposit.
• Refund address: always provide a BCH refund address. If the deposit falls outside the quoted window, no-KYC services will return funds there with no recourse otherwise.
• Memo/tag: NEAR does not use memos, so ignore any field asking for one - paste only the account ID.

Practical tips: send a small test amount first if you are moving a meaningful BCH balance, batch into one transfer to avoid paying the spread twice, and check the aggregator quote against the implied BCH/USD and NEAR/USD spot rates - if the gap exceeds ~2%, wait or pick another route.