Full-Cycle BRC-20 Token Development Service on Bitcoin Ordinals

Launching a token on Bitcoin via the Ordinals protocol comes with many technical pitfalls: two-step transfer, UTXO dependency, and differing indexers. We are a team of blockchain engineers with 10+ years of experience in Ethereum and Bitcoin. We develop BRC-20 tokens turnkey: from deployment of the JSON contract to creating your own indexer and explorer. Order BRC-20 token development turnkey – get an engineering consultation.

What problems does BRC-20 token development solve?

Two-step transfer: a typical beginner mistake

Transferring BRC-20 is not a single transaction. First, a transfer inscription is created on the sender's address. Then this inscription is sent to the recipient via a standard Bitcoin transaction. The indexer records both steps and counts the transfer only when the exact UTXO containing the transfer inscription is spent. If the UTXO is spent incorrectly, tokens are permanently burned. Bitcoin network fees for an inscription typically range from $5 to $15 depending on network load.

UTXO dependency: how not to lose tokens

BRC-20 balances are tied to Bitcoin UTXOs that contain inscriptions. If a wallet is unaware of inscriptions and accidentally spends an inscription UTXO as regular bitcoin (e.g., fee bumping, UTXO consolidation), tokens are lost. A wallet supporting Ordinals is required.

Different indexers – different balances

In the early days of BRC-20, different indexers interpreted edge cases differently. The situation has stabilized, but during development it is essential to cross-check results on several services: Hiro, UniSat, OKX Ordinals.

How does BRC-20 work?

BRC-20 uses JSON format written into the witness part of a SegWit transaction. There are only three operations: deploy, mint, transfer. Each is a separate Ordinals inscription.

{
  "p": "brc-20",
  "op": "deploy",
  "tick": "MYTK",
  "max": "21000000",
  "lim": "1000"
}

{
  "p": "brc-20",
  "op": "mint",
  "tick": "MYTK",
  "amt": "1000"
}

{
  "p": "brc-20",
  "op": "transfer",
  "tick": "MYTK",
  "amt": "500"
}

Why is the choice of indexer important for BRC-20?

Indexers are off-chain services that track inscriptions and compute balances. Different indexers may give different results due to ambiguities in handling edge cases, such as double mints or invalid transfer amounts. Therefore, it is important to choose a reliable indexer and, if necessary, run your own.

How we develop BRC-20: tech stack and example deployment

We use the official ord client and the Ordinalsbot API for creating inscriptions. Here is an example deployment in TypeScript:

import axios from 'axios';

async function deployBRC20Token(config: {
    tick: string;
    max: string;
    lim: string;
    receiverAddress: string;
}) {
    const inscriptionData = JSON.stringify({
        p: "brc-20",
        op: "deploy",
        tick: config.tick,
        max: config.max,
        lim: config.lim,
    });
    const response = await axios.post('https://api.ordinalsbot.com/inscribe', {
        files: [{
            name: "deploy.json",
            size: Buffer.byteLength(inscriptionData),
            type: "text/plain;charset=utf-8",
            dataURL: `data:text/plain;charset=utf-8,${inscriptionData}`,
        }],
        receiveAddress: config.receiverAddress,
        fee: 15,
        lowPostage: false,
    });
    return response.data;
}

After deployment, we check balances via indexers. The Hiro API is among the most reliable:

async function getBRC20Balance(address: string, ticker: string): Promise<string> {
    const response = await axios.get(
        `https://api.hiro.so/ordinals/v1/brc-20/balances/${address}`,
        {
            params: { ticker: ticker.toUpperCase() },
            headers: { 'x-api-key': process.env.HIRO_API_KEY },
        }
    );
    const token = response.data.results.find(
        (t: any) => t.ticker.toLowerCase() === ticker.toLowerCase()
    );
    return token?.overall_balance ?? "0";
}

BRC-20 vs ERC-20 comparison

BRC-20 is dozens of times cheaper to deploy, but lacks flexibility. Compared to ERC-20, deployment savings can reach 90% (smart contract development on Ethereum starts at $2000). For projects requiring programmability, we recommend Stacks or Bitcoin L2s.

Project workflow

1. Analysis – discuss ticker, emission, distribution mechanism.
2. Design – choose the tool stack (ord, APIs, indexers).
3. Implementation – deploy, write mint service, integrate with wallets.
4. Testing – verify on testnet, simulate all operations.
5. Deployment – publish on mainnet, set up monitoring.

What is included (deliverables)

• BRC-20 token deployment with chosen ticker and parameters.
• Creation of a mint service for users (if fair launch is needed).
• Integration with indexers (Hiro, UniSat, OKX).
• Documentation on token usage and API.
• Training for the client's team on BRC-20 operations.
• Support for 2 weeks after launch.
• Access to development and monitoring tools.

Estimated timelines

Simple token deployment – a few hours. Full infrastructure (indexer, explorer, mint service) – 4 to 8 weeks. The cost is calculated individually based on the scope of work.

Our experience is backed by dozens of projects. We guarantee correct operation of all components. We use proven tools and follow best practices. Contact us for a consultation – our engineers will help with ticker selection, infrastructure deployment, and indexer integration.

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.