NEAR

Token

Explore NEAR swap routes

Track how NEAR appears across supported send and receive routes, with network-aware paths and non-custodial settlement flows.

NEAR icon

NEAR

NEAR | Layer 1 asset

NEAR · Layer 1 asset

Category: Layer 1 asset

Common role: Ecosystem entry asset

Supported networks: 1

Popular routes: 5

What is NEAR used for in swaps?

NEAR appears in routes where users want to move into, out of, or across the layer 1 asset bucket without relying on a custodial exchange flow.

This hub surfaces the supported networks, the strongest send and receive routes, and the intent patterns that show how NEAR is actually used inside the broader route graph.

NEAR route overview

NEAR route pages are strongest when they explain why this asset appears in certain send and receive flows, which networks support it best, and which related routes users commonly choose next. This hub is designed to surface those patterns rather than show a flat list of links.

Supported networks

Each supported network changes cost, compatibility, and wallet expectations. Use the right rail for the wallet or ecosystem you plan to use next.

Common route patterns

Altcoins into stablecoins

2

Routes that exit a volatile asset into NEAR for a more stable landing asset.

Stablecoins into other ecosystems

2

Routes that push NEAR into another chain or app ecosystem without stopping in a custodial exchange account.

Bitcoin into other ecosystems

1

Routes that move BTC into another ecosystem when users need native settlement on the destination chain.

Start a NEAR swap

Open the live builder, choose the network that matches your wallet, and create the shift from there.

FAQ

What role does NEAR play in swap routes?

NEAR can appear as a send asset, a receive asset, or both depending on whether users are entering its ecosystem, leaving it, or rotating through it as part of a broader route.

Do I need a dedicated NEAR wallet before swapping?

Yes. The destination wallet or address format still needs to match the selected receive network, so the receiving setup should be ready before the route is created.

How do network choices change NEAR swaps?

Network choice changes wallet compatibility, transfer cost, and sometimes memo requirements. That is why this hub highlights the supported network rails rather than treating every NEAR route as interchangeable.

Can I use NEAR in non-custodial swaps without creating an exchange account?

That is the core idea of these routes: the builder sets the pair and network context first, then the shift page handles deposit instructions and status tracking without turning the flow into a custodial exchange workflow.