Wallets and destination addresses

Wallet connection gives Glider Ramp the account and network information needed for the selected route. Signing remains a separate action in your wallet.

Connection and approval

Connecting a wallet does not itself transfer assets. It allows Glider Ramp to read the public account information available through that connection and request transactions. Review token permissions as well as transfer requests before approving them.

Source network

The network selected in Glider Ramp can differ from the network currently active in your wallet. Check both before signing and follow the network guidance shown by Glider Ramp. A connected account alone does not establish that the selected route is ready to execute.

Two connection controls

The small Connect control manages your EVM wallet. The main action connects the wallet family required by the selected source, such as Bitcoin, Solana, TRON or TON. Both connections can remain available for a crosschain route.

Network-family requirements

Wallet and address requirements vary by network family. Glider Ramp presents the connection and destination fields required for the selected source and destination. Confirm the address format and wallet request before continuing.

Destination address

Where supported, use your connected wallet as the recipient or enter another destination address. Match the address to the destination network. The recipient address is not the asset’s token contract. Review the destination network and receiving address in swap settings. The source wallet signs the transfer. A receiving wallet does not have to be connected when a valid address is supplied.

Connection appears out of date

If your wallet is open but Glider Ramp still asks you to connect, check for an outstanding wallet prompt and use Connect once. For supported desktop browser wallets, Connect can attempt to re-establish an existing authorised connection. If needed, follow the normal wallet connection prompts.

Existing mobile sessions can retain the networks approved when the session was created. If the required network is missing, a user-initiated disconnect and reconnection may be needed. Check any pending transaction before reconnecting.

Disconnecting

Disconnecting clears Glider Ramp’s active connection state. It does not cancel a submitted transaction or revoke token allowances already recorded onchain.