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

# Smart Deposit Addresses

> A swap, bridge, or vault deposit completed with a single token transfer to a unique deposit address. No approval, no router transaction.

Smart Deposit Addresses let a user complete a swap with a single token transfer to a unique deposit address. There's no approval and no router transaction to sign.

The same mechanism now covers more than a same-chain swap: cross-chain routes, Solana and Bitcoin as source chains, deposits that end inside a yield vault, and composed routes into tokens no single bridge reaches. What the sender does never changes. They send a transfer.

## The problem

The standard swap flow asks the user to sign twice: an ERC-20 approval, then the router transaction. That means approval-management UX, extra gas, and a drop-off point where users abandon the flow. For custodial and exchange-style products that can only send a plain transfer, approve-and-execute doesn't fit at all.

## How LI.FI solves it

LI.FI derives a unique deposit address for the trade. The sender transfers the input tokens to that address with an ordinary transfer, and LI.FI executes the swap from there and delivers the output to the recipient. If the trade can't complete under the supported flow, LI.FI returns the funds to the configured sender/refund address.

|                              | Standard flow                     | Smart Deposit Addresses |
| ---------------------------- | --------------------------------- | ----------------------- |
| Signatures                   | Approval, then router transaction | A single transfer       |
| Approval UX                  | Managed by your app               | None                    |
| Fits a transfer-only product | No                                | Yes                     |

## What you see as an integrator

* **Standard quote and route flow.** When Smart Deposit Addresses are enabled for your integrator key, the option appears in routing. The returned step is a plain transfer to the deposit address, with no approval step.
* **Status by deposit address.** Track the trade using the deposit address rather than a source transaction hash. Query the status endpoint with the deposit address and its source chain:

```bash curl theme={"system"}
GET /v1/status?depositAddress={address}&fromChain={chainId}
```

A response while the trade is in flight looks like this:

```json theme={"system"}
{
  "status": "PENDING",
  "substatusMessage": "Waiting for funds to arrive at the deposit address."
}
```

The `status` moves through `PENDING` to `DONE` once execution completes, or to `FAILED` if the trade could not complete and the funds were returned.

<Note>
  Query `depositAddress` together with `fromChain`. Use this in place of a transaction hash when tracking a deposit-address trade.
</Note>

## Supported networks

| Network         | As source                         | As destination                                          |
| --------------- | --------------------------------- | ------------------------------------------------------- |
| Ethereum        | Yes                               | Yes                                                     |
| Arbitrum        | Yes                               | Yes                                                     |
| Base            | Yes                               | Yes                                                     |
| Optimism        | Yes                               | Yes                                                     |
| Polygon         | Yes                               | Yes                                                     |
| BSC             | Yes                               | Yes                                                     |
| Avalanche       | Yes                               | Yes                                                     |
| Plasma          | Yes                               | Yes                                                     |
| Tempo           | Yes                               | Yes                                                     |
| Robinhood Chain | Yes                               | Yes, including tokenized stocks through composed routes |
| Solana          | Yes, one signature, any SPL token | Yes                                                     |
| Bitcoin         | Yes, in beta                      | Not supported                                           |

<Note>
  Coverage moves. If the network you need isn't listed, ask your LI.FI contact rather than assuming it's unavailable: a large set of further chains is already assessed and can be scheduled on request.
</Note>

## Supported routes

| Route                    | Notes                                                                                                                       |
| ------------------------ | --------------------------------------------------------------------------------------------------------------------------- |
| Same-chain swaps on EVM  | The original flow.                                                                                                          |
| EVM to EVM, cross-chain  |                                                                                                                             |
| EVM to Solana            |                                                                                                                             |
| Solana to EVM            | One signed Solana transaction. Native SOL or any SPL token as the source.                                                   |
| Bitcoin to EVM           | Beta, enabled per integrator.                                                                                               |
| Vault deposits           | The journey ends inside a curated ERC-4626 yield vault rather than at a token balance.                                      |
| Composed routes          | Long-tail tokens that no single bridge reaches, including tokenized stocks.                                                 |
| Amount-flexible deposits | Deposit any amount at or above a dynamic minimum, at a rate held for 24 hours. Cross-chain routes only, opt-in per request. |

## Token support

| Supported                                   | Where                                       |
| ------------------------------------------- | ------------------------------------------- |
| ERC-20 to ERC-20                            | Every live route                            |
| Native SOL and any SPL token                | As the source, through the Solana lane      |
| SPL tokens                                  | As the destination                          |
| ERC-4626 vault shares                       | As the destination                          |
| Tokenized stocks and other long-tail tokens | As the destination, through composed routes |

<Warning>
  Native EVM tokens such as ETH and BNB aren't supported as the input, and neither are tokens that tax transfers. The expected sender and refund address is required on the quote request.
</Warning>

## How the deposit address behaves

* Each quote gets a unique, single-use deposit address, valid for 24 hours.
* Failed executions and expired deposits are refunded to the sender automatically, with LI.FI covering the gas.
* Multiple deposits to the same address accumulate and execute cumulatively.

## Availability

Smart Deposit Addresses are an enterprise feature, enabled per integrator. The Solana lane is gated separately, on its own list, so being enabled for the EVM routes doesn't enable Solana. Ask for it by name.

<Card title="Contact the LI.FI team to enable" icon="envelope" href="https://li.fi/contact-us/">
  Tell us your chains and the flow you want to support. We confirm coverage and enable Smart Deposit Addresses for your integrator key.
</Card>
