> For the complete documentation index, see [llms.txt](https://docs.river.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.river.inc/products/editor/bridge.md).

# Bridge

River introduces Omnichain Bridging, enabling users to transfer satUSD seamlessly across multiple blockchains without relying on wrapped assets or liquidity fragmentation. 

Powered by LayerZero’s OFT (Omnichain Fungible Token) standard, this bridge ensures low fees, instant transfers, and unified liquidity across EVM chains, Solana, and Bitcoin Layer 2 networks.

## Supported satUSD Bridge Routes

Here’s a table showing which source chains can bridge satUSD to different destination chains.

| source / destination chain | BOB | BEVM | Bitlayer | BSquared |
| -------------------------- | --- | ---- | -------- | -------- |
| BOB                        | ✅   | ✅    | ❌        | ✅        |
| BEVM                       | ❌   | ✅    | ❌        | ❌        |
| Bitlayer                   | ❌   | ❌    | ✅        | ❌        |
| BSquared                   | ✅   | ❌    | ❌        | ✅        |

## **How the satUSD Bridge Works**

1. **Initiate a Cross-Chain Transfer**
   * Users send satUSD from Chain A (source chain) to Chain B (destination chain).
2. **Burn & Lock Mechanism**
   * On the source chain, satUSD is burned or locked to maintain total supply consistency.
3. **LayerZero Messaging System**
   * A LayerZero cross-chain message is sent, verifying the transaction and triggering the minting process on the destination chain.
4. **Mint & Unlock on the Destination Chain**
   * The same amount of satUSD is minted or unlocked on the destination chain, ensuring a consistent total supply across all chains.

This trustless and decentralized process allows satUSD to move freely across chains without third-party bridges, wrapped tokens, or liquidity pools.

## **Key Features of the satUSD Bridge**

* **Omnichain Transfers**: Move satUSD natively across supported blockchains.
* **No Wrapped Assets**: Eliminates the risks of wrapped token depegging.
* **Unified Liquidity**: satUSD maintains a single, consistent total supply across chains.
* **Low Fees & Fast Settlement**: Transactions are efficient and cost-effective, with minimal slippage.
* **Decentralized & Secure**: Powered by LayerZero’s infrastructure, ensuring trustless execution.

## **LayerZero: The Backbone of satUSD Bridging**

River leverages **LayerZero’s cross-chain interoperability technology** to enable secure and instant bridging:

* **OFT Standard**: Facilitates **seamless satUSD transfers** without requiring external liquidity providers.
* **Cross-Chain Messaging**: LayerZero’s **\_lzSend and \_lzReceive functions** handle omnichain transactions **securely and efficiently.**
* **Burn & Mint Mechanism**: Ensures that satUSD’s total supply remains **synchronized across all integrated chains.**

## **Why This Changes the Game**

* **Solving Fragmented Liquidity** → Unified satUSD supply across all chains, eliminating isolated liquidity pools.
* **Maximizing BTC Utility** → Use satUSD for DeFi, payments, and staking across different ecosystems without friction.
* **Future-Proof Interoperability** → Built for a multi-chain world, supporting EVM, Solana, and Bitcoin Layer 2 ecosystems.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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.river.inc/products/editor/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.