TON → NEAR

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 · 3s

#	Casa de cambio	Puntuación	Historial sin KYC?	Tasa	Recibes (1 TON)	Límites (TON)
1	SideShift MEJOR	C priv 48trust 78	—	1 TON = 0.81581654 NEAR	0.81581654 NEAR	min 1.77534493 · max 6058.79758324		intercambiar en SideShift →
2	StealthEX	C priv 49trust 79	5/5 KYC-free	1 TON = 0.769441 NEAR	0.769441 NEAR	min 0.1406503	intercambiar en notkyc	intercambiar en StealthEX →

SideShift MEJOR C

Tasa1 TON = 0.81581654 NEAR

Recibes0.81581654 NEAR

Límitesmin 1.77534493 · max 6058.79758324 TON

intercambiar en SideShift →

StealthEX C

Tasa1 TON = 0.769441 NEAR

Recibes0.769441 NEAR

Límitesmin 0.1406503 TON

intercambiar en notkyc intercambiar en StealthEX →

Swapping Toncoin to NEAR Protocol means moving from Telegram's TON ecosystem into NEAR's sharded, account-model L1. Both chains settle in seconds with sub-cent fees, so a no-KYC swap here is fast end-to-end - usually under two minutes including confirmations. Common motivations: redeploying TON gains into NEAR DeFi (Ref Finance, Burrow), grabbing NEAR for AI-agent projects on the chain, or accessing Aurora's EVM layer without touching a centralized ramp.

// sobre este par

TON -> NEAR: what makes this pair specific

TON and NEAR are both non-EVM L1s with custom address formats. TON uses workchain-based addresses (often starting with 'EQ' or 'UQ') and a bounceable/non-bounceable distinction that trips up newcomers. NEAR uses human-readable account IDs (yourname.near) alongside 64-character implicit addresses. Neither chain shares signatures or address formats with the other, so this is always a cross-chain swap - no bridging shortcuts, no wrapped-asset tricks.

Liquidity for TON-NEAR is thinner than TON-USDT or NEAR-USDT, so most aggregated routes internally hop through a stablecoin or BTC leg. That is why quoted rates can vary 1-3 percent across providers for the same input amount. Block times work in your favor: TON finalizes in ~5 seconds, NEAR in ~1-2 seconds, so total swap time is bottlenecked by the provider's internal processing, not the chains.

Choosing a route and sizing the swap

Confirm the deposit address type - send a bounceable TON address only if the provider explicitly supports it; otherwise use non-bounceable (UQ...) to avoid stuck funds.
For NEAR receipt, double-check whether the provider accepts named accounts or only implicit addresses.
Check min/max: TON's low unit value means minimums are often 5-10 TON; large orders (>5000 TON) may exhaust a single provider's float.
Prefer fixed-rate quotes for amounts over a few hundred USD - floating rates can drift during NEAR's quick finality window if the provider is slow to credit.
Verify the refund-address field is filled with a TON wallet you control, not the exchange-internal address.

Practical tip: split orders above ~$2000 into two transactions across different providers. This avoids float exhaustion penalties and gives you a real-time A/B on execution quality. Memo/tag fields are not used on either chain for these swaps, but always send a small test amount first if you have not used a particular route before.

// preguntas

Do I need a .near account to receive the swap?

No. Implicit NEAR accounts (64-character hex addresses derived from a public key) work fine and are what most non-custodial wallets generate by default. Named accounts like 'you.near' also work if the provider's address validator accepts them - some only accept implicit format. Check before sending.

Should I send TON from a bounceable or non-bounceable address?

Send from whichever your wallet uses, but the deposit address the provider gives you matters more. Use the non-bounceable form (starts with UQ) when possible. If you send to a bounceable address (EQ) that is uninitialized or rejects the message, TON will return the funds minus fees, which delays the swap.

Why does the rate vary so much between providers for TON -> NEAR?

Direct TON/NEAR order books barely exist on the venues these aggregators use. Most route through USDT or BTC internally, so you are paying two spreads plus the provider's margin. Differences of 1-3 percent on the effective rate are normal. Compare the final NEAR-received amount, not the headline rate.

How long does a TON to NEAR swap actually take?

Both chains have fast finality - TON confirms in roughly 5 seconds, NEAR in 1-2 seconds. Real-world swap time is dominated by the provider's internal processing and risk checks, typically 1-3 minutes. If a swap sits in 'exchanging' status beyond 15 minutes without a hash, contact support with your transaction ID.

Is this swap reportable or traceable?

No-KYC providers do not collect identity, but both TON and NEAR are public ledgers. The on-chain link between your TON sending address and NEAR receiving address is visible to anyone analyzing flows through the provider's hot wallets. If unlinkability matters, use fresh wallets on both sides and avoid reusing addresses.

What happens if I send less than the minimum?

Most providers will either auto-refund to the address listed in the order (minus network fees) or hold the funds pending manual review. This is why filling the refund address field with a TON wallet you actually control is critical - if it is blank or wrong, recovery becomes a support ticket rather than an automatic process.

// relacionados