# Runes
### What Are Runes?
**Runes** are a new protocol for creating and managing **fungible tokens** directly on the **Bitcoin base layer**, without relying on off-chain data, external indexers, or additional layers. The protocol was introduced by **Casey Rodarmor** (creator of Ordinals).
Unlike other Bitcoin-based token standards like **BRC-20**, which depend heavily on off-chain indexers and inscription parsing, **Runes are fully UTXO-based and on-chain**, making them more efficient, lightweight, and aligned with Bitcoin’s native architecture.
#### 🔧 How Runes Work
* Runes use **Bitcoin's UTXO model** to store and transfer token balances.
* Tokens are created through a process called **etching**, which defines the Rune's name, supply, divisibility, symbol, and optional terms.
* All data is embedded in the **OP\_RETURN** field of standard Bitcoin transactions.
* The protocol avoids account-based logic, keeping things lean and scalable.
#### 💡 Key Features
* Fully on-chain and indexer-free
* Simple UTXO-based transfers
* Flexible minting via etching rules
* Stateless and efficient by design
#### 🧱 Origin of Runes
Runes originate when someone **etches** (creates) a new Rune via a Bitcoin transaction.\
The creator defines:
* Token name (e.g., `MOONRUNE`)
* Symbol or ID
* Total supply
* Decimal places (divisibility)
* Minting rules (e.g., who can mint and when)
Once etched, these tokens can be distributed, traded, or held — all natively on Bitcoin.
### Swap Runes
#### ➱ **Open the Asigna multisig app**
Navigate to the Asigna multisig app in your web browser:
#### ➱ **Select the Vault**
On the homepage page select the Vault and open it by clicking the Vault preview card.
#### ➱ **Access Swap**
Navigate to the **Swap** section, where a modal window will appear.
Input the **BTC Amount**, select the **Rune type** from the list of available Runes.
Configure the Max Slippage and Fee Rate if needed. Optimal Route will be selected automatically.
#### ➱ Transaction Confirmation
Click **Swap** button and confirm the transaction in the connected wallet.
{% hint style="warning" %}
Note, creating this transaction requires 2 signatures.
{% endhint %}
#### ➱ Transaction Execution
{% hint style="info" %}
**Receiving your Runes may take some time.**
This is because the swap service first sends your funds to an intermediate wallet. If the Rune price changes during transaction processing, the service will continue trying to complete the swap for up to **24 hours**.\
If the swap cannot be completed within that time, your funds will be **automatically returned** to your Vault.
{% endhint %}
Before the transaction is executed, it must be **signed by the required number of Vault owners**. Once the confirmation threshold is reached, locate this transaction in the **Transactions** section -> **Queue** tab and click the **Execute** button to start broadcasting of the transaction.
### Transfer Runes
#### ➱ **Open the Asigna multisig app**
Navigate to the Asigna multisig app in your web browser:
#### ➱ **Select the Vault**
On the homepage page select the Vault and open it by clicking the Vault preview card.
#### ➱ **Access Runes**
Navigate to the **Assets** section -> **Runes** tab, where you will find a list of the available **Runes**. Runes can be transferred to other Vaults or Wallets just like any other token.
#### ➱ Send Runes
To initiate a transfer, click the **Send** button.
A modal window will appear, prompting you to input the **Rune type**, **Amount**, and **Recipient Address**.
{% hint style="success" %}
You can send any amount of **Runes** from your available balance — either a portion or the full amount.\
Sending a portion of your Runes will create **two new UTXOs with Runes**, each with a size of **546 sats**.
{% endhint %}
After entering the necessary details, you'll be prompted to select a transaction fee. You can choose from the **recommended fee options** or input a **custom fee**.
#### ➱ Transaction Review and Confirmation
Once the fee is set, you'll be able to **review** the transaction details. If everything is correct, click **Confirm** button and confirm the transaction in the connected wallet.
#### ➱ Transaction Execution
Before the transaction is executed, it must be **signed by the required number of Vault owners**. Once the confirmation threshold is reached, locate this transaction in the **Transactions** section -> **Queue** tab and click the **Execute** button to start broadcasting of the transaction.
