# About Pontis

**Pontis** is an innovative bridge designed to seamlessly connect the Bitcoin ecosystem. The initial version focuses on integrating **Runes** and **BTC as Pontis BTC** on Stacks and EVM networks, along with bridging **SIP10 <> ERC20 tokens**. Pontis enhances the utility and accessibility of Bitcoin assets, creating new opportunities for decentralized finance and asset management.

### Features

#### Bitcoin Asset Integration

Pontis bridges key assets across ecosystems, including:

* **Runes**
* **BRC-20**
* **Ordinals**
* **BTC as Pontis BTC**
* **SIP10 <> ERC20 tokens**

{% hint style="info" %}
When **sBTC** becomes live on the Stacks mainnet:

> * All **Pontis BTC tokens** will be converted to sBTC.
> * The **Pontis BTC bridge to Stacks** will be decommissioned.
> * On EVM networks, **Pontis BTC** will also transition to sBTC once the protocol goes live.
>   {% endhint %}

### Roadmap

#### Current and Upcoming Goals

| **Feature**              | **Status**  | **Details**                                                                        |
| ------------------------ | ----------- | ---------------------------------------------------------------------------------- |
| Support for **Runes**    | Live        | Full support for Runes bridging on Stacks and EVM.                                 |
| Support for **sBTC**     | In Progress | Pontis BTC migration to sBTC upon its deployment on Stacks mainnet.                |
| Expand **BRC20** support | Planned     | Support for BRC20 token integration to unlock more Bitcoin asset capabilities.     |
| Ordinals integration     | Planned     | Enable bridging of Bitcoin Ordinals across chains.                                 |
| Additional L2s           | Planned     | Integration with non-EVM Bitcoin Layer 2s, Ethereum, Solana, and other ecosystems. |

### Security Model

Pontis employs a robust security architecture based on a multisignature setup across all connected networks. Each multisig participant functions as an independent node, responsible for validating and verifying every bridging transaction. Once a transaction is approved, the node signs it, ensuring a secure and decentralized process.

The nodes participating in the multisig setup are established and reputable projects from the Bitcoin and Stacks ecosystems. These projects include:

{% tabs %}
{% tab title="First Phase" %}

* [**Asigna**](https://www.asigna.io)
* [**Bima**](https://www.bima.money)
* [**BILLION•DOLLAR•CAT**](https://www.billiondollarcat.com)
* [**Bitflow**](https://www.bitflow.finance)
* [**DeSpread**](https://www.despread.io)
* [**Ducat**](https://docs.ducatprotocol.com)
* [**Hermetica**](https://www.hermetica.fi)
* [**Leather**](https://www.leather.io)
* [**Liquidium**](https://app.liquidium.fi/lend)
* [**OrdinalsBot**](https://www.ordinalsbot.com)
* [**Pontis**](https://www.pontis.io)
* [**Sats Ventures**](https://www.satsventures.com)
* [**StackingDAO**](https://www.stackingdao.com)
* [**Xverse**](https://www.xverse.app)
* [**Zest**](https://www.zestprotocol.com)
  {% endtab %}

{% tab title="Second Phase" %}
To be updated
{% endtab %}
{% endtabs %}

#### Transition to Trustlessness

Pontis will transition from multisig to a **Threshold Signature Scheme (TSS)**, enabling:

* **Full decentralization** of the signature process.
* Elimination of reliance on trusted participants.
* Enhanced security for bridging operations.

### Bridging Details

#### Minimum Bridging Amounts

| **Asset** | **Minimum Amount** |
| --------- | ------------------ |
| BTC       | 0.001 BTC          |
| Runes     | Varies by token    |

***

#### Fees

| **Operation**     | **Fee Structure**    |
| ----------------- | -------------------- |
| **BTC Peg-in**    | `0.1% + 0.0001 BTC`  |
| **BTC Peg-out**   | `0.1% + 5 STX`       |
| **Runes Peg-in**  | `0.25% + 0.0001 BTC` |
| **Runes Peg-out** | `0.25% + 5 STX`      |

{% hint style="info" %}
The fees cover:

1. Costs for operations on both ends of the bridge.
2. Support for ongoing development of the Pontis bridge.
   {% endhint %}


---

# 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://pontis.gitbook.io/about/introduction/about-pontis.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.