> ## Documentation Index
> Fetch the complete documentation index at: https://docs.li.fi/llms.txt
> Use this file to discover all available pages before exploring further.

# Limitations

> Current limitations and constraints of LI.FI Composer.

Composer is actively evolving. This page documents the current limitations so you can plan your integration accordingly.

***

## 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)

Protocols that do not return a token upon deposit are not currently supported by Composer.

### Deposit-Only Protocols

Some supported protocols only support **deposit** via Composer; withdrawals must be performed directly through the protocol's interface. Which protocols are deposit-only varies over time, so check the live [Supported Protocols & Chains](/composer/protocols-and-chains) table — a protocol that exposes only an `enter-position` edge (no `exit-position`) is 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 the `FAILED` 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

<CardGroup cols={2}>
  <Card title="Supported Protocols" icon="list" href="/composer/protocols-and-chains">
    Full list of supported protocols and their capabilities
  </Card>

  <Card title="Error Handling" icon="triangle-exclamation" href="/composer/lifi-api/reference/error-handling">
    Handle Composer errors and failure modes
  </Card>

  <Card title="How It Works" icon="diagram-project" href="/composer/composer-101">
    Understand same-chain vs cross-chain execution
  </Card>

  <Card title="Composer Overview" icon="wand-magic-sparkles" href="/composer/overview">
    What is Composer and why use it
  </Card>
</CardGroup>