LI.FI (lifi)

​

Notes

• LI.FI is a bridge aggregator — it routes through underlying bridges (Across, Stargate, Hop, cBridge, etc.)
• Uses a Diamond proxy pattern (EIP-2535)
• The Diamond address is the same on every chain but Arc, whose address differs
• Uses standard EVM chain IDs for destinationChainId
• The bridge field in BridgeData specifies which underlying bridge to use
• hasSourceSwaps / hasDestinationCall enable swap-then-bridge or bridge-then-execute patterns
• Requires ERC-20 approval to the LiFi Diamond address
• Finality depends on the underlying bridge selected (varies from 1 minute to 20 minutes)

​

Its names in a program

function main() {
  // Ethereum's lifiDiamond, `0x1231DEB6f5749EF6cE6943a275A1D3E7486F4EaE`.
  require(Lifi.LiFiDiamond != 0);
}

​

Deployments

​

ABI

​

LiFiDiamondABI

• startBridgeTokensViaAcrossV4((bytes32 transactionId, string bridge, string integrator, address referrer, address sendingAssetId, address receiver, uint256 minAmount, uint256 destinationChainId, bool hasSourceSwaps, bool hasDestinationCall) bridgeData, (bytes32 receiverAddress, bytes32 refundAddress, bytes32 sendingAssetId, bytes32 receivingAssetId, uint256 outputAmount, uint128 outputAmountMultiplier, bytes32 exclusiveRelayer, uint32 quoteTimestamp, uint32 fillDeadline, uint32 exclusivityParameter, bytes message) acrossData) payable
• extractBridgeData(bytes data) pure returns ((bytes32 transactionId, string bridge, string integrator, address referrer, address sendingAssetId, address receiver, uint256 minAmount, uint256 destinationChainId, bool hasSourceSwaps, bool hasDestinationCall) bridgeData)

​

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.