Deployments/Contract Addresses
Last updated
Was this helpful?
Last updated
Was this helpful?
When requesting a quote through LI.FI's API, the response contains a transactionData object which has the LiFiDiamond address as to parameter.
Do NOT hardcode this address in your dApp/code as the diamond address varies across different EVM chains.
LI.FI is constantly expanding, both in terms of adding new chains/ecosystems as well as integrating new bridges/protocols.
For a list of all networks our contracts are deployed to (including chainIds, RPC_URLs, etc.), please refer to our file in the smart contract repository .
A list of all deployed-to contract addresses can be found in the folder. For each network there are at least two files:
<networkName>.json: contains a list of the latest contract addresses that are deployed to this network
<networkName>.diamond.json: contains a list of all contracts (facets and periphery) that are currently registered in / supported by the LiFiDiamond of that network.
In case of staging deployments there will also be deployment files containing the prefix .staging. in their name. LiFi does not guarantee to keep staging deployments up-to-date due to fast-changing requirements. Please get in touch with our team if you need a staging deployment.
We also recommend to use Louper for analyzing and interacting with our diamond contracts. Here is a sample link for LiFi's mainnet diamond:
LiFi does not actively maintain any testnet deployments due to the nature of the protocol and the requirement to have external protocols/bridges and tokens properly deployed in order to function properly.
Unit testing is done using forked Foundry tests.
Besides over 40 EVM networks (and counting) LI.FI supports transactions to and from other ecosystems. Currently supported are:
Solana
Bitcoin
more to follow soon