> For the complete documentation index, see [llms.txt](/llms.txt).

Atlas Bridge is a cross-chain bridge for the Rootstock ecosystem. You can use it to move assets between Rootstock and other supported networks.

- Peg-in means you move assets into Rootstock.
- Peg-out means you move assets out of Rootstock.

## How Atlas fits the stack

Atlas uses three client-side SDKs. Each one opens a different bridge or swap path. Funds end on Bitcoin or Rootstock.

### Architecture diagram

Atlas talks to three client-side SDKs: `@rsksmart/powpeg-sdk`, `@rsksmart/flyover-sdk`, and `@rsksmart/rsk-swap-sdk`. Cross-chain swaps go through `rsk-swap-api` to LiFi, Symbiosis, Boltz, and Changelly. `flyover-sdk` goes to Flyover liquidity providers, then Liquidity Provider Servers (LPS). `powpeg-sdk` goes to Native PowPeg, then `powpeg-api`. LPS, `powpeg-api`, and the swap providers talk to Bitcoin and Rootstock.

```mermaid
flowchart TB
  AtlasUI["Atlas Bridge UI"]

  PowpegSdk["powpeg-sdk<br/>@rsksmart/powpeg-sdk"]
  FlyoverSdk["flyover-sdk<br/>@rsksmart/flyover-sdk"]
  RskSwapSdk["rsk-swap-sdk<br/>@rsksmart/rsk-swap-sdk"]

  PowpegSdk -.- FlyoverSdk
  FlyoverSdk -.- RskSwapSdk

  NativePowPeg["Native PowPeg<br/>Union Bridge (planned)"]
  FlyoverLP["Flyover liquidity providers"]
  SwapApi["rsk-swap-api"]

  PowPegApi["powpeg-api<br/>(2wp-api)"]
  FlyoverLPS["Liquidity Provider Servers<br/>(LPS)"]

  subgraph SwapProviders["Swap providers"]
    direction LR
    LiFi["LiFi"]
    Symbiosis["Symbiosis"]
    Boltz["Boltz"]
    Changelly["Changelly"]
  end

  Networks["Bitcoin and Rootstock"]

  AtlasUI --> PowpegSdk
  AtlasUI --> FlyoverSdk
  AtlasUI --> RskSwapSdk

  PowpegSdk --> NativePowPeg
  FlyoverSdk --> FlyoverLP
  RskSwapSdk --> SwapApi

  NativePowPeg --> PowPegApi
  FlyoverLP --> FlyoverLPS
  SwapApi --> LiFi
  SwapApi --> Symbiosis
  SwapApi --> Boltz
  SwapApi --> Changelly

  PowPegApi --> Networks
  FlyoverLPS --> Networks
  LiFi --> Networks
  Symbiosis --> Networks
  Boltz --> Networks
  Changelly --> Networks

  classDef ui fill:#FCE4F6,stroke:#FF71E1,stroke-width:2px,color:#1a1a1a
  classDef sdk fill:#E0FFFA,stroke:#08FFD0,stroke-width:2px,color:#1a1a1a
  classDef api fill:#EDE7FF,stroke:#9E76FF,stroke-width:2px,color:#1a1a1a
  classDef provider fill:#FFF0D9,stroke:#FF9100,stroke-width:2px,color:#1a1a1a
  classDef network fill:#E8F5D0,stroke:#79C600,stroke-width:2px,color:#1a1a1a

  class AtlasUI ui
  class PowpegSdk,FlyoverSdk,RskSwapSdk sdk
  class SwapApi,FlyoverLPS,PowPegApi api
  class LiFi,Symbiosis,Boltz,Changelly,FlyoverLP,NativePowPeg provider
  class Networks network
  linkStyle 0,1 stroke:none,fill:none
```

`@rsksmart/rsk-swap-sdk` quotes and runs swaps through `rsk-swap-api` (LiFi, Symbiosis, Boltz, Changelly). `@rsksmart/flyover-sdk` talks to Flyover liquidity providers, which use Liquidity Provider Servers (LPS) to reach Bitcoin and Rootstock. `@rsksmart/powpeg-sdk` talks to Native PowPeg, which uses `powpeg-api` (2wp-api) to reach the chains. Union Bridge work is planned for the PowPeg path.

Atlas lets you compare routes before you connect a wallet. To quote and swap from your own app, start with [`@rsksmart/rsk-swap-sdk`](https://github.com/rsksmart/rsk-swap-sdk).

## Prerequisites
You need a wallet for the source network and a wallet address for the destination network. You also need enough balance to cover both transfer amount and fees.

Do not send funds from exchange deposit addresses. Use wallets you control.

## Getting Started
To get started, read [How to use Atlas Bridge](/resources/guides/atlas/getting-started-atlas/). Find and resolve common errors in the [FAQ](/resources/guides/atlas/faq/).

## Integrate with the RSK Swap SDK

[Atlas Bridge](https://atlas.rootstock.io) is the web interface for comparing provider routes before you connect a wallet. To quote and execute swaps from your own wallet, exchange, or dApp, use [`@rsksmart/rsk-swap-sdk`](https://github.com/rsksmart/rsk-swap-sdk). The SDK calls `rsk-swap-api`. That API returns routes from LiFi, Symbiosis, Boltz, and Changelly. Supported pairs and providers come from the API at request time. They can differ from the routes Atlas shows in the UI.

Install the package:

```bash
npm install @rsksmart/rsk-swap-sdk
```

The SDK estimates routes, reads swap limits, broadcasts EVM transactions through your connected wallet, and returns BIP21 or BOLT11 strings for Bitcoin and Lightning steps. Chain IDs identify EVM networks. Pass `BTC` for Bitcoin and `LN` for Lightning. Use `BTC` or `tBTC` to select mainnet or testnet on those networks. See the [RSK Swap SDK repository](https://github.com/rsksmart/rsk-swap-sdk) for setup, examples, and API reference.

### Related SDKs

Atlas also uses these client SDKs for other routes:

- [`@rsksmart/flyover-sdk`](https://github.com/rsksmart/flyover-sdk) for the Flyover liquidity-provider path
- [`@rsksmart/powpeg-sdk`](https://github.com/rsksmart/powpeg-sdk) for native PowPeg and Bitcoin utilities. Union Bridge work is planned to land here.

### Store swap context securely

When you create a swap, the SDK returns a result object with a `context` field. That field holds provider-specific data for claiming or refunding the swap. Some providers include sensitive client-side material in `context`, such as keys for atomic swaps. The SDK generates this data in the browser or your app. It does not send `context` to `rsk-swap-api`.

Persist the full swap result in storage you control. Treat `context` as secret. Do not log it, cache it in plain text, or send it to analytics or support channels unless your runbook requires it.

## Before you bridge
Atlas lets you compare provider routes, amounts, and estimated completion times before you connect a wallet. This helps you choose a route that matches your amount, speed target, and fee tolerance.

### Minimum Transaction Amounts
If Atlas shows no provider for your amount, your amount is often below a provider minimum.

| Provider | Minimum Peg-In | Minimum Peg-Out |
| :--- | :---: | ---: |
| Flyover - Teks | 0.00500001 BTC | 0.004 rBTC |
| Changelly | Equivalent of 30 USD | Equivalent of 30 USD |
| Boltz | 0.00001 BTC | 0.00001 rBTC |
| Native | 0.005 BTC | 0.004 rBTC |

:::tip[Tip]

For some providers, minimums do not include fees. Keep extra balance in the source wallet.
:::

### Mainnet
Available swaps on [Mainnet](https://atlas.rootstock.io/):

- rBTC → BTC (L1)
- BTC (L1) → rBTC
- rBTC → BTC (Lightning)
- BTC (Lightning) → rBTC
- ETH → rBTC
- USDT → rBTC
- USDC → rBTC
- WBTC → rBTC
- BNB → rBTC
- rBTC → ETH
- rBTC → USDT
- rBTC → USDC
- rBTC → BNB
- rBTC → WBTC

### Testnet
Available swaps on [Testnet](https://atlas.testnet.rootstock.io/):

- trBTC → BTC (L1)
- BTC (L1) → trBTC

## Expected Time & Confirmations
Bridging depends on source-chain confirmations and provider processing. Times below are estimates. Actual times vary with network conditions.

| Provider | Peg-In | Peg-Out |
| :--- | :---: | :---: |
| Flyover - Teks | 20m | 20m |
| Flyover - Rootstock | 20m | 20m |
| Changelly | 15m | 15m |
| Boltz | 1m | 5m |
| Native | 17h | 34h |

## Safety checks before confirmation
Use this checklist before you submit:
- Confirm source and destination networks.
- Confirm destination address on the correct chain.
- Confirm amount after fees.
- Keep the transaction hash for support and tracking.

## Where to Get Help
If you run into issues:
- Check the [FAQ](/resources/guides/atlas/faq/) first.
- Use [Rootstock Discord](https://rootstock.io/discord) for community help.
- Contact the team via [Rootstock Contact Us](https://rootstock.io/contact/).

## Resources

- [Get rBTC: Comprehensive Guide to Bridging to Rootstock](https://rootstock.io/blog/get-rbtc-comprehensive-guide-to-bridging-to-rootstock/)
- [Rootstock: the most secure and advanced Bitcoin layer](https://rootstock.io/technology/)
- [rBTC overview](https://rootstock.io/rbtc/)
- [Release Notes](https://github.com/rsksmart/bridge/releases)