← todas las casas de cambio

AVAX NEAR

tipo de tasa
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 AVAX) Límites (AVAX)
1 OctoSwap MEJOR A priv 87trust 70
// no on-platform swaps yet
1 AVAX = 3.415124 NEAR 3.415124 NEAR min 1017.072285 · max 174355.248819 intercambiar en notkyc intercambiar en OctoSwap →
2 XMRS C priv 61trust 71
6/6 KYC-free
1 AVAX = 3.3468 NEAR 3.3468 NEAR min 14.5296 · max 145296.0406 intercambiar en notkyc intercambiar en XMRS →
3 Baltex D priv 40trust 65 1 AVAX = 3.3392981 NEAR 3.3392981 NEAR min 0.02959249 intercambiar en Baltex →
4 SideShift C priv 48trust 78 1 AVAX = 3.32702918 NEAR 3.32702918 NEAR min 0.4361099 · max 1485.33934556 intercambiar en SideShift →
5 StealthEX C priv 49trust 79
5/5 KYC-free
1 AVAX = 3.3222553 NEAR 3.3222553 NEAR min 0.0293273 intercambiar en notkyc intercambiar en StealthEX →
OctoSwap MEJOR A
Tasa1 AVAX = 3.415124 NEAR
Recibes3.415124 NEAR
Límitesmin 1017.072285 · max 174355.248819 AVAX
Tasa1 AVAX = 3.3468 NEAR
Recibes3.3468 NEAR
Límitesmin 14.5296 · max 145296.0406 AVAX
Tasa1 AVAX = 3.3392981 NEAR
Recibes3.3392981 NEAR
Límitesmin 0.02959249 AVAX
Tasa1 AVAX = 3.32702918 NEAR
Recibes3.32702918 NEAR
Límitesmin 0.4361099 · max 1485.33934556 AVAX
Tasa1 AVAX = 3.3222553 NEAR
Recibes3.3222553 NEAR
Límitesmin 0.0293273 AVAX

Swapping AVAX to NEAR moves you between two high-throughput L1s with very different design philosophies: Avalanche's subnet/C-Chain EVM model versus NEAR's sharded Nightshade architecture and human-readable account names. Most users making this swap are rotating into NEAR ecosystem dApps (Ref Finance, Burrow, Aurora) or rebalancing exposure away from the Avalanche subnet thesis. A no-KYC route keeps the rotation private and avoids exchange withdrawal queues.

// sobre este par

AVAX -> NEAR: what makes this pair specific

AVAX and NEAR are not bridge-compatible in any native sense. AVAX lives on the C-Chain (EVM) or X/P-Chains, while NEAR uses its own non-EVM runtime with WASM-based contracts and named accounts like 'yourname.near'. Aurora exists as an EVM layer on NEAR, but a direct AVAX -> NEAR swap through an aggregator settles to a native NEAR account, not an Aurora address. Both chains finalize fast (sub-2s on AVAX C-Chain, ~1-2s on NEAR), so the rate-lock window matters more than confirmation drag.

Liquidity for this pair is thinner than AVAX -> ETH or AVAX -> SOL. Expect wider spreads on amounts above ~50 AVAX, and check whether the quoted rate is floating or fixed before committing.

Choosing a route

  • Confirm the destination address format - NEAR accepts both 64-char implicit addresses and named accounts; some services reject named accounts.
  • Source network for AVAX should be C-Chain unless explicitly stated; X-Chain deposits will be lost on most routes.
  • Fixed-rate quotes protect you from a NEAR pump mid-swap but cost 0.5-1.5% in spread. Floating rates are cheaper if both chains are calm.
  • Check minimums - NEAR's small unit value means some services set a higher AVAX floor to avoid dust on the output side.
  • Refund address: always provide an AVAX address you control, not an exchange deposit address, in case the swap falls outside the rate window.

Timing tip: AVAX gas spikes during subnet activity and NEAR fees stay near-zero, so network cost is essentially an AVAX-side concern. Batch the swap when C-Chain base fee is low (check Snowtrace) to shave a few cents off the deposit transaction.

// preguntas
Can I send AVAX from the X-Chain or P-Chain for this swap?
No. Almost every aggregator route expects AVAX on the C-Chain (EVM-compatible). Sending from the X-Chain or P-Chain to a C-Chain deposit address requires an internal cross-chain transfer first inside your wallet. If you send directly from X or P, the funds will not be credited and recovery is usually impossible.
Does the swap deliver native NEAR or wrapped NEAR on Aurora?
Native NEAR, in nearly all cases. The output goes to a NEAR Protocol account - either an implicit 64-character hex address or a named account ending in .near. If you specifically want NEAR on Aurora (the EVM layer), you would need a separate bridge step after receiving native NEAR, or a route that explicitly supports Aurora as a destination network.
Why are AVAX -> NEAR rates often worse than AVAX -> ETH or AVAX -> USDT?
Liquidity. NEAR has lower aggregate market depth across CEX order books than ETH or major stablecoins, so swap services route through more hops (often AVAX -> USDT -> NEAR) and pass the spread on to you. For amounts under ~10 AVAX the difference is small; above that, comparing live quotes matters more.
How long does an AVAX -> NEAR swap typically take?
End-to-end usually 3-8 minutes. AVAX C-Chain confirms in seconds, NEAR finalizes in 1-2 seconds, and the bulk of the time is the swap service's internal processing and any intermediate trades. Fixed-rate swaps can take longer if the service waits for additional AVAX confirmations to lock the rate.
Can I use a named NEAR account like myname.near as the destination?
Most services accept named accounts, but a minority only support implicit (hex) addresses. If a route rejects 'myname.near', use the 64-character implicit address from your wallet instead - both control the same balance if the named account was created from that key. Always test with a small amount first if unsure.
Is a fixed or floating rate better for this pair?
Floating is cheaper when both AVAX and NEAR are stable, typically saving 0.5-1.5%. Fixed makes sense if NEAR is rallying or if you are swapping a larger amount where slippage during the deposit confirmation could exceed the fixed-rate premium. For routine rotations under a few thousand dollars, floating is usually fine.
// relacionados