MSTR Cat

Blockchain/Level IX · Speed and spectacle/9.2 The fair market/Lesson 7

Fair launches on bitcoin: from blueprint to practice

Perpetual curves, no admin keys, and the launch that remains human

MaterialsA block explorer with UTXO visualizationThe Runes protocol documentationThe BitVM white paperAccess to Citrea’s mainnet documentation

Wonder

  1. How can a market function without an owner who controls the supply?
  2. Which attack vectors does the UTXO model weaken, and which remain?
  3. What is the precise trade-off between security guarantees and execution speed in a fixed-block-time environment?

Explore

    Part IBlueprint: a fair launch market on Bitcoin

  1. Bitcoin’s design removes some of the commonest tools of fraud found elsewhere: no admin keys over the base asset, no standing token approvals, and no upgradeable logic where rules change silently. Issuance is fixed and governed by consensus rather than a committee, and with the default signature type every spend commits to exact inputs and outputs. Tokens built on Bitcoin can still be abused, for example through a creator’s large premine, so a fair market needs rules of its own on top.
  2. Code is only half of fairness; the other half is conduct. A launch built to these standards would also have no admin or promoter whose ongoing work holders depend on (the ‘efforts of others’ at the heart of the US Howey test), make no promise of profit or yield, publish plain disclosures of what the token is and is not, disclose any paid promotion, and get legal review before launch. Neither half suffices alone: honest people can ship exploitable code, and safe code can be sold with misleading promises.
  3. A fair launch design removes mint abuse by construction: supply is fixed at creation and no key can add to it. Honeypots disappear if selling is always open and no owner can block exits. Oracle manipulation disappears because price comes only from the curve’s own reserves. Sybil reward farming gains nothing when rewards are linear in balance. Liquidity pulls are impossible only if the reserve is held by the rules themselves; Bitcoin Script cannot hold such a reserve, so it must sit on a host layer whose trust model becomes the limit.
  4. Sniping and sandwich attacks are neutralized within a block through uniform per-block clearing. All trades in a given block settle at one uniform price, removing the advantage of order within the block, though a miner can still delay or exclude an order. Buying in an earlier block can still pay, so that edge is bounded, not removed. Large holders selling creates price risk for other participants but not theft; it is standard market volatility. Custodial exchanges may net trades off-chain, outside these rules, though on-chain settlement is unaffected.
  5. Irreducible risks remain: phishing, impersonation, paid hype, and poor individual judgment are human factors no protocol can eliminate. The remaining trust depends entirely on the hosting layer. A metaprotocol relies on Bitcoin consensus and indexers for its rules but cannot itself hold bitcoin. A BitVM rollup assumes at least one of n operators is honest to challenge fraud. A sidechain federation requires trusting a specific group of signers. Each choice trades different risks against different capabilities.
  6. The costs are real: fewer features, coarse price updates with roughly ten-minute blocks, and fees that rise in congestion. None of the parts is new. No-admin AMM contracts have run since Uniswap v1 (2018); batch auctions run on CoW Protocol and in Penumbra’s per-block swaps; Shutter encrypts pending transactions; PSBTs make Bitcoin signing explicit; Runes carries tokens on Bitcoin; BitVM points to trust-minimized Bitcoin layers. No widely used launchpad yet combines them all. This blueprint is an open design that anyone may build.
  7. Part IIFair launches on Bitcoin: from blueprint to practice

  8. Bitcoin’s genesis block, mined January 3, 2009, contained no premine. The 50 BTC reward was unspendable, and mining opened to anyone with the first public software release on 9 January 2009. Distribution depended entirely on hash rate; early miners, including Satoshi Nakamoto, accumulated much of the initial supply through dominance rather than allocation. No committee distributed coins, but network effects still concentrated wealth among those who arrived first.
  9. Runes, launched at the April 2024 halving, introduced open etchings with fixed mint caps and block-height windows. Anyone could mint a fixed amount, paying only fees, without permission from an issuer. This eliminated admin keys for token creation but not for distribution; etchers can reserve a premine, and bots and early participants often took large shares of open mints. The protocol enforced the cap, but it did not enforce equitable participation.
  10. Metaprotocols like Alkanes, live since early 2025, host programs carried in Bitcoin transactions and executed by Alkanes indexers. These platforms support token launchpads where developers deploy logic for minting and trading. While the base layer remains permissionless, some launchpads introduce operators who manage liquidity and order books. Trust shifts from protocol designers to these intermediaries, creating new points of failure and centralized control.
  11. Bitcoin layers such as Citrea, which reached mainnet in January 2026, enable AMM-style markets using BitVM-bridged bitcoin. These rollups execute complex logic off-chain while settling on Bitcoin. They offer faster execution but require users to trust the bridge’s security assumptions. The trade-off is expressiveness against the risk of a compromised sequencer or validator set.
  12. Indexer disagreement remains a critical gap in Bitcoin-based token markets. Different software implementations may interpret protocol rules differently, leading to divergent views of supply and ownership. A user holding a token on one indexer’s view might appear insolvent on another. This fragmentation complicates trading and increases the risk of errors during swaps or liquidations.
  13. Whether a market can combine batch clearing, no admin keys and settlement in native bitcoin is still an open question. Existing platforms tend to use operator-run order books, pooled liquidity with admin controls, or wrapped bitcoin. The building blocks exist (level VIII), and the technical barriers are lower than at Bitcoin’s start; the social coordination problem remains.

Key facts

  • With default signatures, Bitcoin’s UTXO model makes every spend explicit and leaves no standing token approvals.
  • A fair design also needs fair conduct: no promoter whose efforts holders rely on, no profit promises, plain and paid-promotion disclosures, and legal review.
  • Uniform per-block clearing neutralizes sniping and sandwich attacks by settling all trades in a block at one uniform price.
  • BitVM-style bridges replace trusted federations with a 1-of-n honesty assumption, where at least one operator must be honest.
  • No mint key exists in fair launch designs, making supply expansion impossible beyond scheduled issuance.
  • The ten-minute block time provides a verification window but prevents high-frequency trading and real-time price discovery.
  • Bitcoin had no premine; coins were distributed through mining from the first public release in January 2009.
  • Runes launched in April 2024 with open etchings and fixed mint caps.
  • Alkanes, live since early 2025, runs programs executed by indexers and hosts token launchpads.
  • Citrea reached mainnet in January 2026, enabling AMM-style markets via BitVM.
  • Indexer disagreement can cause different software to report conflicting token balances.
  • Combining batch clearing, no admin keys and native bitcoin settlement remains an open design problem.

Exercise nine, six, three, one

9CollectList 9 distinct attack vectors common to account-based blockchain ecosystems.
6ClusterGroup the 9 vectors into 6 by what, if anything, could defeat each.
3DistillReduce the 6 categories to 3 core principles that define a ‘fair launch’ architecture in a fixed-issuance environment.
1CrystallizeWrite 1 sentence stating what is traded away for security in this design model.

Fact check

Dates, figures and claims checked against the published sources listed below.

Open in the interactive academy →

PT ES ZH JA KO RU DE FR MS