# Bridge between chains

Need SOL on BSC, or USDC on Solana? Ayebot bridges between the two chains directly from chat. No browser tabs, no signature pop-ups in five different apps, no guessing which route is cheapest.

## How it works

1. **Pick the source chain and token** — what you want to move.
2. **Pick the destination chain and token** — what you want to receive.
3. **Set the amount.**
4. **The bot quotes the full cost** — bridge fee, on-chain gas on both sides, expected slippage.
5. **You confirm.** The funds leave the source chain immediately.
6. **You get a notification** the moment they land on the destination chain.

Most transfers complete in **2 to 10 minutes**, depending on chain congestion.

## What you see in the quote

Before you sign, the bot lays out:

* Source chain gas (the fee to send out of Solana or BSC)
* Bridge fee (the third-party bridge or aggregator cut)
* Expected slippage on the receive side
* **Net amount on destination** — the number you actually care about

If the route is unhealthy (insufficient liquidity, dead bridge), the bot tells you and suggests a smaller size or an alternative pair.

## Supported routes

Major liquid tokens on both chains:

* **Solana → BSC** — SOL, USDC, USDT, plus the most liquid memecoins
* **BSC → Solana** — BNB, USDC, USDT, plus the most liquid BSC tokens

The bot only quotes routes that are actually live right now. You'll never see a "ghost" option that fails at execution time.

## Minimum amounts

Bridging tiny amounts isn't economical — the fixed bridge fee eats the transfer. Minimum thresholds:

* **$5-$10 equivalent** for stablecoin pairs
* **Slightly higher for volatile pairs** to absorb the slippage cushion

The bot tells you the live minimum for the route you're picking, before you confirm.

## Common commands

```
/bridge         Open the bridge wizard
/bridges        List your recent bridge transactions
```

## What if a transfer is delayed?

Bridge timing depends on the underlying provider. Most complete in 2-10 minutes. If a transfer takes longer than expected:

* The bot keeps the operation in **pending** state and shows live status.
* You'll get a Telegram notification the moment funds land.
* If funds don't arrive within the route's documented SLA, contact [@ayebot\_support](https://t.me/ayebot_support) with the bridge ID and we'll investigate.

{% hint style="info" %}
**Funds are never lost in flight.** A bridge transfer is always either on the source chain (not yet sent) or on the destination chain (received). Worst case is a delay, not a loss.
{% endhint %}

## FAQ

**How long does a transfer take?**\
Most complete in 2 to 10 minutes. The bot pings you the moment funds arrive on the destination chain.

**Is there a minimum amount?**\
Yes — usually $5 to $10 worth, depending on the route. The bot tells you upfront.

**Which tokens can I bridge?**\
Major liquid tokens on both Solana and BSC. The bot only quotes routes that are actually available right now.

**Can I bridge to a different wallet address?**\
By default, the destination is your own Ayebot wallet on the other chain. Sending to an external address is currently not supported through the bridge wizard — withdraw on the source chain first, then send manually.

## What to read next

* [Multi-chain swap](/trading/multichain-swap.md) — once your funds are on the destination chain, trade them
* [Self-custody](/wallet-and-security/self-custody.md) — your wallet works on both chains by default


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ayebot.io/trading/bridge.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.