_ stay anonymous. stay free.
← all services

AVAX → NEAR

→
Tier
Trusted Unvetted
sort by
Best rate Most trusted Tier
rate type
Floating Fixed
Market-rate quotes (may change before execution).
root@notkyc:~$ Getting live rates... 0/…
# Exchange Tier ⇅ Score No-KYC record? Rate You receive (1 AVAX) Limits (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.

// about this pair

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.

// FAQ
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.
// related
Best for AVAXBest for NEARAVAX → NEAR calculatorHow to swap BTC → XMRHow to swap ETH → XMR