Current Limitations
EVM Chains Only
Composer supports EVM-compatible chains only, including cross-chain deposits between EVM chains. There is no support for:- Solana
- Other non-EVM chains
Tokenised Positions Only
Composer targets must return a tokenised position to the user. This includes:- Vault tokens (e.g., Morpho vault shares)
- aTokens (e.g., Aave aUSDC)
- Liquid staking tokens (e.g., wstETH, EtherFi tokens)
- Yield tokens (e.g., Pendle yield tokens, sUSDe, vkHYPE)
Deposit-Only Protocols
Some supported protocols only support deposit via Composer. Withdrawals must be performed directly through the protocol’s interface:| Protocol | Limitation |
|---|---|
| Ethena | Deposit only (USDe → sUSDe, ENA → sENA) |
| Kinetiq | Deposit only |
| Maple | Deposit only |
| Royco | Deposit only |
| USDai | Deposit only |
Non-EVM Chains Are Not Supported
Cross-chain Composer deposits work across EVM chains today. Solana and other non-EVM chains are not supported. Cross-chain flows are not fully atomic. Each chain’s phase is atomic within itself, but the overall flow is eventually consistent. In rare cases, a bridge may succeed while the destination deposit fails, leaving the user with tokens on the destination chain rather than deposited into the target protocol. Always implement status polling and handle theFAILED case in your UI.
Simulation Cannot Prevent Every Revert
Composer simulates the full execution path before returning a quote, but the onchain state can change between simulation and execution (e.g., mempool front-running, vault becoming full). In these edge cases, the transaction may revert onchain. Source tokens remain in the user’s wallet (for same-chain), but gas fees are consumed.Related Pages
Supported Protocols
Full list of supported protocols and their capabilities
Error Handling
Handle Composer errors and failure modes
How It Works
Understand same-chain vs cross-chain execution
Composer Overview
What is Composer and why use it