NEAR → BCH

sort by

rate type

Floating Fixed

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 NEAR)	Limits (NEAR)
1	OctoSwap BEST	A priv 87trust 70	// no on-platform swaps yet	1 NEAR = 0.00882 BCH	0.00882 BCH	min 3477.569676 · max 596154.80153	swap on notkyc	swap on OctoSwap →
2	SideShift	C priv 48trust 78	—	1 NEAR = 0.00872155 BCH	0.00872155 BCH	min 1.4777267 · max 7388.63349402		swap on SideShift →
3	XMRS	C priv 61trust 71	6/6 KYC-free	1 NEAR = 0.0087 BCH	0.0087 BCH	min 49.6622 · max 496622.9638	swap on notkyc	swap on XMRS →
4	Baltex	D priv 40trust 65	—	1 NEAR = 0.0082322 BCH	0.0082322 BCH	min 0.12638554		swap on Baltex →
5	StealthEX	C priv 49trust 79	5/5 KYC-free	1 NEAR = 0.0081902 BCH	0.0081902 BCH	min 0.1251342	swap on notkyc	swap on StealthEX →

OctoSwap BEST A

Rate1 NEAR = 0.00882 BCH

You receive0.00882 BCH

Limitsmin 3477.569676 · max 596154.80153 NEAR

swap on notkyc swap on OctoSwap →

SideShift C

Rate1 NEAR = 0.00872155 BCH

You receive0.00872155 BCH

Limitsmin 1.4777267 · max 7388.63349402 NEAR

swap on SideShift →

XMRS C

Rate1 NEAR = 0.0087 BCH

You receive0.0087 BCH

Limitsmin 49.6622 · max 496622.9638 NEAR

swap on notkyc swap on XMRS →

Baltex D

Rate1 NEAR = 0.0082322 BCH

You receive0.0082322 BCH

Limitsmin 0.12638554 NEAR

swap on Baltex →

StealthEX C

Rate1 NEAR = 0.0081902 BCH

You receive0.0081902 BCH

Limitsmin 0.1251342 NEAR

swap on notkyc swap on StealthEX →

Moving NEAR into BCH is a cross-chain hop between two structurally different networks: NEAR's sharded Nightshade proof-of-stake chain and Bitcoin Cash's UTXO-based 32MB-block PoW fork of Bitcoin. Common reasons to swap include rotating out of a smart-contract ecosystem token into a high-liquidity payments coin, consolidating holdings into something with deep CEX support, or funding a BCH address for low-fee on-chain transfers without touching a KYC venue.

// about this pair

NEAR -> BCH: what this swap actually involves

NEAR settles in roughly 1-2 second blocks with sub-cent fees, while BCH confirms in ~10 minute blocks with fees usually under a cent. There is no shared bridge or wrapped-asset path between them, so any swap is a custodial or non-custodial atomic exchange where the service receives NEAR on the NEAR mainnet and broadcasts native BCH to your address. There is only one BCH network (mainnet) - unlike NEAR, BCH is not deployed across multiple L2s or wrappers, so address selection is simpler on the receive side.

Liquidity for NEAR/BCH is thin compared to NEAR/USDT or BCH/BTC, so aggregated quotes typically route through an intermediate leg (NEAR -> USDT -> BCH or NEAR -> BTC -> BCH). Expect spreads to widen on amounts above a few thousand dollars.

Choosing a route and avoiding bad fills

Confirm the deposit address is a NEAR named account or implicit account (64-char hex), not an EVM-style 0x address.
Confirm the BCH payout address starts with 'bitcoincash:' (CashAddr) or a legacy '1'/'q' prefix the service supports - sending to a BTC address by mistake is unrecoverable on most no-KYC desks.
Check whether the rate is fixed (locked at quote time, worse rate, no surprises) or floating (better mid-market rate, but recalculated on arrival).
Read the refund policy: minimum-amount failures and rate-window expiries are the two most common reasons funds get held pending a manual return.

Practical tips: send a small test transaction first if the amount is significant; time the swap during overlapping US/EU hours when market-maker liquidity is deepest; avoid swapping during BCH halving cycles or NEAR unlock events when volatility spikes the floating rate; and never reuse a one-time deposit address from a previous quote.

// FAQ

Why is the NEAR to BCH rate often worse than NEAR to BTC?

BCH has lower order-book depth than BTC across most venues, so swap services route NEAR -> stablecoin or NEAR -> BTC -> BCH internally. Each hop adds spread. If you are swapping a large size, comparing the implied NEAR/BCH rate against the product of NEAR/USDT and USDT/BCH on a major exchange tells you how much overhead the route is costing.

Can I send NEAR from Aurora (the EVM layer) directly?

No. Aurora uses 0x-style EVM addresses and most no-KYC swap services expect native NEAR on the NEAR Protocol mainnet (named accounts or 64-char implicit accounts). Bridge Aurora ETH or NEAR back to native NEAR via the Rainbow Bridge or Aurora's withdrawal flow before initiating the swap, otherwise the deposit will not be detected.

Which BCH address format should I use for the payout?

CashAddr format (starting with 'bitcoincash:' or just 'q') is the modern standard and universally supported. Legacy format (starting with '1') still works on most services but is visually identical to BTC legacy addresses, which increases the risk of a wrong-network mistake. Stick with CashAddr unless your wallet only generates legacy.

How long does a NEAR to BCH swap take end to end?

NEAR finality is near-instant (1-2 seconds) so the deposit leg confirms quickly. The bottleneck is BCH: services typically wait 1-2 BCH confirmations before treating the swap as settled, which is roughly 10-20 minutes. Total time from sending NEAR to receiving spendable BCH is usually 15-25 minutes on a fixed-rate quote.

Is there a wrapped BCH on NEAR I could use instead?

There is no liquid, widely-supported wrapped BCH token on NEAR or Aurora. If you want BCH exposure inside the NEAR ecosystem you are largely out of luck - native BCH on its own chain is the practical option, which is why a cross-chain swap (rather than a bridge) is the standard path.

What happens if my NEAR deposit arrives below the minimum?

Most no-KYC services define a minimum tied to the BCH network fee plus a profitability floor. Deposits under that minimum are either auto-refunded to a return address you provide at quote time, or held until you contact support with the transaction hash. Always set a refund address even on fixed quotes - it is the only recovery path if anything goes wrong.

// related