Skip to main content

​
Supported Protocols

Set toToken to the protocol’s vault, staking, or deposit token address and Composer activates automatically. Protocols marked Deposit only must be withdrawn through the protocol’s own interface.

​
Supported Chains

Composer currently supports deposits on the following chains.

​
Example Token Addresses

These are example addresses you pass as toToken to trigger a Composer route.
Vault and market token addresses vary by chain, asset, and strategy. Always verify against the protocol’s own app or documentation before using in production.
ProtocolTokenChainAddressDecimals
MorphoSpark USDC VaultBase (8453)0x7BfA7C4f149E7415b73bdeDfe609237e29CBF34A18
Aave V3aEthUSDCEthereum (1)0x98C23E9d8f34FEFb1B7BD6a91B7FF122F4e16F5c6
EthenasUSDeEthereum (1)0x9D39A5DE30e57443BfF2A8307A4256c8797A349718
Morpho vaults are named after their curator (e.g., Spark, Gauntlet), not after Morpho itself. A vault returning symbol: "sparkUSDC" is a Spark-curated Morpho vault. Browse all Morpho vaults at app.morpho.org.
For any supported protocol, find the correct vault token address in the protocol’s own app or documentation.

​
Requesting a New Protocol Integration

  • The protocol must be on an EVM-compatible chain
  • The protocol must return tokenised positions (e.g., vault tokens, aTokens, LSTs)
See For Protocol Teams or contact the LI.FI team to start the process.

Deposit Recipes

End-to-end deposit recipes for multiple protocols

Withdrawals Guide

Withdrawal patterns for supported protocols

Limitations

Current limitations and constraints