Why Integrate with Composer
Reach Users on Every Chain
Without Composer, users must manually bridge assets, swap tokens, and navigate to your protocol’s UI. With Composer, any user on any supported EVM chain can deposit into your protocol in one click, directly from wallets, dApps, and aggregators that integrate LI.FI.Distribution Through the LI.FI Ecosystem
LI.FI is integrated into hundreds of wallets, dApps, and DeFi platforms. When your protocol is available via Composer, it becomes accessible through:- LI.FI API — used by integrators building custom DeFi experiences
- LI.FI SDK — TypeScript SDK for frontend and backend applications
- LI.FI Widget — embeddable UI component used by wallets and dApps
Better UX for Your Users
Composer transforms multi-step, multi-chain operations into a single transaction:| Without Composer | With Composer |
|---|---|
| Bridge assets to the right chain | One transaction |
| Swap to the required token | One signature |
| Approve the token | One click |
| Deposit into the protocol | Atomic execution |
Pre-Execution Simulation
Every Composer transaction is simulated before execution, giving users certainty about the outcome before they sign. This reduces failed transactions and improves trust in your protocol.Integration Requirements
To be integrated with Composer, your protocol must meet these requirements:1. EVM-Compatible Chain
Composer currently supports EVM-compatible chains only. Solana and other non-EVM chains are not yet supported.2. Tokenised Positions
Your protocol must return a tokenised position to the user upon deposit. This includes:- Vault tokens (e.g., ERC-4626 vault shares)
- Receipt tokens (e.g., Aave aTokens)
- Liquid staking tokens (e.g., wstETH)
- Yield tokens (e.g., Pendle yield tokens)
3. Standard Deposit Interface
Your protocol’s deposit function should follow standard patterns that Composer’s eDSL compiler can encode. The LI.FI team will work with you to ensure compatibility.Currently Integrated Protocols
The following protocols are already integrated with Composer, demonstrating the range of protocol types supported:| Protocol | Type | Actions |
|---|---|---|
| Morpho V1 and V2 | Lending / Vaults | Deposit, Withdraw |
| Aave V3 | Lending | Deposit, Withdraw |
| Euler | Lending | Deposit, Withdraw |
| Lido wstETH | Liquid Staking | Deposit, Withdraw |
| EtherFi | Liquid Staking | Deposit, Withdraw |
| Pendle | Yield | Deposit, Withdraw |
| Felix Vanilla | Vaults | Deposit, Withdraw |
| HyperLend | Lending | Deposit, Withdraw |
| Neverland | Vaults | Deposit, Withdraw |
| Seamless | Lending | Deposit, Withdraw |
| USDai | Yield | Deposit, Withdraw |
| Kinetiq | Staking | Deposit |
| Kinetiq Earn (vkHYPE) | Yield | Deposit |
| Ethena | Yield | Deposit |
| Maple | Lending | Deposit |
Getting Integrated
Integrations are handled by the LI.FI team. Partner protocols can also be invited to contribute to the Composer backend codebase directly.Apply for Composer Integration
Fill out the protocol integration form to start the process.
- Discord: LI.FI Discord
- Email: partnerships@li.fi
What You Get
Once integrated, your protocol is automatically available to:- All LI.FI API integrators — your vault/staking tokens appear as valid
toTokendestinations - All LI.FI Widget deployments — users can select your protocol’s tokens as destinations
- All LI.FI SDK users — developers can build custom flows targeting your protocol