← all services

SUI NEAR

rate type
Market-rate quotes (may change before execution).
root@notkyc:~$ rates cached for everyone · ttl 60s · 0s
# Exchange Score No-KYC record? Rate You receive (1 SUI) Limits (SUI)
1 OctoSwap BEST A priv 87trust 70
// no on-platform swaps yet
1 SUI = 0.373336 NEAR 0.373336 NEAR min 9244.585314 · max 1584786.053883 swap on notkyc swap on OctoSwap →
2 XMRS C priv 61trust 71
6/6 KYC-free
1 SUI = 0.3661 NEAR 0.3661 NEAR min 132.0655 · max 1320655.0449 swap on notkyc swap on XMRS →
3 SideShift C priv 48trust 78 1 SUI = 0.36565007 NEAR 0.36565007 NEAR min 3.96254084 · max 13515.13429498 swap on SideShift →
4 Baltex D priv 40trust 65 1 SUI = 0.3220113 NEAR 0.3220113 NEAR min 0.29100696 swap on Baltex →
OctoSwap BEST A
Rate1 SUI = 0.373336 NEAR
You receive0.373336 NEAR
Limitsmin 9244.585314 · max 1584786.053883 SUI
Rate1 SUI = 0.3661 NEAR
You receive0.3661 NEAR
Limitsmin 132.0655 · max 1320655.0449 SUI
Rate1 SUI = 0.36565007 NEAR
You receive0.36565007 NEAR
Limitsmin 3.96254084 · max 13515.13429498 SUI
Rate1 SUI = 0.3220113 NEAR
You receive0.3220113 NEAR
Limitsmin 0.29100696 SUI

Swapping SUI to NEAR moves you between two high-throughput L1s with different design philosophies: Sui's object-centric model with parallel execution, and NEAR's sharded architecture with human-readable account names. Both settle in roughly 1-2 seconds with sub-cent fees, so this pair is popular for users rotating between Move-based and Rust-based ecosystems, chasing yield differentials, or consolidating into NEAR to use BOS components, Aurora EVM, or chain signatures without touching a centralized venue or KYC gate.

// about this pair

SUI -> NEAR: what makes this pair specific

SUI and NEAR live on completely separate, non-EVM networks. There is no bridge-native path here - any swap is effectively a sell-side liquidation of SUI on one venue and a buy-side fill of NEAR on another, abstracted behind a single quote. That has implications: the rate you see bundles two order books plus the routing spread, and large sizes can suffer slippage on the SUI leg since SUI's CEX depth is generally thinner than majors like SOL or ETH.

Both chains finalize fast and cost fractions of a cent, so on-chain timing is rarely the bottleneck. The bottleneck is the aggregator's rate-lock window and the SUI deposit confirmation count. NEAR addresses can be either implicit (64-char hex) or named (yourname.near) - both are valid destinations, but double-check format support before sending.

Choosing a route and sizing the swap

When comparing quotes for this pair, focus on:

  • Float vs fixed rate: fixed protects you during SUI volatility but charges 1-2% premium; float gives better mid-market but can drift if the SUI leg confirms slowly
  • Minimum and maximum bounds - SUI mins are usually denominated in SUI tokens, NEAR maxes in NEAR; verify both legs
  • Refund address policy: always set a SUI refund address you control, since stuck deposits below minimum are common with low-decimal sends
  • Whether the route supports named NEAR accounts or only implicit addresses

Practical tips: split swaps above ~5,000 USD equivalent into two tranches to reduce slippage on the SUI sell side. Avoid swapping during major SUI unlock events (check the vesting schedule) when sell pressure widens spreads. Send a small test transaction first if the destination is a fresh NEAR account - implicit accounts only become 'real' after first deposit, and some wallets handle this inconsistently.

// FAQ
Is there a direct bridge between Sui and NEAR?
No native bridge exists between Sui and NEAR as of now. Aggregator swaps work by routing through liquidity venues that hold both assets - you send SUI, the service sells it and delivers NEAR to your address. This is faster and cheaper than the multi-hop bridge paths you would otherwise need (SUI -> Wormhole -> ETH -> Rainbow Bridge -> NEAR).
How long does a SUI to NEAR swap take?
Typically 2 to 10 minutes end-to-end. SUI finality is sub-second but most services wait for several checkpoint confirmations (usually 30-60 seconds). The NEAR payout itself confirms in 1-2 seconds. The bulk of the wait is the internal trading leg and any compliance screening the venue applies before releasing funds.
Can I send to a named NEAR account like myname.near?
Most aggregator routes accept named accounts, but some only validate 64-character implicit addresses. If your quote rejects a .near address, use the implicit hex address from your wallet instead - funds are equivalent and you can move them inside NEAR afterward at near-zero cost. Always copy-paste; named accounts are case-sensitive in some clients.
Why does the rate differ so much between providers?
Three factors: depth of SUI order books on the venue's backend exchange, whether they quote fixed (with a risk premium) or float, and routing fees. SUI has lower aggregate liquidity than top-10 assets, so spreads vary more. Comparing live quotes on this page surfaces the cheapest current path rather than locking you into one provider's spread.
What happens if SUI price moves while my deposit is confirming?
On a fixed-rate quote, you receive the locked NEAR amount regardless of price movement, as long as you sent within the deposit window (usually 10-30 minutes) and within the stated min/max. On a float quote, the final NEAR amount is recalculated when your SUI confirms - you benefit from upside but absorb downside. Pick fixed if SUI is volatile that hour.
Do I need a NEAR account funded with storage to receive tokens?
For native NEAR, no - receiving NEAR itself creates or tops up the account. For NEP-141 tokens (like USDC on NEAR) the receiving account needs storage staked, but that is not relevant to this pair since you are receiving native NEAR. A fresh implicit address works directly.
// related