# MineBridge Core Expansion

From the outset we have taken a product-led marketing approach and will continue to lead with product. To that end, we’re sharing here the primary product roadmap for RuneMine by MineLabs, split into three distinct phases.

[Phase 1: Evolution ](#phase-1-evolution)

[Phase 2: Odyssey](#phase-2-odyssey) 

[Phase 3: Ascension](#phase-3-ascension)

{% hint style="info" %}
Timeline is estimated and lays out the general vision for the MineLabs roadmap and may be subject to change.
{% endhint %}

### Phase 1: Evolution

Focuses on initiating the decentralization of the MineBridge with Multi-Party Computation (MPC)/Threshold Signature Scheme (TSS) and increasing the number of trusted validators. 

Evolution emphasizes growth and security, beginning with a careful selection of validators based on their reputation and monetary stake, similar to Chainlink’s model. 

The process involves validators independently verifying and signing off on transactions before a majority consensus approves bridge transfers.<br>

### Phase 2: Odyssey

Broaden the validator network and enhance connectivity between Solana, Bitcoin, and additional ecosystems, lay the groundwork for BitVM2 implementation.&#x20;

Research and development focus on signature sharing solutions and integrating more complex blockchain environments, including direct developments on Bitcoin’s integration challenges through multisig and TSS solutions.

### Phase 3: Ascension

Full transition to BitVM2-based bridging solution.&#x20;

Marks the transition to a fully decentralized bridging solution using BitVM2. Ascension involves deploying a bridge based on the BitVM2 design, enabling us to reduce the amount of trust imparted on bridge operators, and optimizing the system to handle cross-chain transactions more efficiently.&#x20;

The goal is to establish a permissionless and trustless framework for asset transfers, positioning Solana as a leading Layer 2 solution for Bitcoin-related transactions.

<br>


---

# 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/roadmap/minebridge-core-expansion.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.