Contracts

Squid deploys router contracts on every supported EVM chain. Most chains share the same contract address, but some newer chains use a different deployment.

Dynamic Lookup: You can always retrieve the correct contract address for any chain programmatically using the /v2/sdk-info or /v2/chains endpoints. Each chain object includes a squidContracts.squidRouter field with the correct router address.

Mainnet

SquidRouter — Primary

Used on the majority of EVM chains:

Chain	Address
All (default)	0xce16F69375520ab01377ce7B88f5BA8C48F8D666
Blast	0x492751eC3c57141deb205eC2da8bFcb410738630
Fraxtal	0xDC3D8e1Abe590BCa428a8a2FC4CfDbD1AcF57Bd9

SquidRouter — Alternate

The following chains use an alternate router address:

Address	0x2B4d4Cf15dAD79D3426D19674Bd237C1dc9144aa

Chain	Chain ID
Berachain	80094
Citrea	4114
Gnosis	100
Hedera	295
HyperEVM	999
Mantra	5887
Monad	143
Peaq	3338
SagaEVM	5464
Soneium	1868
Sonic	146
Tempo	4217

Always use the contract address returned by the API for the chain you are targeting. Do not hardcode router addresses — use the /v2/sdk-info or /v2/chains endpoint to fetch the correct squidContracts.squidRouter dynamically.

How to look up the router address

API

curl -H "x-integrator-id: YOUR_ID" \
  "https://v2.api.squidrouter.com/v2/chains?chainId=295" | jq '.chain.squidContracts.squidRouter'

SDK

SquidMulticall

0xaD6Cea45f98444a922a2b4fE96b8C90F0862D2F4