NEAR → SUI

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 = 2.641977 SUI	2.641977 SUI	min 3473.428274 · max 595444.846921	intercambiar en notkyc	intercambiar en OctoSwap →
2	SideShift	C priv 48trust 78	—	1 NEAR = 2.61012668 SUI	2.61012668 SUI	min 1.47827046 · max 5859.56795073		intercambiar en SideShift →
3	XMRS	C priv 61trust 71	6/6 KYC-free	1 NEAR = 2.5891 SUI	2.5891 SUI	min 49.6204 · max 496204.0391	intercambiar en notkyc	intercambiar en XMRS →
4	Baltex	D priv 40trust 65	—	1 NEAR = 2.4896274 SUI	2.4896274 SUI	min 0.10952127		intercambiar en Baltex →

OctoSwap MEJOR A

Tasa1 NEAR = 2.641977 SUI

Recibes2.641977 SUI

Límitesmin 3473.428274 · max 595444.846921 NEAR

intercambiar en notkyc intercambiar en OctoSwap →

SideShift C

Tasa1 NEAR = 2.61012668 SUI

Recibes2.61012668 SUI

Límitesmin 1.47827046 · max 5859.56795073 NEAR

intercambiar en SideShift →

XMRS C

Tasa1 NEAR = 2.5891 SUI

Recibes2.5891 SUI

Límitesmin 49.6204 · max 496204.0391 NEAR

intercambiar en notkyc intercambiar en XMRS →

Baltex D

Tasa1 NEAR = 2.4896274 SUI

Recibes2.4896274 SUI

Límitesmin 0.10952127 NEAR

intercambiar en Baltex →

Swapping NEAR to SUI moves you between two newer L1s with very different architectures: NEAR's sharded Nightshade chain with human-readable accounts, and Sui's object-centric Move-based runtime with parallel execution. Both settle in seconds and cost fractions of a cent, so a no-KYC swap here is usually about repositioning into Sui's DeFi and gaming ecosystem (Cetus, Suilend, NAVI) without touching a centralized account or routing through wrapped assets on Ethereum.

// sobre este par

What makes NEAR -> SUI specific

NEAR and SUI are not bridge-compatible in any native sense. There is no canonical NEAR<>SUI bridge, so every swap is effectively a sell-side disposal of NEAR followed by a buy-side acquisition of SUI on the aggregator's routing layer. That means the rate you see depends heavily on liquidity depth on both legs at the moment of quote, not on a single AMM pool.

Both chains are fast (NEAR ~1.2s finality, Sui ~400ms checkpoint commit) and cheap, so on-chain confirmation is rarely the bottleneck. The slow step is the provider's internal processing and any rate-lock window. Send NEAR to a fresh implicit or named account address; receive SUI to a 0x-prefixed 32-byte address. Sending SUI to a NEAR-style address (or vice versa) is unrecoverable on most providers.

Choosing a provider for this pair

Confirm the deposit network is NEAR mainnet (not Aurora, NEAR's EVM layer - Aurora NEAR is a different asset path).
Check that the SUI payout is on Sui mainnet, not a wrapped SUI on Ethereum or BSC.
Compare floating vs fixed rates: floating usually wins on this pair because both assets are liquid, but fixed protects you if NEAR is mid-move.
Read the refund policy and refund-address field - some providers void refunds if you skip it.
Note min/max: NEAR mins are often ~1-2 NEAR, Sui-side caps depend on hot wallet depth.

Practical tips: split large amounts (>5k USD equivalent) into two transfers to avoid quote slippage on the SUI leg. Avoid swapping during NEAR validator epoch transitions or major Sui protocol upgrades when mempool behavior is irregular. Always verify the receiving Sui address character-by-character - Move addresses have no checksum like EVM EIP-55.

// preguntas

Can I send NEAR from Aurora instead of NEAR mainnet?

No. Aurora is NEAR's EVM-compatible layer and uses a different asset representation. Most aggregators only accept native NEAR from NEAR mainnet accounts. If your NEAR is on Aurora, withdraw it to NEAR mainnet via the Rainbow Bridge or Aurora's native withdrawal first, then initiate the swap.

How long does a NEAR -> SUI swap typically take?

End-to-end usually 3-8 minutes. NEAR finality is ~1-2 seconds and Sui payout confirms in under a second, so most of the time is provider-side: deposit detection, internal routing, and hot-wallet signing. Floating-rate orders can be faster than fixed-rate since they skip the lock-quote handshake.

Do I need to memo or tag the NEAR deposit?

Generally no when using a unique deposit address generated per order. NEAR supports function-call deposits but standard transfers to a fresh implicit address (64-char hex) do not require a memo. Always use the exact address the provider gives you for that specific order - reusing a previous one will likely lose funds.

Why does the rate differ between providers for this pair?

NEAR/SUI is not a directly-quoted pair on most venues. Providers route NEAR -> USDT -> SUI or NEAR -> BTC -> SUI internally, and each hop has its own spread and depth. Differences of 1-3 percent between providers are normal; larger gaps usually indicate one side has stale liquidity or is hedging delay.

Is staked NEAR (stNEAR, LiNEAR) accepted?

Almost never. Liquid-staked NEAR derivatives like stNEAR (Meta Pool) or LiNEAR are separate fungible tokens with their own contracts. Unstake or swap them to native NEAR on a NEAR-side DEX (Ref Finance) before using a cross-chain swap aggregator.

What happens if I send less than the minimum?

Behavior varies: some providers auto-refund minus network fees, others hold the deposit until you top it up to the minimum, and a few mark it as a manual-review case. Always check the stated minimum before sending and include a refund address on the order form to avoid recovery delays.

// relacionados