Supported Networks
CoW Protocol maintains a multi-chain presence across numerous EVM-compatible blockchains. The protocol deploys identical core contracts across all networks using CREATE2 deterministic deployment.Contract Addresses
All core contracts are deployed at identical addresses across all supported networks using CREATE2 deterministic deployment.| Contract | Address |
|---|---|
| GPv2Settlement | 0x9008D19f58AAbD9eD0D60971565AA8510560ab41 |
| GPv2VaultRelayer | 0xC92E8bdf79f0507f65a392b0ab4667716BFE0110 |
| GPv2AllowListAuthentication (Proxy) | 0x2c4c28DDBdAc9C5E7055b4C863b72eA0149D8aFE |
Mainnet Deployments
Ethereum Mainnet
- Chain ID: 1
- Native Token: ETH
- Block Explorer: Etherscan
Gnosis Chain
- Chain ID: 100
- Native Token: xDAI
- Block Explorer: Gnosisscan
- Formerly known as xDAI Chain
Arbitrum One
- Chain ID: 42161
- Native Token: ETH
- Block Explorer: Arbiscan
- Layer 2 optimistic rollup
Optimism
- Chain ID: 10
- Native Token: ETH
- Block Explorer: Optimistic Etherscan
Polygon
- Chain ID: 137
- Native Token: MATIC
- Block Explorer: Polygonscan
BNB Smart Chain
- Chain ID: 56
- Native Token: BNB
- Block Explorer: BscScan
Base
- Chain ID: 8453
- Native Token: ETH
- Block Explorer: Basescan
- Coinbase’s Layer 2
Avalanche C-Chain
- Chain ID: 43114
- Native Token: AVAX
- Block Explorer: Snowtrace
Testnet
Sepolia
- Chain ID: 11155111
- Native Token: SepoliaETH
- Block Explorer: Sepolia Etherscan
- Development and testing infrastructure with identical contract addresses
Integration Guidance
- Select the appropriate network for your use case
- Always verify contract addresses through official channels before integrating
- Configure corresponding RPC endpoints for your target network
- Account for each network’s native token requirements for gas
- Use the correct chain ID when constructing domain separators