# Getting Started

{% hint style="success" %}
MineBridge is a **triple-audited** permissionless bi-directional bridge for Runes (Bitcoin native tokens) between Bitcoin and other L1 chains. Currently MineBridge supports bridging between **Bitcoin, Solana and NEAR**. More chain expansions, starting with EVM chains, are coming soon.&#x20;
{% endhint %}

This page will help you prepare everything you need before using the bridge for the first time.

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

### 🟄 What is MineBridge?

MineBridge allows you to move tokens securely across chains in all directions.

* You can take **Runes (Bitcoin-native tokens)** and bridge them into ecosystems like Solana or NEAR, where they can be traded, staked, or used in DeFi.
* You can also take **Solana or NEAR tokens** and bridge them back to **Bitcoin**, where they are etched immutably as Runes and integrated into the Bitcoin ecosystem.

The bridge is **non-custodial and permissionless**. You remain in control of your wallets at all times, and all transactions are final once confirmed.

### 🟄 What You’ll Need

Before you can use MineBridge, make sure you have the following in place:

#### 1. A Bitcoin wallet that supports Runes

You will need a Bitcoin wallet that is compatible with the Runes protocol. This is where your Rune tokens are held if you are bridging *from Bitcoin*, and where they will arrive if you are bridging *to Bitcoin*.

* Commonly used wallets include **Xverse** *(Recommended)*, **Leather, Unisat** and **Magic Eden Wallet.**
* Ensure that your wallet has a balance of BTC to cover transaction fees.

#### 2. A wallet on the destination chain

MineBridge supports both directions, so your “destination” may be Bitcoin, Solana, or NEAR depending on the transaction.

* **If you are bridging from Bitcoin → Solana/NEAR**: you will need a wallet on the target chain such as **Phantom** or **Backpack** (Solana), or a **native NEAR account**.
* **If you are bridging from Solana/NEAR → Bitcoin**: your Bitcoin wallet (Xverse, Magic Eden, Leather) will act as the destination wallet.

{% hint style="info" %}
Always **double-check** that your destination wallet address supports the token you intend to bridge.
{% endhint %}

#### 3. Gas fees on the origin chain

Every bridge transaction requires network fees.

* **On Bitcoin**: You must pay a network gas fee in BTC. MineBridge allows you to choose your fee level *(Slow/Medium/Fast/Custom)* depending on how quickly you want the transaction confirmed.
* **On Solana or NEAR**: You need a small balance of the native token (SOL or NEAR) to cover gas fees when bridging tokens.

#### 4. The token you want to bridge

* If bridging **from Bitcoin**, ensure the Rune token is in your Bitcoin wallet.
* If bridging **to Bitcoin**, make sure you hold the supported Solana or NEAR token that you wish to bridge.

Not all tokens are available on every chain. MineBridge UI will only show you tokens that are currently supported.

{% hint style="info" %}
**MineBridge Fees:** In addition to network gas, note that MineBridge charges a small fee:

* **0.5% - 1%** of the transferred amount, depending on the token being bridged.
* This fee is automatically deducted from the bridged tokens on the **destination chain**.
  {% endhint %}

**Once you have these four things ready - your wallets, gas, and tokens - you’re prepared to begin. Continue to How to Use MineBridge for the full step-by-step process.**


---

# 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://runemine.gitbook.io/runemine/user-guides/minebridge-user-guide/getting-started.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.
