Networks and assets

Glider Ramp brings supported EVM and non-EVM networks into one crosschain application. Bitcoin, Solana, TRON and TON sit alongside Ethereum, Base, Arbitrum and other supported EVM networks, while PulseChain is available through live inbound and outbound routes.

Crosschain coverage

Supported routes span EVM networks and non-EVM networks including Bitcoin, Solana, TRON and TON. Each can be a source or destination where a live route exists. Not every pair across network families is available at all times.

Eclipse uses its own network through the Solana wallet family. Hyperliquid and Lighter have route-specific account requirements. Lighter requires an existing account. XRP Ledger is not offered as a network. XRP assets may still appear on other supported networks when a route is available.

One Glider Ramp flow across network families

The basic flow remains consistent across supported networks: choose the source and destination, review a live quote, authorise the required wallet action and follow onchain delivery. Glider Ramp adapts the address, wallet and transaction requirements to the selected network family.

Built around live availability

Glider Ramp does not assume that every asset can move between every network at every moment. The selectors show supported networks and assets. A current quote and the execution checks determine whether the selected pair and amount can proceed.

PulseChain

Crosschain swaps into and out of PulseChain are live on supported routes. Native PLS and other available assets use the same core selection, live quote, wallet approval and tracking flow as the rest of Glider Ramp. PulseChain is EVM-compatible and is shown separately in the coverage diagram as a featured integration.

PulseChain assets and routes

The destination selector uses the current supported PulseChain token catalogue. Search by name, symbol or contract address, or scroll through the available assets. Supported inbound sources can reach these destinations without an Ethereum-only restriction. Dedicated bridge assets retain their supported counterpart.

Outbound selections follow the supported source assets and destinations. A token that can be received on PulseChain may not support the exact reverse swap. The direction control explains when a pair is one-way. Changing the source asset can reveal other supported destinations.

Solana and PulseChain

Solana USDC can be selected as a source for supported PulseChain destinations. PulseChain USDC can be sent to Solana USDC. Other PulseChain assets do not automatically gain a Solana return route. The live quote determines availability for the selected pair and amount.

Solana source execution checks the USDC balance, SOL for transaction fees and account rent, the selected recipient and the transaction simulation before requesting a wallet signature. The source and destination addresses belong to different network families.

Finding assets across networks

Crosschain selectors show the available catalogue results and discovered wallet assets. Search by name or address to find additional supported tokens. Catalogue responses can be limited, so an asset absent from the initial list may still be found by searching. Network changes default to the native asset where it is supported. Reversing a supported pair preserves the assets you selected.

Networks and assets stay separate

Glider Ramp separates network selection from asset selection so the source and destination are explicit. This makes it easier to review exactly where a swap begins and where destination delivery occurs.

Availability changes with the route

Minimum amounts, liquidity, network conditions and the selected pair can affect whether a quote is available. Glider Ramp combines configured asset references with live route information. A listed asset does not guarantee that every amount or destination can execute.