← all services
BTC → NEAR
sort by
Market-rate quotes (may change before execution).
| # | Exchange | Score | No-KYC record? | Rate | You receive (1 BTC) | Limits (BTC) | ||
|---|---|---|---|---|---|---|---|---|
| 1 |
|
A priv 87trust 70 | 1 BTC = 30738.979703 NEAR | 30738.979703 NEAR | min 0.112462 · max 19.279165 | swap on notkyc | swap on OctoSwap → | |
| 2 |
|
C priv 64trust 70 | 1 BTC = 30654.98753661 NEAR | 30654.98753661 NEAR | min 0.00371 · max 15.9868 | swap on notkyc | swap on Swaponix → | |
| 3 |
|
C priv 62trust 70 | 1 BTC = 30622.023324 NEAR | 30622.023324 NEAR | min 0.00096882 · max 15.98614362 | swap on notkyc | swap on Lizex → | |
| 4 |
|
C priv 49trust 75 | — | 1 BTC = 30596.40976236 NEAR | 30596.40976236 NEAR | — | swap on Quickex → | |
| 5 |
|
D priv 40trust 65 | — | 1 BTC = 30535 NEAR | 30535 NEAR | min 0.00001919 | swap on Baltex → | |
| 6 |
|
C priv 49trust 79 | 1 BTC = 30522.19980653 NEAR | 30522.19980653 NEAR | min 0.000019 | swap on notkyc | swap on StealthEX → | |
| 7 |
|
B priv 59trust 88 | 1 BTC = 30431.5899 NEAR | 30431.5899 NEAR | min 0.001446 · max 48.197896 | swap on notkyc | swap on Swapuz → | |
| 8 |
|
D priv 43trust 72 | — | 1 BTC = 30425.38164973 NEAR | 30425.38164973 NEAR | min 0.00056487 | swap on ChangeHero → | |
| 9 |
|
A+ priv 95trust 94 | 1 BTC = 30390.20881023 NEAR | 30390.20881023 NEAR | min 0.00016066 · max 10 | swap on notkyc | swap on PegasusSwap → | |
| 10 |
|
C priv 49trust 80 | 1 BTC = 30299.16015625 NEAR | 30299.16015625 NEAR | min 0.00078726 · max 10 | swap on notkyc | swap on Exolix → | |
| 11 |
|
C priv 61trust 71 | 1 BTC = 30124.2001 NEAR | 30124.2001 NEAR | min 0.0016 · max 16.0659 | swap on notkyc | swap on XMRS → | |
| 12 |
|
C priv 48trust 78 | — | 1 BTC = 30065.24882834 NEAR | 30065.24882834 NEAR | min 0.0000482 · max 0.16438004 | swap on SideShift → | |
| 13 |
|
C priv 65trust 60 | 1 BTC = 29862.36413821 NEAR | 29862.36413821 NEAR | min 0.00048249 · max 3.61863976 | swap on notkyc | swap on GhostSwap → |
Rate1 BTC = 30738.979703 NEAR
You receive30738.979703 NEAR
Limitsmin 0.112462 · max 19.279165 BTC
Rate1 BTC = 30654.98753661 NEAR
You receive30654.98753661 NEAR
Limitsmin 0.00371 · max 15.9868 BTC
Rate1 BTC = 30622.023324 NEAR
You receive30622.023324 NEAR
Limitsmin 0.00096882 · max 15.98614362 BTC
Rate1 BTC = 30596.40976236 NEAR
You receive30596.40976236 NEAR
Limits— BTC
Rate1 BTC = 30522.19980653 NEAR
You receive30522.19980653 NEAR
Limitsmin 0.000019 BTC
Rate1 BTC = 30431.5899 NEAR
You receive30431.5899 NEAR
Limitsmin 0.001446 · max 48.197896 BTC
Rate1 BTC = 30425.38164973 NEAR
You receive30425.38164973 NEAR
Limitsmin 0.00056487 BTC
Rate1 BTC = 30390.20881023 NEAR
You receive30390.20881023 NEAR
Limitsmin 0.00016066 · max 10 BTC
Rate1 BTC = 30299.16015625 NEAR
You receive30299.16015625 NEAR
Limitsmin 0.00078726 · max 10 BTC
Rate1 BTC = 30124.2001 NEAR
You receive30124.2001 NEAR
Limitsmin 0.0016 · max 16.0659 BTC
Rate1 BTC = 30065.24882834 NEAR
You receive30065.24882834 NEAR
Limitsmin 0.0000482 · max 0.16438004 BTC
Rate1 BTC = 29862.36413821 NEAR
You receive29862.36413821 NEAR
Limitsmin 0.00048249 · max 3.61863976 BTC
// rate history · BTC → NEAR
Swapping BTC to NEAR moves capital from the most liquid base asset into a sharded layer-1 built around human-readable accounts and sub-second finality. Skipping KYC keeps the trail off centralized order books and avoids tying your NEAR account to a passport scan - useful if you plan to stake, mint NFTs, use Aurora (NEAR's EVM), or interact with Ref Finance under a fresh wallet that has no link to your BTC history.
// about this pair
What makes BTC -> NEAR specific
Bitcoin and NEAR live on incompatible networks: BTC settles on UTXO with ~10 minute blocks, NEAR uses an account model with ~1.2 second block times and roughly 1 second finality. There is no native bridge in the UX sense - any swap service is doing a custodial or atomic conversion behind the scenes, sending you native NEAR to your account.near or hex implicit address. Liquidity for this pair is deep across aggregators because BTC is the universal input, but NEAR's spread is wider than BTC -> ETH or BTC -> SOL, so quoted rates between providers can vary 1-3% on the same minute.
Typical reasons to make this swap:
- Funding a fresh NEAR wallet for staking (validators pay ~9% nominal, ~5% real after inflation)
- Bridging into Aurora to use EVM dApps with cheaper gas than mainnet Ethereum
- Buying storage stake for contract deployment (NEAR charges ~1 NEAR per 100kb)
- NFT activity on Mintbase or Paras without a CEX paper trail
Choosing a provider for this pair
Check these before committing the BTC send:
- Address format: confirm the service supports both named accounts (
yourname.near) and 64-char implicit addresses. Some only accept implicit. - Rate type: floating rates win on calm days; fixed rates protect you when BTC mempool is congested and confirmation drags past 30 minutes.
- Min / max: NEAR minimums are usually around 0.001 BTC. Large trades (>1 BTC) often trigger manual review even on no-KYC venues - split if needed.
- Refund address: always set a BTC refund address you control. If the rate slips outside tolerance on a fixed quote, funds bounce back there.
Practical tips: send with a fee that confirms in 1-3 blocks to avoid rate-lock expiry, double-check the destination is a NEAR address (not Aurora 0x... unless the service explicitly routes to Aurora), and if you're funding a brand new account, make sure it's already been initialized with the 0.1 NEAR minimum or the swap output will fail to land.
// FAQ
Can I receive NEAR directly to a named account like alice.near?
Most aggregated providers accept named accounts, but some legacy integrations only support 64-character implicit addresses (hex). If your service rejects the named format, generate the implicit address from your wallet's public key, receive there, then transfer to your named account. The transfer costs roughly 0.0001 NEAR in gas.
Is the output native NEAR or wrapped NEAR on Aurora?
By default you get native NEAR on the NEAR mainnet. If you need it on Aurora (NEAR's EVM layer) for DeFi like Trisolaris or Bastion, you must bridge it via the Rainbow Bridge or Aurora's deposit contract after the swap. A few providers route directly to Aurora 0x addresses - verify before sending.
How long does a BTC to NEAR swap actually take?
The bottleneck is Bitcoin confirmations. Most services require 1-2 BTC confirmations (10-20 minutes) before releasing NEAR. The NEAR-side payout itself finalizes in under 2 seconds. Total wall-clock time is typically 15-30 minutes depending on the fee you paid and current mempool conditions.
What happens if BTC price moves during the confirmation wait?
On a floating rate, you receive NEAR at the rate when your BTC confirms - so a 5% BTC pump during the wait reduces your NEAR output by ~5%. On a fixed rate, the quote is locked but only if BTC arrives within the lock window (usually 10-20 minutes). Past that, the service either refunds or recalculates at spot.
Are there amount thresholds that trigger KYC even on no-KYC services?
Yes. Most no-KYC aggregators flag swaps above 0.5-1 BTC for manual AML review, especially if the BTC inputs touch flagged addresses. To avoid friction, keep individual swaps under that threshold, use BTC with clean provenance, and never send from a known mixer output directly into the swap address.
Do I need NEAR in the destination account before the swap arrives?
If the destination is a fresh implicit address with zero balance, the incoming NEAR will create the account automatically as long as the amount exceeds the storage minimum (~0.00182 NEAR). Named accounts must be pre-registered. Sending to a non-existent named account will fail and the provider should refund to your BTC refund address.
// related