Skip to main content
Each Composer contract has the same address on every chain where it is deployed. Your integration doesn’t need to hardcode them: each compile response carries the addresses it touches. See Addresses from the compile response and the Account model.

Canonical (production)

Served from https://composer.li.quest. The four contracts are deployed on these 38 chains (chain id in brackets), five of them testnets: Ethereum (1), Optimism (10), BSC (56), Gnosis (100), Unichain (130), Polygon (137), Monad (143), Sonic (146), X Layer (196), Fraxtal (252), World Chain (480), HyperEVM (999), Lisk (1135), Pharos (1672), Soneium (1868), Tempo (4217), Megaeth (4326), Robinhood Chain (4663), Mantle (5000), Arc (5042), Base (8453), Plasma (9745), Immutable zkEVM (13371), Mode (34443), Arbitrum (42161), Celo (42220), Avalanche (43114), Ink (57073), Linea (59144), Berachain (80094), Plume (98866), Scroll (534352), Katana (747474), and the testnets Base Sepolia (84532), Arbitrum Sepolia (421614), Arc Testnet (5042002), Ethereum Sepolia (11155111) and OP Sepolia (11155420). GET /chains returns the same list with display names; the SDK wraps it as sdk.getSupportedChains().

Read the addresses from the API

GET /addresses returns the four addresses for every enabled chain, keyed by chain id. Send your API key in the x-lifi-api-key header.
The response is truncated to one chain here. Addresses come back in lowercase. GET /addresses does not list the settlement contract.

Settlement contract (CATValidatorV2)

LI.FI’s settlement service registers an escrow for each continuation.settle node. The escrow is fresh for every compile; read it from settlements[<nodeId>].escrow.address in the compile response. The settlement contract is fixed: Cross-chain flows are served on these 13 chains: Ethereum (1), Optimism (10), BSC (56), Polygon (137), HyperEVM (999), Pharos (1672), Tempo (4217), Robinhood Chain (4663), Arc (5042), Base (8453), Plasma (9745), Arbitrum (42161) and Avalanche (43114). No testnet is served.

Addresses from the compile response

Every POST /compose response carries the addresses an integration touches, and they always match the deployment that produced the calldata. Prefer them over the tables above.
transactionRequest is absent when the compiled program is empty, for example a flow whose only node is a continuation.settle with funding: 'external'. Then every submission is an entry in result.actions, and the escrow funding transfer is the action with purpose: 'fundEscrow'. Both the success and the partial result carry userProxy.