NEAR → BTC

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.000032 BTC	0.000032 BTC	min 3477.39692 · max 596125.186289	intercambiar en notkyc	intercambiar en OctoSwap →
2	SideShift	C priv 48trust 78	—	1 NEAR = 0.00003196 BTC	0.00003196 BTC	min 2.95813968 · max 7395.34919073		intercambiar en SideShift →

OctoSwap MEJOR A

Tasa1 NEAR = 0.000032 BTC

Recibes0.000032 BTC

Límitesmin 3477.39692 · max 596125.186289 NEAR

intercambiar en notkyc intercambiar en OctoSwap →

SideShift C

Tasa1 NEAR = 0.00003196 BTC

Recibes0.00003196 BTC

Límitesmin 2.95813968 · max 7395.34919073 NEAR

intercambiar en SideShift →

Swapping NEAR to BTC is a common move for users rotating out of an L1 smart contract token into the deepest liquidity asset in crypto. Whether you're taking profit after a NEAR rally, consolidating bags into hard money, or shifting from a Rust-based sharded chain into something you can self-custody on a hardware wallet long-term, a no-KYC route lets you do it without surrendering ID to a centralized desk.

// sobre este par

NEAR -> BTC: what makes this pair specific

NEAR runs on its own NightShade-sharded PoS chain with ~1-2 second finality and sub-cent fees, so the leg sending NEAR out is fast and cheap. The slow side is BTC: confirmations average 10 minutes, and during mempool congestion you may wait 30-60 minutes for the first confirmation a destination wallet considers safe. Aggregators usually wait for 1-2 BTC confirmations before marking the swap complete, so plan for total settlement around 15-45 minutes regardless of which service quotes the best rate.

Liquidity for NEAR/BTC is decent but thinner than ETH/BTC or SOL/BTC. Expect rate spread to widen on swaps above ~50k USD equivalent, and floating rates can drift 0.3-0.8% during the BTC confirmation window.

Choosing a route for this pair

Network match: send NEAR on the native NEAR chain (not wrapped NEAR on Aurora/ETH) unless the quote explicitly accepts it. Receive BTC on mainnet; Lightning is rarely supported by aggregator routes for this pair.
Fixed vs floating rate: fixed locks the quote but charges a 1-2% premium and has tighter min/max bands. Floating gives a better headline rate but exposes you to BTC price drift during confirmation.
Min/max: NEAR swaps typically start around 5-10 NEAR and cap in the 50k-200k NEAR range per transaction.
Refund address: always provide a NEAR address you control. If the deposit arrives outside the rate window, the service refunds there.

Practical tips: send a small test amount first if you've never used the route, double-check the memo field is NOT required (NEAR uses implicit accounts, not memos like XRP or XLM), and avoid swapping during obvious BTC volatility spikes - a 2% candle mid-swap on a floating quote is real money lost.

// preguntas

How long does a NEAR to BTC swap actually take?

The NEAR deposit confirms in seconds. The bottleneck is Bitcoin: most aggregators release BTC after 1-2 confirmations, which means 15-30 minutes typical, up to 60+ minutes if mempool fees spike. Fixed-rate quotes usually allow a 10-15 minute deposit window before the rate expires.

Do I need a memo or tag when sending NEAR?

No. NEAR uses named accounts (like alice.near) or 64-character implicit addresses, and the address itself routes the deposit. There is no memo or destination tag step like with XRP, XLM, or BNB Beacon Chain. Just paste the deposit address exactly as shown.

Should I pick a fixed or floating rate for NEAR -> BTC?

Fixed if you want certainty and the amount is meaningful. Floating if you're swapping a small amount, comfortable with 0.3-0.8% drift during BTC confirmation, and want the better headline rate. NEAR/BTC liquidity is solid enough that floating spreads stay reasonable outside of major news events.

Can I receive BTC over Lightning instead of mainnet?

Almost never for this pair through no-KYC aggregators. Routes for NEAR -> BTC settle on Bitcoin mainnet. If you need Lightning, swap NEAR -> BTC mainnet first, then bridge to Lightning via a submarine swap or a Lightning-enabled wallet separately.

Is wrapped NEAR on Aurora or Ethereum accepted?

Usually not without explicitly selecting that network in the quote. Most NEAR -> BTC routes assume native NEAR on the NEAR Protocol chain. Sending ERC-20 wrapped NEAR to a native NEAR deposit address will result in lost funds. Confirm the network label before sending.

What's a safe test amount before sending a large NEAR balance?

5-10 NEAR is usually above the minimum and cheap enough to verify the route end-to-end. Once you confirm BTC arrives at your destination wallet, send the remainder in one transaction to avoid paying multiple network fees and to lock a single rate quote.

// relacionados