Skip to main content
Bitrune supports etching (creating) new Runes directly from the platform. The etching transaction follows the Runes protocol and is broadcast to the Bitcoin network as a standard transaction with an OP_RETURN Runestone.

​
Standard Etch

1

Choose a Rune name

Names consist of uppercase letters A–Z only. Verify the name is available on-chain and that it meets the current minimum character-length requirement.
2

Set parameters

  • divisibility (0–38, default 8) — number of decimal places
  • premine — total supply premined to the etcher’s address
  • symbol (single character, optional) — currency symbol displayed in wallets and explorers
3

Upload a logo (optional)

Upload an image file. The logo is inscribed as an Ordinals inscription linked to the Rune.
4

Sign the etching transaction

The platform constructs the transaction and presents BIP-340 sighashes for MuSig2 signing. The user computes partial Schnorr signatures over each sighash and submits their public nonces and partial signatures. The platform aggregates signatures and broadcasts the etching transaction.
5

Wait for confirmation

After 1 confirmation, the Rune is assigned its permanent RuneId in the format block:tx_index (e.g., 840000:25).
6

Premine delivery

The premined supply lands at the user’s deposit address as a 546-sat dust UTXO carrying the full premine amount.
7

Create a pool (optional)

Launch a liquidity pool seeded with the premined Rune and a BTC deposit.

​
Deflationary Etch

A deflationary etch follows the same steps as a standard etch, with the addition of a tax configuration.

​
Tax Configuration Fields

ParameterRangeDescription
buy_tax_bps0–10000Tax on BTC-to-Rune swaps, in basis points (e.g., 500 = 5%)
sell_tax_bps0–10000Tax on Rune-to-BTC swaps
buckets1–4 entriesDistribution rules for collected tax

​
Bucket Types

TypeDescriptionExtra Fields
BURNTokens are permanently removed from circulationnone
AUTO_LPTokens are auto-injected into the pool’s reservesnone
ADDRESSTokens are sent to a specified walletdest_address
Each bucket includes a share_bps field (basis points). The sum of all bucket share_bps values must equal 10000.

​
Example Tax Configuration

{
  "buy_tax_bps": 300,
  "sell_tax_bps": 500,
  "buckets": [
    { "type": "BURN", "share_bps": 5000 },
    { "type": "AUTO_LP", "share_bps": 3000 },
    { "type": "ADDRESS", "share_bps": 2000, "dest_address": "bc1q..." }
  ]
}

​
Immutability

Tax rules are immutable after the etching transaction is broadcast. The platform computes a SHA-256 hash of the canonical JSON representation of the tax configuration and stores it on record. This hash can be used to verify that the rules have not been altered.

​
Notes

  • Only Runes are supported. BRC-20, Ordinals inscriptions, and Stamps are out of scope.
  • The Rune name must be unique across the entire Runes protocol, not just within Bitrune.
  • Divisibility determines the smallest transferable unit. A divisibility of 8 means the Rune can be divided to 8 decimal places, similar to BTC satoshis.