← all services

BCH NEAR

rate type
Market-rate quotes (may change before execution).
root@notkyc:~$ rates cached for everyone · ttl 60s · 0s
# Exchange Score No-KYC record? Rate You receive (1 BCH) Limits (BCH)
1 OctoSwap BEST A priv 87trust 70
// no on-platform swaps yet
1 BCH = 113.339293 NEAR 113.339293 NEAR min 30.672158 · max 5258.084305 swap on notkyc swap on OctoSwap →
2 Quickex C priv 49trust 75 1 BCH = 112.80784703 NEAR 112.80784703 NEAR swap on Quickex →
3 Lizex C priv 62trust 70
1/1 KYC-free
1 BCH = 112.670486 NEAR 112.670486 NEAR min 0.26408084 · max 4357.53700611 swap on notkyc swap on Lizex →
4 StealthEX C priv 49trust 79
5/5 KYC-free
1 BCH = 112.46467958 NEAR 112.46467958 NEAR min 0.0011024 swap on notkyc swap on StealthEX →
5 Swapuz B priv 59trust 88
10/10 KYC-free
1 BCH = 112.2761 NEAR 112.2761 NEAR min 0.394 · max 13138.298 swap on notkyc swap on Swapuz →
6 Baltex D priv 40trust 65 1 BCH = 112.2124787 NEAR 112.2124787 NEAR min 0.00111342 swap on Baltex →
7 PegasusSwap A+ priv 95trust 94
2/2 KYC-free
1 BCH = 111.83695631 NEAR 111.83695631 NEAR min 0.04379434 · max 425.57588333 swap on notkyc swap on PegasusSwap →
8 ChangeHero D priv 43trust 72 1 BCH = 111.58783569 NEAR 111.58783569 NEAR min 0.09581 swap on ChangeHero →
9 Exolix C priv 49trust 80
6/6 KYC-free
1 BCH = 111.5046463 NEAR 111.5046463 NEAR min 0.21459227 · max 425.57588333 swap on notkyc swap on Exolix →
10 XMRS C priv 61trust 71
6/6 KYC-free
1 BCH = 111.1309 NEAR 111.1309 NEAR min 0.4379 · max 4379.4341 swap on notkyc swap on XMRS →
11 SideShift C priv 48trust 78 1 BCH = 110.34283467 NEAR 110.34283467 NEAR min 0.0131406 · max 44.79863827 swap on SideShift →
12 GhostSwap C priv 65trust 60
3/4 KYC-free
1 BCH = 110.24600879 NEAR 110.24600879 NEAR min 0.13153765 · max 986.53233747 swap on notkyc swap on GhostSwap →
OctoSwap BEST A
Rate1 BCH = 113.339293 NEAR
You receive113.339293 NEAR
Limitsmin 30.672158 · max 5258.084305 BCH
Rate1 BCH = 112.80784703 NEAR
You receive112.80784703 NEAR
Limits— BCH
Rate1 BCH = 112.670486 NEAR
You receive112.670486 NEAR
Limitsmin 0.26408084 · max 4357.53700611 BCH
Rate1 BCH = 112.46467958 NEAR
You receive112.46467958 NEAR
Limitsmin 0.0011024 BCH
Rate1 BCH = 112.2761 NEAR
You receive112.2761 NEAR
Limitsmin 0.394 · max 13138.298 BCH
Rate1 BCH = 112.2124787 NEAR
You receive112.2124787 NEAR
Limitsmin 0.00111342 BCH
Rate1 BCH = 111.83695631 NEAR
You receive111.83695631 NEAR
Limitsmin 0.04379434 · max 425.57588333 BCH
Rate1 BCH = 111.58783569 NEAR
You receive111.58783569 NEAR
Limitsmin 0.09581 BCH
Rate1 BCH = 111.5046463 NEAR
You receive111.5046463 NEAR
Limitsmin 0.21459227 · max 425.57588333 BCH
Rate1 BCH = 111.1309 NEAR
You receive111.1309 NEAR
Limitsmin 0.4379 · max 4379.4341 BCH
Rate1 BCH = 110.34283467 NEAR
You receive110.34283467 NEAR
Limitsmin 0.0131406 · max 44.79863827 BCH
Rate1 BCH = 110.24600879 NEAR
You receive110.24600879 NEAR
Limitsmin 0.13153765 · max 986.53233747 BCH

Moving BCH into NEAR pairs a UTXO-based Bitcoin fork with a sharded, account-based proof-of-stake chain - two completely incompatible networks with no bridge between them. Swapping is the practical way to rotate from a payments-focused asset into NEAR's developer ecosystem (Aurora EVM, chain signatures, account abstraction). Aggregating quotes matters here because BCH/NEAR is a thin direct pair on most venues, and routing usually goes through BTC or USDT under the hood.

// about this pair

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.

// FAQ
Do I need a .near account before swapping?
Yes. NEAR requires the destination account to exist on-chain before it can receive tokens. Either use a named account (yourname.near) created through a wallet, or an implicit account (64-character hex address) which is auto-created on first funding. Most swap services accept both, but double-check the address field validation before depositing BCH.
Why does the BCH -> NEAR rate look worse than BCH -> BTC plus BTC -> NEAR separately?
Because most services route this pair through an intermediate asset internally and charge spread on each leg. Aggregators surface the venue with the tightest combined spread. If you see a >2% gap versus calculated spot, it usually means the venue has shallow NEAR liquidity, not that BCH is mispriced.
How long does a BCH -> NEAR swap take end to end?
Roughly 15-25 minutes in normal conditions. BCH needs 1-2 block confirmations (~10-20 minutes) before the service credits the swap, then NEAR settlement takes 1-3 seconds. During mempool congestion or low fee-rate sends, BCH confirmation can stretch to 30+ minutes. NEAR-side delays are rare.
Can I send BCH from a Bitcoin (BTC) wallet by mistake?
No, and you should not try. BCH and BTC share historical address formats but operate on separate chains. Sending BTC to a service expecting BCH (or vice versa) will result in lost funds with no recovery on no-KYC platforms. Use a wallet that explicitly supports BCH and the CashAddr format (bitcoincash:...).
Is there a minimum BCH amount for this swap?
Typically yes - around 0.05-0.1 BCH depending on the venue, set to cover network fees and ensure the NEAR output exceeds dust thresholds. Sending below the minimum after a quote is generated usually triggers an automatic refund to your declared BCH refund address, minus the BCH network fee.
Does swapping BCH to NEAR no-KYC leave a traceable link?
On-chain, yes - the BCH deposit and NEAR payout are both public, and chain analysis can correlate them via timing and amount. No-KYC means the service does not collect identity, not that the swap is private. If unlinkability matters, route through a privacy-preserving asset first or use multiple hops with different services.
// related