> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bitrune.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Bitrune is a Bitcoin-native AMM for trustless BTC-Rune swaps, built on Taproot and MuSig2.

**Bitrune** is a Bitcoin-native Automated Market Maker (AMM) that enables trustless swaps between BTC and **Runes** directly on Bitcoin mainnet. It operates entirely on Bitcoin L1 using **Taproot** (BIP-341) key-path and script-path spends, **MuSig2** cooperative signing for custody, and the **Runes protocol** for fungible token issuance and transfer. There are no smart contracts, sidechains, or bridge assumptions.

Users deposit BTC or Runes into MuSig2-secured deposit addresses, trade through constant-product liquidity pools, provide liquidity to earn fees, etch new Runes with optional deflationary mechanics, and withdraw at any time via cooperative signing or unilateral CSV recovery.

## Core Features

<CardGroup cols={2}>
  <Card title="Passkey Wallet" icon="fingerprint">
    No seed phrase, no browser extension. A single biometric (Face ID / Touch ID) creates a Bitcoin key pair and deposit address. The private key never leaves the device.
  </Card>

  <Card title="BTC ↔ Rune Swaps" icon="arrow-right-arrow-left">
    Constant-product AMM pools (x × y = k) with a default 0.3% swap fee.
  </Card>

  <Card title="Liquidity Provision" icon="droplet">
    Deposit BTC + Rune at the current pool ratio, receive LP shares. Constant-product mint/burn accounting.
  </Card>

  <Card title="BITRUNE Mining" icon="pickaxe">
    Stake LP-Rune tokens into mining pools to earn BITRUNE rewards, distributed per-block.
  </Card>

  <Card title="Referral Rebate" icon="user-plus">
    Invite friends with a unique 6-character invite code. Referrers earn BITRUNE rewards from their referees' swap volume.
  </Card>

  <Card title="Rune Etching" icon="hammer">
    Create new Runes from the Bitrune UI with configurable supply, divisibility, symbol, and optional deflationary tax rules.
  </Card>

  <Card title="On-Chain Audit Tags" icon="shield-check">
    Every swap, LP event, and tax execution embeds verifiable proof data in Runestone odd-tags. Anyone can replay the AMM math from the blockchain alone.
  </Card>

  <Card title="CSV Recovery" icon="key">
    If the platform becomes unavailable, users can self-recover funds after a timelock (default 30 days) using the Taproot script-path spend.
  </Card>
</CardGroup>

## How Bitrune Differs from Other DEXes

| Property               | Bitrune                                   | Typical DEX                     |
| ---------------------- | ----------------------------------------- | ------------------------------- |
| Execution layer        | Bitcoin L1 only                           | EVM / L2 / sidechain            |
| Key management         | Passkey (biometric, no seed phrase)       | Seed phrase / browser extension |
| Custody model          | 2-of-2 MuSig2 (user + platform)           | Smart-contract escrow           |
| Recovery mechanism     | Taproot CSV script-path (user unilateral) | Depends on contract admin       |
| On-chain verifiability | Runestone audit tags on every tx          | Trust the contract / indexer    |
| Signing                | Schnorr / MuSig2 (BIP-327)                | ECDSA or account abstraction    |
| Address type           | P2TR (BIP-341)                            | Varies                          |

* No smart contracts. All swap logic is coordinated off-chain and settled in Bitcoin transactions.
* No bridges or wrapped tokens. BTC and Runes move natively.
* MuSig2 cooperative custody means the platform cannot unilaterally spend user funds.
* Taproot script-path recovery means the user can always reclaim funds if the platform disappears.

## Supported Assets

Bitrune supports exactly two asset classes:

* **BTC** — native Bitcoin (satoshis).
* **Runes** — fungible tokens issued via the Runes protocol (Runestone / Edict encoding in `OP_RETURN`).

The following are explicitly **out of scope** and will not be supported:

* BRC-20
* Ordinals (inscriptions)
* Stamps

This constraint is by design. The atomicity model required for trustless AMM settlement is incompatible with the transfer semantics of BRC-20, Ordinals, and Stamps.