Squid Router

Definition:

Squid Router is a cross-chain swap aggregator built on Axelar that enables users to swap any token on one blockchain for any token on a different blockchain in a single transaction — handling source chain DEX routing, token bridging via Axelar’s GMP, and destination chain DEX routing automatically, eliminating the multi-step friction of: “swap on chain A → bridge → swap on chain B” into one click. Squid is the primary consumer-facing application built on Axelar’s cross-chain infrastructure and powers the cross-chain swap functionality embedded in many DApps and wallets via its SDK.


Problem: Multi-Step Cross-Chain Swaps

Traditional cross-chain asset movement requires:

  1. Swap token A for USDC on source chain (DEX)
  2. Bridge USDC from source chain to destination chain (bridge UI)
  3. Wait for bridge confirmation
  4. Swap USDC for token B on destination chain (DEX)

This involves multiple transactions, multiple approvals, multiple waiting periods, and multiple UIs. Any step can fail, leaving the user with intermediate assets.


How Squid Works

Single-transaction cross-chain token routing:

  1. User specifies: “Swap X ETH on Ethereum → Y ARB on Arbitrum”
  2. Squid’s router quotes a path:
    Source chain: ETH → USDC via Uniswap (or best DEX)
    Bridge: USDC via Axelar CCTP or Axelar lock-and-mint
    Destination chain: USDC → ARB via Camelot or best DEX
  3. User signs ONE transaction on the source chain
  4. Squid handles the rest — bridging and destination swap happen automatically
  5. User receives ARB in their destination wallet

Axelar GMP (General Message Passing):

Squid uses Axelar’s message passing to coordinate the destination chain swap: the bridged message contains instructions to swap the bridged token at a specified DEX, not just deliver it bare.


Architecture

Source Chain Contract:

  • Receives the user’s token
  • Swaps to bridge token (USDC or axlUSDC) via source-chain DEX routing
  • Calls Axelar Gateway to send a GMP message with the destination swap instructions

Axelar Gateway:

  • Routes the bridge transfer and GMP message across chains
  • Relayers forward the message and token to the destination chain

Destination Chain Contract:

  • Receives the bridged token and the GMP message
  • Executes the destination DEX swap
  • Delivers final token to the user’s address

If the destination swap fails (slippage exceeded), the user receives the bridged intermediate token (USDC), not nothing — protecting against total loss.


Supported Chains (2024)

Squid supports 60+ chains including:

  • Ethereum, Arbitrum, Optimism, Base, Polygon
  • BNB Chain, Avalanche, Fantom
  • Cosmos chains (via Osmosis and Axelar IBC routing)
  • Solana (partial support via Wormhole integration)

DApp Integration (Squid SDK / Widget)

Squid provides an embeddable cross-chain swap widget:

“`typescript

import { SquidWidget } from “@0xsquid/widget”;

function App() {

return (

<SquidWidget config={{

integratorId: “YOUR_ID”,

defaultChainId: “1”, // source chain

defaultTokenSymbol: “ETH”

}} />

);

}

“`

Many DApps (Osmosis, dYdX, various NFT minting sites) embed the Squid widget to allow users to pay in any token from any chain.


BOOST Mode

Squid’s BOOST mode uses USDC Circle CCTP (Cross-Chain Transfer Protocol) for faster bridging:

  • Standard Axelar bridging: 15–30 min finality
  • CCTP BOOST: 2–5 min finality
  • Available on CCTP-supported chains (Ethereum, Arbitrum, Optimism, Base, Polygon)

Comparison to Alternatives

Protocol Bridge Swap on Both Chains Key Differentiator
Squid Axelar Yes Full any-to-any atomic routing
LI.FI Multiple bridges Yes Bridge aggregator with more bridge options
Rango Exchange Multiple bridges Yes More chain support
Across Protocol Across No (transfer only) Speed optimized for same-token transfers

Related Terms


Sources

Last updated: 2026-04