Runes Token Development on Bitcoin: Architecture and Implementation

Runes Token Development (Bitcoin)

Before Runes, there was confusion: BRC-20 ran on top of Ordinals, creating an inscription for every transfer, cluttering the mempool with junk transactions. Casey Rodarmor, creator of Ordinals, designed Runes as a clean-room solution for fungible tokens on Bitcoin — without unnecessary data, using existing Bitcoin primitives. Runes solve the token scaling problem: each BRC-20 transaction produces unwanted inscriptions, increasing the blockchain size. Runes use UTXO and OP_RETURN, making them 10x more compact. In this article, we'll dive into the architecture, etching, transfer, and indexing of Runes, along with real code examples. You'll learn how to avoid common pitfalls, such as losing tokens due to pointer logic, and how to set up an indexer properly. Our experience: 5+ years in blockchain development, 15+ projects on Bitcoin and EVM. We guarantee protocol compliance and no losses due to pointer logic. Contact us for a consultation — we assess complexity and timelines within one day.

How Does the Runes Protocol Work?

Runes does not require changes to the Bitcoin consensus. The protocol lives in OP_RETURN — data is not stored in the UTXO set, so the blockchain doesn't get bloated (unlike BRC-20, which stores state in satoshis).

Key concepts:

• Runestone — the protocol message inside OP_RETURN. Contains etching, mint, transfer, and edicts.
• UTXO as balance carrier — Runes balances are stored not in a global mapping (like ERC-20), but in specific UTXOs. If you hold 1000 RUNE, you have a UTXO with an attached balance.
• Rune ID — {block_height}:{tx_index} of the etching transaction. For example, the first Rune has ID 840000:3.
• Spacers — visual separators in the name (dots), e.g., UNCOMMON•GOODS.

How to Create a Rune (Etching)?

Etching is a transaction with a Runestone in OP_RETURN declaring a new Rune.

Etching parameters: divisibility (0–38, analogous to decimals in ERC-20), symbol (Unicode character for display), premine (amount of tokens for the etcher immediately), terms (conditions for open mint, if allowed) — amount, cap, height, offset, turbo (compatibility flag for future versions).

The Runestone data structure is encoded using varint encoding (LEB128) — a compact variable-length integer representation.

Practical Implementation via ord CLI

# Install ord (official client)
cargo install ord

# Synchronize with Bitcoin node (or via RPC to external)
ord --bitcoin-rpc-url http://user:pass@localhost:8332 index

# Create wallet
ord wallet create

# Etch a new Rune
ord wallet etch \
  --rune "MYTOKEN•NAME" \
  --divisibility 8 \
  --symbol "M" \
  --supply 21000000 \
  --premine 21000000 \
  --fee-rate 20

# Mint (if open mint is enabled)
ord wallet mint \
  --rune "MYTOKEN•NAME" \
  --fee-rate 20

Via Library (JavaScript/TypeScript)

For integration into an application, use the runestone npm package or work directly with bitcoinjs-lib:

import { Runestone, Etching, Terms, RuneId } from "runestone-lib";
import * as bitcoin from "bitcoinjs-lib";

function buildEtchingTransaction(
  utxo: UTXO,
  runeName: string,
  divisibility: number,
  supply: bigint,
  feeRate: number
): bitcoin.Transaction {
  const runestone = new Runestone({
    etching: new Etching({
      rune: Rune.fromString(runeName),
      divisibility,
      symbol: "T",
      premine: supply,
      turbo: true,
    }),
    edicts: [{
      id: new RuneId(0n, 0n),  // 0:0 = itself during etching
      amount: supply,
      output: 1n,              // output index for receiving premine
    }],
  });

  const psbt = new bitcoin.Psbt({ network: bitcoin.networks.bitcoin });
  
  // Input: funded UTXO to pay fees
  psbt.addInput({
    hash: utxo.txid,
    index: utxo.vout,
    witnessUtxo: { script: utxo.scriptPubKey, value: utxo.value },
  });
  
  // Output 0: OP_RETURN with Runestone
  psbt.addOutput({
    script: bitcoin.script.compile([
      bitcoin.opcodes.OP_RETURN,
      Buffer.from("52554e45", "hex"),  // RUNE magic bytes
      runestone.encipher(),
    ]),
    value: 0,
  });
  
  // Output 1: recipient of premine (must be above dust)
  psbt.addOutput({
    address: recipientAddress,
    value: 546,  // dust limit for P2WPKH
  });
  
  // Output 2: change
  psbt.addOutput({ address: changeAddress, value: changeAmount });
  
  return psbt;
}

Transferring Runes (Edicts)

Transferring Runes is a transaction with a Runestone containing edicts. Each edict specifies: which Rune, how many, to which output.

Important protocol rule: if the Rune balance of an input UTXO is not fully covered by edicts, the remainder automatically goes to the first non-OP_RETURN output (pointer). No explicit pointer means the first output. This differs from EVM, where unspent funds remain with the sender.

Example: you have a UTXO with 1000 RUNE. Transaction with edict: send 300 RUNE → output 2. Automatically: 700 RUNE → output 1 (default pointer). If output 1 is a burn address, you accidentally burn 700 RUNE. This is the main cause of token loss — misunderstanding pointer logic. When developing a Runes wallet, you must explicitly configure the pointer output to the user's change address.

Indexing Runes: Options and Practice

Runes do not have a standard RPC API in Bitcoin Core — a separate indexer is required. Compare options:

For production, we use our own ord indexer with replication — guaranteeing availability and speed. Up to 40% savings compared to hosted solutions.

How Runes Differs from BRC-20

What's Included in Our Runes Token Development

• Tokenomics and protocol parameter analysis
• Etching, mint, and transfer logic
• Wallet integration (list of Runes-supporting wallets)
• Development of an indexing API (ord + custom endpoints)
• UI for mint/transfer (optional)
• Testnet and mainnet testing
• Documentation and team training
• One month of technical support after launch

Limitations of Runes (What to Know in Advance)

Runes are not smart contracts. No conditional transfers, staking, or DEX without a separate solution. All logic familiar from Solidity is impossible on-chain. Only creation, transfer, and burn are available.

For DeFi on top of Runes, you need off-chain matching (centralized orderbook) or a separate L2 with verification via Bitcoin SPV. Comparison with ERC-20: EVM tokens win in flexibility, but Runes provide native Bitcoin security and audience.

Development timeline: etching and basic wallet — 1–2 weeks. Full integration with indexer and marketplace — 6–10 weeks. Pricing is determined individually after requirements audit. Get a consultation for your project — we assess complexity and propose the optimal solution.

Our experience: 5+ years in blockchain development, 15+ projects on Bitcoin and EVM. We guarantee protocol compliance and no losses due to pointer logic.

Token Development: ERC-20, Tokenomics, Vesting

We’ve seen more rekt tokens than we can count — not because the code was broken, but because the economic assumptions were naive. A token that doesn’t collapse from inflation in six months, where governance actually works, and vesting can’t be bypassed through delegation tricks — that’s real engineering. We build under that standard.

How We Avoid Common ERC-20 Pitfalls

ERC-20 standard has nine functions. Complexity starts with extensions:

ERC-20Permit (EIP-2612) — gasless approve via signature. User signs permit(owner, spender, value, deadline, v, r, s) off-chain, spender calls permit() + transferFrom() in one transaction. Removes separate approve step. Risk: signature can be intercepted — need deadline and nonce checking. We always implement EIP-712 typed structured data to prevent signature malleability.

ERC-20Votes (EIP-5805) — snapshot balances for governance. Checkpoint system stores balance history by block number. getPastVotes(address, blockNumber) returns balance at proposal creation, not current. Prevents flash loan governance: can't borrow tokens and vote in one transaction.

Rebasing tokens (stETH, Ampleforth) — balanceOf changes automatically through internal shares ratio. High integration complexity: most DeFi protocols don't work correctly with rebasing without non-rebasing wrapper. We've deployed wrappers that decouple balance from share price for Uniswap compatibility.

Fee-on-transfer tokens — percentage cut on every transfer. Breaks AMM calculations: pool receives less than expected. Uniswap v2/v3 don't support natively — needs special pair/router. We’ve built custom routers that handle fee-on-transfer tokens without reverting.

Why Tokenomics Sustainability Matters More Than Excel

Tokenomics isn't Excel table summing to 100%. It's incentive model that either works long-term or creates selling pressure killing the project.

Emission Schedule and Inflation — Fixed supply (Bitcoin model) works for store-of-value, but for utility tokens you need controlled inflation. Inflationary model (like Ethereum post-Merge) generates new tokens to incentivize participants. Key balance: emission should be <= value captured by protocol. If protocol earns $100k/month but emission is $500k/month in market value — constant selling pressure inevitable. We model these scenarios using Python simulations with cadCAD for complex systems.

Supply Distribution — No universal formula. Principle: no single entity >33% voting power at launch. Otherwise governance is fiction.

What Are the Most Critical Vesting Contract Mistakes?

Linear vesting with cliff is standard for team and investors. cliff is the period after TGE with zero availability. After cliff: linear unlock until duration. Typical implementation errors we catch in audit:

• Revocable vesting without timelock — owner can revoke immediately. Solution: revocation through multisig + governance vote with 7-day delay.
• Cliff doesn't block governance rights — with ERC-20Votes, recipient can delegate voting power from day one even if tokens aren't unlocked. We explicitly separate voting power from claim logic.
• No emergency pause — if vesting contract vulnerability discovered, need ability to pause claims. Pausable + timelock on unpause.

We’ve seen a project where the cliff was set to 0 by mistake — team could dump immediately. Our fuzz tests catch such edge cases before deployment.

Why Is Liquidity Bootstrapping Crucial for Token Launch?

Launch mechanics are critical. Three main approaches:

• Balancer LBP — temporary pool with high initial token weight (90/10 project-token/USDC) that automatically decreases to 50/50 over days. Creates downward price pressure preventing bot buys at one price. After LBP liquidity moves to permanent pool.
• Fjord Foundry — specialized platform for LBP and fair launches. Less operational overhead than direct Balancer integration.
• Uniswap v3 with limited range — add liquidity in narrow range around initial price. High capital efficiency but requires active range management.
• TWAMM — mechanics for gradual large-order sales without slippage. Implemented in FraxSwap.

LBP is 3-5x better than standard AMM listing for price discovery; we’ve seen fair launches with 50% less initial dump compared to direct Uniswap listings.

Governance Tokens and Voting Mechanics

OpenZeppelin Governor is the standard. Modular: GovernorVotes for counting, GovernorTimelockControl for timelock execution, GovernorSettings for adjustable parameters. Quorum is minimum percentage of supply for voting validity. Compound set quorum at 400k COMP (4% supply). We set quorum dynamically based on historical participation to avoid apathy or whale capture.

Flash loan governance attack — attacker borrows tokens via flash loan, delegates to self, creates proposal or votes, returns tokens. ERC-20Votes with block-based snapshot completely blocks this: must have tokens at snapshot creation moment, not voting moment.

Delegation — small holders often don't vote. Liquid delegation (like Optimism) lets delegate voting power to addresses without transfer. Critical for protocols with many passive holders.

Token Development Stack

Contracts: Solidity 0.8.x, OpenZeppelin Contracts 5.x (ERC20, ERC20Permit, ERC20Votes, Governor, TimelockController, TokenVesting).
Tokenomics audit: Python models with emission/demand simulation, cadCAD for complex systems modeling.
Deployment and management: Foundry scripts, Gnosis Safe for treasury, OpenZeppelin Defender for automation.
Analytics: Dune Analytics for on-chain metrics, Token Terminal for protocol revenue.

What’s Included in the Work (Deliverables)

• Tokenomics model with stress tests (bear market, whale exit, governance capture)
• Contract development with Foundry fuzz tests (gas optimization, reentrancy tests, overflow checks)
• Audit summary and list of edge cases covered
• Deployment scripts with Gnosis Safe admin keys
• Documentation for future upgrades and maintenance
• 30-day post-launch monitoring support

Process

1. Tokenomics design — supply model, allocation, emission schedule, vesting. Stress-test scenarios.
2. Contract development — ERC-20 + extensions, vesting, governance. Foundry fuzz tests on vesting calculations, governance thresholds.
3. Audit — special attention on governance attack vectors, vesting bypass, permit replay attacks. We use Slither and Echidna for formal verification.
4. LBP / launch — choose mechanics, set parameters, monitor first 24 hours.
5. Post-launch — monitor supply distribution via Dune, governance participation metrics, treasury management.

Timelines

• ERC-20 with permit and basic governance: 2–3 weeks
• Vesting contract with revocation and cliff: 2–4 weeks
• Full governance (Governor + Timelock + Token): 4–7 weeks
• Token + LBP + governance + vesting: 8–14 weeks

We can estimate your project within 24 hours after discussing requirements. Contact us to start the conversation — no obligation, just a technical chat about your token model. Get a detailed proposal tailored to your tokenomics and compliance needs.