Current Limitations
EVM Chains Only
Composer currently supports EVM-compatible chains only. 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 |
|---|---|
| Kinetiq | Deposit only |
| Kinetiq Earn (vkHYPE) | Deposit only |
| Ethena | Deposit only (USDe → sUSDe, ENA → sENA) |
| Maple | Deposit only |
Cross-Chain Atomicity
- Same-chain Composer transactions are atomic: all steps succeed or all revert
- Cross-chain Composer flows are eventually consistent: each phase (source chain and destination chain) is atomic within its chain, but the overall flow is not atomic across chains
- In rare cases, a cross-chain flow may partially complete (e.g., bridge succeeds but destination deposit fails), leaving the user with tokens on the destination chain
Pre-Execution Simulation
Composer simulates the full execution path before returning a quote. While this prevents most failed transactions, edge cases exist:- Rapid state changes between simulation and execution (e.g., mempool front-running)
- Protocol state changes (e.g., vault becomes full between simulation and execution)