12Technical notes

Technical architecture

A high-level view of the Glider Labs architecture behind Glider Ramp.

Product referenceMaintained by Glider LabsUpdated 9 Oct 2026Glider Ramp Revision 2

Glider Labs develops Glider Ramp’s interface, route controls, request validation and transaction-state presentation. Together, these layers carry a swap from configuration and quote review through wallet approval and progress tracking.

InterfaceSwap configurationNetworks · assets · amount · destination

Glider Ramp controlsQuote and validationRoute checks · quote requests · execution preparation

Wallet hand-offAuthorisation requestAccount · balance · transaction checks

StatusProgress trackingSource submission · route state · delivery status

Application state

Glider Ramp tracks the chosen networks, assets, amount, destination, quote and connection state. It distinguishes live quote data from execution data and updates the available action as these conditions change.

Route preparation and validation

Glider Ramp obtains current quote and execution data for the selected swap. It checks network IDs, token addresses, decimals, source amounts, approval targets and destination instructions before presenting a wallet request. Solana and EVM transactions use their own balance and simulation checks. Discovery of a token alone does not make a transaction executable.

Network-family handling

Glider Ramp normalises route selection across EVM, Bitcoin, Solana, TRON and TON while preserving the address, wallet and transaction rules of each network family. This allows one crosschain flow without treating fundamentally different networks as if they behave the same way.

Wallet connectivity

Glider Ramp tracks the connected account, network and signing connection so it can respond to the wallet’s current state. Transaction requests are presented through the connected wallet, where the user reviews and authorises them.

Execution and onchain settlement

After wallet approval, Glider Ramp submits the source transaction through the selected execution flow and follows the available onchain state across source and destination. Glider Ramp distinguishes submission, processing, destination delivery and completion so users can follow the swap without treating a pending update as a completed transaction.

Monitoring and confirmation

Glider Ramp brings transaction and route status into one view. A completed route status and blockchain finality are distinct. Source and destination transaction records provide the context needed to verify delivery.

Published by Glider Labs

Official product documentation for Glider Ramp.

Open Glider Ramp