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

# Stellar Ecosystem Coverage

> Overview of LI.FI's Stellar ecosystem coverage including bridges, DEXs, and key features

LI.FI offers Stellar support with 4 integrated bridges and interoperability between Stellar and 26 chains.

<Note>
  For technical implementation details, see the [Stellar Providers](/introduction/lifi-architecture/stellar-overview) page. For the full list of supported chains, see [Chain Overview](/introduction/chains).
</Note>

***

## Bridges

LI.FI integrates 4 bridges for Stellar connectivity:

Polymer (Fast), Polymer (Standard), Circle CCTP, NearIntents

* **Polymer (Fast)**: USDC transfers into Stellar from 19 EVM chains, settled on Circle's fast attestation.
* **Polymer (Standard)**: The same 19 EVM chains into Stellar, settled on Circle's standard attestation for a lower fee.
* **Circle CCTP**: USDC transfers out of Stellar to 10 EVM chains, including Ethereum, Arbitrum, Base, Polygon, and Avalanche.
* **NearIntents**: Intent-based routing into Stellar from 14 chains, including Ethereum, Solana, Bitcoin, Tron, and major L2s.

<Note>
  Each bridge routes in one direction today. Polymer and NearIntents route **into** Stellar. Circle CCTP routes **out of** Stellar. Same-chain swaps on Stellar are available through Soroswap, and a Soroswap swap can precede a CCTP transfer out, for example XLM to USDC to Base.
</Note>

***

## DEXs

LI.FI integrates 1 DEX aggregator on Stellar:

* **Soroswap**: Aggregates liquidity across Stellar AMMs and splits a trade across venues for the best output. It powers same-chain swaps on Stellar.

***

## Key Features

### Soroban Asset Contract addressing

Every Stellar token, native XLM included, is addressed by its Stellar Asset Contract (SAC) `C...` address. One addressing scheme covers native XLM, wrapped classic assets, and Soroban-native tokens.

### Expiring token allowances

Soroban allowances always carry an expiration ledger. Indefinite approvals do not exist on Stellar, so a route grants only the allowance it needs and that allowance expires by itself.

### Federation addresses

The LI.FI SDK resolves SEP-2 federation addresses (`name*domain.com`) to a `G...` account address before it builds a request.

### Account reserve handling

A route that bridges into Stellar delivers XLM to the receiver and holds back a buffer for the account reserve and for the destination step fees.

### Wallet coverage

The LI.FI Widget connects Freighter, xBull, Lobstr, Rabet, Hana, Klever, OneKey, and Bitget through the [Stellar Wallets Kit](https://github.com/Creit-Tech/Stellar-Wallets-Kit).

***

## Availability

Stellar support is available on the LI.FI API, the [SDK](/sdk/overview), and the [Widget](/widget/overview). Stellar routing runs on the public Stellar network only.

***

## Integration Options

LI.FI's Stellar support is available through all standard integration methods:

* [API](/api-reference)
* [SDK](/sdk/overview)
* [Widget](/widget/overview)