Frequently Asked Questions (FAQs)
What is Atlas Bridge?
Atlas Bridge is a cross-chain bridge for Rootstock. It helps you move supported assets between Rootstock and other supported networks.
- Peg-in means you move assets into Rootstock.
- Peg-out means you move assets out of Rootstock.
Which networks and assets does Atlas support?
Support depends on provider availability and network conditions. Check the current supported pairs in the Atlas interface and in the Atlas guide.
What is rBTC?
rBTC is the Bitcoin-pegged native asset on Rootstock. You use it for gas and dApp interactions on Rootstock.
Is my BTC safe when using Atlas Bridge?
BTC bridged through Rootstock-native routes uses the PowPeg mechanism. Third-party routes have their own trust and risk model. Always review provider details before you confirm a transaction.
How long does the bridging process take?
The process depends on confirmations and provider processing time. It can take minutes or hours depending on route and network load.
| Provider | Peg-In | Peg-Out |
|---|---|---|
| Flyover - Teks | 20m | 20m |
| Flyover - Rootstock | 20m | 20m |
| Changelly | 15m | 15m |
| Boltz | 1m | 5m |
| Native | 17h | 34h |
Why do I need to wait for Bitcoin confirmations?
Bitcoin confirmations reduce reversal risk before assets are released on the destination side. This step is required.
Can I send BTC from an exchange?
No. You should only send BTC from a wallet you fully control. Sending BTC from an exchange may result in loss of funds.
What wallets are supported?
You need:
- A Bitcoin wallet you control to send BTC
- A Rootstock-compatible wallet (e.g., MetaMask configured for Rootstock) to receive and use rBTC
Always follow the bridge UI instructions for supported wallets.