NEAR → BCH

ordenar por

tipo de tasa

Flotante Fija

Cotizaciones a tasa de mercado (pueden cambiar antes de ejecutarse).

root@notkyc:~$ tasas en caché para todos · ttl 60s · 0s

#	Casa de cambio	Puntuación	Historial sin KYC?	Tasa	Recibes (1 NEAR)	Límites (NEAR)
1	OctoSwap MEJOR	A priv 87trust 70	// no on-platform swaps yet	1 NEAR = 0.008838 BCH	0.008838 BCH	min 3477.39692 · max 596125.186289	intercambiar en notkyc	intercambiar en OctoSwap →
2	SideShift	C priv 48trust 78	—	1 NEAR = 0.00873281 BCH	0.00873281 BCH	min 1.47906984 · max 7395.34919073		intercambiar en SideShift →
3	XMRS	C priv 61trust 71	6/6 KYC-free	1 NEAR = 0.0087 BCH	0.0087 BCH	min 49.677 · max 496770.9885	intercambiar en notkyc	intercambiar en XMRS →
4	Baltex	D priv 40trust 65	—	1 NEAR = 0.0082312 BCH	0.0082312 BCH	min 0.12638312		intercambiar en Baltex →
5	StealthEX	C priv 49trust 79	5/5 KYC-free	1 NEAR = 0.0081892 BCH	0.0081892 BCH	min 0.1251318	intercambiar en notkyc	intercambiar en StealthEX →

OctoSwap MEJOR A

Tasa1 NEAR = 0.008838 BCH

Recibes0.008838 BCH

Límitesmin 3477.39692 · max 596125.186289 NEAR

intercambiar en notkyc intercambiar en OctoSwap →

SideShift C

Tasa1 NEAR = 0.00873281 BCH

Recibes0.00873281 BCH

Límitesmin 1.47906984 · max 7395.34919073 NEAR

intercambiar en SideShift →

XMRS C

Tasa1 NEAR = 0.0087 BCH

Recibes0.0087 BCH

Límitesmin 49.677 · max 496770.9885 NEAR

intercambiar en notkyc intercambiar en XMRS →

Baltex D

Tasa1 NEAR = 0.0082312 BCH

Recibes0.0082312 BCH

Límitesmin 0.12638312 NEAR

intercambiar en Baltex →

StealthEX C

Tasa1 NEAR = 0.0081892 BCH

Recibes0.0081892 BCH

Límitesmin 0.1251318 NEAR

intercambiar en notkyc intercambiar en 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.

// sobre este par

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.

// preguntas

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.

// relacionados