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

# Bridge

## Scala Network Bridge Guide <a href="#id-9-scala-network-bridge-guide" id="id-9-scala-network-bridge-guide"></a>

The Scala Network Bridge facilitates seamless, bidirectional asset transfers between the native **Scala Network** and three major ecosystems: **Solana (SOL)**, **Ethereum (ETH)**, and **Binance Smart Chain (BSC)**.  This process allows users to **wrap** native **XLA** into **wXLA** (Wrapped XLA) for use on external chains, and **unwrap** wXLA back to native XLA on the Scala Network. <br>

<figure><img src="/files/zx7vxhUJBVMbScikLjJy" alt=""><figcaption></figcaption></figure>

### What is a Bridge and Why Do You Need It? <a href="#id-11-what-is-a-bridge-and-why-do-you-need-it" id="id-11-what-is-a-bridge-and-why-do-you-need-it"></a>

Imagine the world of cryptocurrency as a collection of separate islands. Each island (like **Ethereum**, **Solana**, or **BNB Chain**) has its own unique rules, currency, and shops (apps).  Normally, you cannot take your money from one island and spend it on another; you are stuck where you started.&#x20;

A **crypto bridge** acts as a secure ferry or tunnel connecting these islands.  It allows you to move your value from one network to another without selling your assets or using a centralized bank.&#x20;

#### How It Works (The "Locked Box" Concept) <a href="#id-11-how-it-works-the-locked-box-concept" id="id-11-how-it-works-the-locked-box-concept"></a>

When you use a bridge to move assets (like **XLA**) from the **Scala Network** to another chain (like **Ethereum**):

1. **Lock**: The bridge takes your native **XLA** and locks it in a secure digital vault on the Scala Network.
2. **Mint**: Once the lock is confirmed, the bridge creates an equal amount of **Wrapped XLA (wXLA)** on the destination chain.&#x20;
3. **Result**: You now have **wXLA** on Ethereum that behaves exactly like a native Ethereum token, even though the original **XLA** is safely sitting on Scala.  The value remains **1:1**.

When you want to go back, you "burn" (destroy) the **wXLA**, and the bridge unlocks your original **XLA** on the Scala Network.

#### Unlocking DEXs and dApps <a href="#id-11-unlocking-de-xs-and-d-apps" id="id-11-unlocking-de-xs-and-d-apps"></a>

The primary reason to use a bridge is to access **Decentralized Exchanges (DEXs)** and other **Decentralized Applications (dApps)** that don't exist on your home network.&#x20;

* **Access New Markets**: Suppose a popular trading platform or a high-yield savings protocol only exists on **Ethereum**. Without a bridge, your **XLA** on Scala is useless there.  By bridging to **wXLA**, you can instantly trade, lend, or earn interest on that Ethereum platform.&#x20;
* **One Wallet, Many Worlds**: You don't need to create new accounts. Your single wallet address works across these connected networks. The bridge simply allows your assets to "travel" to where the best opportunities are.&#x20;

In short, bridges turn isolated islands into a connected global economy, letting you use your XLA anywhere in the crypto world.&#x20;


---

# 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://wiki.scalaproject.io/applications/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.