Skip to main content
LI.FI Composer enables users to deposit into your protocol from any token on any EVM chain in a single transaction. This page explains why you should integrate and how the process works.

​
Why Integrate with Composer

​
Reach Users on Every Chain

Without Composer, users must navigate to your protocol’s UI and sign multiple transactions. With Composer, users can deposit into your protocol in one click, directly from wallets, dApps, and aggregators that integrate LI.FI, including from any other EVM chain.

​
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 ComposerWith Composer
Bridge assets to the right chainOne transaction
Swap to the required tokenOne signature
Approve the tokenOne click
Deposit into the protocolAtomic 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)
Protocols that do not return a token upon deposit are not currently supported.

​
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

20+ protocols are already integrated with Composer, spanning lending, liquid staking, yield, and vault strategies.

Supported Protocols

View the full list of integrated protocols, supported actions, and example token addresses.

​
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.
You can also reach out directly: For detailed technical requirements, see Technical Requirements.

​
What You Get

Once integrated, your protocol is automatically available to:
  • All LI.FI API integrators: your vault/staking tokens appear as valid toToken destinations
  • 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
No additional work is required from your side after integration. LI.FI handles the routing, bridging, swapping, and deposit execution.

​
Next Steps

Technical Requirements

Detailed technical requirements for integration

Composer Overview

Learn how Composer works

How It Works

Architecture deep-dive

Limitations

Current constraints and supported chains