Squid Router (squid)

​

Notes

• Built on Axelar GMP — uses Axelar chain name strings for destination (e.g. “ethereum”, “arbitrum”, “Polygon”)
• bridgeCall for simple token bridges; callBridgeCall for swap-then-bridge (includes pre-bridge DEX swaps)
• Same Router address (0xce16F6...) deployed across all supported chains
• bridgedTokenSymbol must match the Axelar-registered symbol for the bridged asset
• The payload parameter enables post-bridge execution on the destination chain
• callBridgeCall’s calls array allows chaining multiple swap steps before the bridge
• Requires ERC-20 approval to the Squid Router address
• Finality: 2-5 minutes (depends on Axelar validator consensus)

​

Its names in a program

function main() {
  // Ethereum's squidRouter, `0xce16F69375520ab01377ce7B88f5BA8C48F8D666`.
  require(Squid.SquidRouter != 0);
}

​

Deployments

​

ABI

​

SquidRouterABI

• bridgeCall(string bridgedTokenSymbol, uint256 amount, string destinationChain, string destinationAddress, bytes payload, address gasRefundRecipient, bool enableExpress) payable
• callBridgeCall(address token, uint256 amount, (uint8 callType, address target, uint256 value, bytes callData, bytes payload)[] calls, string bridgedTokenSymbol, string destinationChain, string destinationAddress, bytes payload, address gasRefundRecipient, bool enableExpress) payable

​

Next steps

• Protocols: the other protocols, by what they do.
• Protocols and tokens: calling a contract by its namespace, or through its ABI.
• Glossary: the words these pages use, in plain terms.