# SecureSovereign — Full Corpus
> Concatenated Markdown sources from secsov.com (articles and BIP pre-proposals). Generated by build script. Index: https://secsov.com/llms.txt
---
# Articles
# Bitcoin Appeal by Demographics
## Table of Contents
1. [What this document is](#what-this-document-is)
2. [Generational](#1-generational)
3. [Geographic and Economic](#2-geographic-and-economic)
4. [Professional](#3-professional)
5. [Ideological and Political](#4-ideological-and-political)
6. [Employment and Economic Circumstances](#5-employment-and-economic-circumstances)
7. [Use Case Specific](#6-use-case-specific)
8. [Lifestyle](#7-lifestyle)
9. [Technical Expertise](#8-technical-expertise)
10. [Special Circumstances](#9-special-circumstances)
11. [Merchant and Business](#10-merchant-and-business)
## What this document is
This is a **structured taxonomy**: for many demographic slices, it lists **plausible reasons** Bitcoin might resonate. It is **not** a weighted statistical study. There is no claim here that each bullet is true for a majority of that group, or that the sections are equally important in the real economy.
**Why that matters.** Treat the lists below as **hypotheses and narratives** worth testing against data, not as established facts per segment. This document maps plausible appeal vectors. It does not measure them.
Surveys that ask about “cryptocurrency” often **mix Bitcoin with altcoins**. On-the-ground usage (P2P, remittance, savings) may not show up cleanly in household surveys. Real adoption is also skewed by access, regulation, culture, wealth, and self-selection.
When a slice lists 401k or index integration as the appeal, that is a real entry vector. It is not Stage One monetary sovereignty. The 401k remains inside the extraction accounting in [The_SP500_Sleight_of_Hand.md](../../03-analytical/capture-apparatus/The_SP500_Sleight_of_Hand.md).
## Introduction
The sections below organize **many possible appeal vectors** by demographic and situational lens. **Universal** themes (inflation hedge, settlement without intermediaries, self-custody, fixed supply, etc.) recur across groups; a short shared list follows so we do not repeat the same ideas under every heading.
## Universal Bitcoin Appeals
These themes show up again and again in the bullets below, often combined with cohort-specific constraints (regulation, wealth, tech comfort). They are listed once here so later sections can stay shorter.
The following appeals apply across most demographics and represent Bitcoin's fundamental value propositions. These won't be repeated in individual demographic sections:
- **Inflation Hedge**: Protection against currency debasement and monetary expansion
- **Store of Value**: Digital asset for wealth preservation over time
- **Portfolio Diversification**: Uncorrelated asset for investment portfolio balance
- **Global Payments**: Borderless money transfer without intermediaries
- **Censorship Resistance**: Financial transactions immune to third-party interference
- **Financial Sovereignty**: Self-custodial wealth independent of institutions
- **Network Effects**: Benefit from growing global Bitcoin adoption
- **Fixed Supply**: Scarcity economics with 21 million coin limit
- **24/7 Markets**: Continuous trading and transaction capability
- **Settlement without a middleman**: Payments that complete without a bank, card network, or reversible issuer
---
## 1. Generational
Age shapes time horizon, who controls savings, and whether Bitcoin is encountered as a game, a career bet, or a retirement question. The same protocol can read as education, speculation, or legacy depending on where someone sits in the lifecycle.
### **Generation Alpha (Born 2010-2025)**
- **Digital Payment Integration**: Bitcoin payments for freelance work and digital collaboration tasks
- **Technology Career Preparation**: Early familiarity with cryptocurrency for future employment opportunities
- **Long-term Investment Horizon**: Multi-decade time frame for maximum compound growth potential
- **Alternative Income Sources**: Bitcoin supplementing traditional income during economic transitions
- **Global Financial Access**: International financial services without geographic restrictions
- **Digital Asset Understanding**: Early adoption of digital assets and cryptocurrency technology
### **Generation Z (Born 1997-2012)**
- **Alternative to Traditional Banking**: Bitcoin as option outside conventional financial system
- **Social Media Financial Status**: Bitcoin holdings as digital wealth signaling
- **Economic Uncertainty Preparation**: Bitcoin as hedge against economic instability
- **Creator Economy Monetization**: Bitcoin payments for digital content and social media influence
- **Housing Market Alternative**: Bitcoin appreciation as alternative to expensive homeownership
- **Financial Security**: Bitcoin gains reducing anxiety about financial future
### **Millennials (Born 1981-1996)**
- **Housing Market Alternative**: Bitcoin appreciation replacing blocked homeownership wealth building
- **Banking System Distrust**: Bitcoin as alternative to traditional banking after financial crisis experience
- **Student Debt Offset**: Bitcoin gains offsetting decades of student loan payments
- **Gig Economy Financial Stability**: Bitcoin providing stability during irregular freelance income
- **FIRE Movement Acceleration**: Bitcoin enabling Financial Independence Retire Early goals
- **Lifestyle Affordability**: Bitcoin making millennial lifestyle affordable through appreciation
### **Generation X (Born 1965-1980)**
- **Peak Earnings Bitcoin Allocation**: Highest income years coinciding with Bitcoin adoption phase
- **Retirement Portfolio Innovation**: Adding Bitcoin to traditional 401k and IRA strategies
- **Business Treasury Strategy**: Corporate Bitcoin adoption following institutional models
- **Estate Planning Modernization**: Digital assets for inheritance and wealth transfer
- **Investment Diversification**: Bitcoin gains replacing expensive lifestyle spending
- **Technology Adoption**: Comfortable with digital finance while remembering pre-internet scarcity
### **Baby Boomers (Born 1946-1964)**
- **Grandchildren's Future**: Bitcoin gifts and education for next generations
- **Fixed Income Enhancement**: Bitcoin supplementing inadequate retirement income
- **Estate Transfer Innovation**: Modern asset class for inheritance planning
- **Historical Monetary Perspective**: Understanding Bitcoin through gold standard experience
- **Professional Wealth Management**: Bitcoin through trusted financial advisors and institutions
- **Legacy Preservation**: Protecting accumulated wealth from government fiscal irresponsibility
---
## 2. Geographic and Economic
Jurisdiction drives ETF access, tax treatment, banking friction, and whether the main pain is inflation, capital controls, or remittance cost. Regional buckets are coarse; use them as orientation, not as uniform descriptions of every country inside the bucket.
### **North America**
- **Investment Sophistication**: Portfolio diversification and wealth building
- **Regulatory Clarity**: Access to Bitcoin ETFs and institutional products
- **Innovation Economy**: Participation in technological advancement
- **Tax Optimization**: Strategic use of tax-advantaged accounts and planning
- **Real Estate Alternative**: Bitcoin appreciation vs expensive housing markets
- **Retirement Planning**: 401k integration and IRA strategies
- **Mining Infrastructure**: Abundant energy resources for Bitcoin mining
- **Cross-Border Trade**: Seamless US-Canada business relationships
### **Europe**
- **Regulatory Framework**: Clear legal structure for institutional adoption
- **Currency Diversification**: Alternative to Euro and national currencies
- **Cross-Border Payments**: Seamless EU-wide and international transactions
- **Digital Innovation**: Leading fintech adoption and blockchain development
- **Privacy Rights**: Financial privacy compatible with data protection frameworks
- **Energy Costs**: Optimizing energy costs for Bitcoin mining operations
- **Financial Center Integration**: International Bitcoin trading hub development
### **East Asia**
- **Regulatory Development**: Bitcoin legal framework recognition and development
- **Technology Integration**: Advanced digital payment infrastructure
- **Gaming Culture**: Bitcoin integration with gaming economies
- **Investment Culture**: High savings rates channeled into Bitcoin investing
- **Corporate Adoption**: Business treasury and payment integration strategies
- **Manufacturing Economy**: Bitcoin payments for international trade
- **Innovation Hub**: Leading blockchain and Bitcoin development
### **Southeast Asia**
- **Currency Volatility Protection**: Hedge against unstable local currencies
- **Remittance Optimization**: Lower-cost money transfers for overseas workers
- **Gaming Economy**: Bitcoin earning through gaming and digital work
- **Mobile Money Evolution**: Building on existing mobile payment infrastructure
- **Financial Access**: Financial services for underbanked populations
- **Investment Opportunity**: Bitcoin as investment option
- **Tourism Integration**: Bitcoin payments for international tourists
### **Latin America**
- **Hyperinflation Protection**: Protection against currency collapse and devaluation
- **Capital Controls Bypass**: Alternative to government currency restrictions
- **Remittance Corridor**: Efficient money transfers from US diaspora
- **Economic Alternative**: Financial tool during economic instability
- **Dollar Access**: Bitcoin as pathway to US dollar stability
- **Legal Tender Innovation**: Following country-level Bitcoin adoption models
- **Cross-Border Trade**: Regional commerce facilitation
### **Sub-Saharan Africa**
- **Currency Devaluation Protection**: Hedge against volatile local currencies
- **Mobile Money Evolution**: Building on mobile payment foundations
- **Remittance Solutions**: Lower-cost diaspora money transfers
- **Financial Access**: Financial services for rural and underbanked populations
- **Youth Employment**: Bitcoin services as income generation
- **Banking Alternative**: Alternative to traditional banking limitations
- **Economic Development**: Participation in global digital economy
### **Middle East and North Africa**
- **Economic Crisis Response**: Financial tool during economic and political instability
- **International Access**: Alternative to restricted international financial access
- **Currency Protection**: Protection from devaluing local currencies
- **Banking Alternative**: Alternative to limited traditional banking infrastructure
- **Capital Preservation**: Protecting wealth from economic instability
- **Oil Economy Diversification**: Alternative to petroleum-dependent economies
- **International Trade Access**: Connection to global markets
### **South Asia**
- **Currency Hedge**: Protection against local currency devaluation
- **Remittance Solutions**: Lower-cost international money transfers
- **Technology Innovation**: Leading blockchain development and adoption
- **Financial Access**: Financial services for large rural populations
- **Cross-Border Trade**: International business payment solutions
- **Investment Opportunity**: Wealth building through Bitcoin appreciation
- **Regulatory Navigation**: Adapting to evolving regulatory frameworks
---
## 3. Professional
Industry norms decide whether Bitcoin shows up as a stack skill, a client mandate, a treasury option, or a reputational risk. High-earning credentialed roles often have different capacity to save and different liability concerns than gig or hourly work.
### **Technology Professionals**
- **Career Development**: Bitcoin skills for tech industry advancement and employment
- **Open Source Contribution**: Contributing to Bitcoin development ecosystem and protocols
- **International Payments**: Bitcoin payments for tech services and contractor work
- **Startup Treasury Strategy**: Bitcoin adoption for technology company cash management
- **Technical Understanding**: Professional confidence in Bitcoin's cryptographic architecture
- **Innovation Investment**: Early adoption of transformative monetary technology
### **Finance Professionals**
- **Client Service**: Meeting institutional and retail investor Bitcoin interest
- **Career Positioning**: Bitcoin expertise for modern financial advisory roles
- **Product Innovation**: Developing Bitcoin ETFs, custody solutions, and investment products
- **Market Evolution**: Adapting to Bitcoin's integration with traditional financial markets
- **Performance Enhancement**: Bitcoin investment strategies for superior returns
- **Professional Development**: Bitcoin knowledge for financial industry career advancement
### **Healthcare Professionals**
- **High Income Bitcoin Allocation**: Substantial capital for meaningful Bitcoin positions
- **Medical Practice Innovation**: Accepting Bitcoin for healthcare services
- **Asset Protection**: Bitcoin holdings outside professional liability concerns
- **International Medical Work**: Bitcoin payments for overseas medical work
- **Technology Skills**: Blockchain knowledge for healthcare career advancement
- **Financial Independence**: Bitcoin enabling early retirement from demanding medical careers
### **Education Professionals**
- **Pension Supplementation**: Bitcoin enhancing teacher retirement plans
- **Academic Research**: Research opportunities in Bitcoin economics
- **Student Education**: Teaching practical Bitcoin and monetary literacy
- **International Payments**: Bitcoin for global education partnerships and exchanges
- **Income Diversification**: Bitcoin services during school breaks
- **Emergency Fund**: Bitcoin savings during labor disputes and negotiations
### **Legal Professionals**
- **Professional Services Growth**: Bitcoin legal services for growing industry
- **Practice Innovation**: Accepting Bitcoin payments for legal services
- **Regulatory Expertise**: Specializing in Bitcoin law and compliance
- **Industry Investment**: Bitcoin holdings aligned with professional expertise
- **International Work**: Bitcoin payments for cross-border legal services
- **Career Specialization**: Bitcoin law focus for legal practice differentiation
### **Traditional Industry Workers**
- **Wealth Building**: Bitcoin enabling working-class wealth accumulation
- **Pension Supplementation**: Bitcoin enhancing traditional retirement plans
- **Industry Transition**: Bitcoin wealth building during economic transitions
- **Investment Alternative**: Bitcoin as alternative to traditional investments
- **Generational Wealth**: Bitcoin creating family assets for working families
- **Economic Stability**: Bitcoin providing financial security during variable work
### **Service Industry Workers**
- **Tip Monetization**: Bitcoin tips bypassing payment processor fees
- **Career Transition Fund**: Bitcoin accumulation enabling career advancement
- **Gig Economy Payments**: Bitcoin payments for freelance and contracted services
- **Cash Conversion**: Converting cash tips to Bitcoin for long-term wealth storage
- **Financial Security**: Bitcoin holdings providing security during work disruptions
- **Skills Investment**: Bitcoin gains funding career advancement and training
---
## 4. Ideological and Political
Worldview filters which properties of Bitcoin get emphasized (sound money, inclusion, privacy, state capacity). The bullets are not predictions of how every voter or activist behaves; they map common rhetorical fits between ideology and monetary technology.
### **Libertarians and Austrian Economists**
- **Monetary Sovereignty**: Money independent of government control
- **Sound Money Principles**: Fixed supply vs inflationary fiat currencies
- **Government Skepticism**: Distrust of government monetary policy and central banking
- **Property Rights**: Financial privacy and property rights protection
- **Free Market Economics**: Voluntary transactions without intermediaries
- **Individual Freedom**: Financial sovereignty and personal responsibility
### **Conservatives**
- **Value Preservation**: Bitcoin protecting family wealth and traditional principles
- **Family Legacy**: Generational wealth transfer and inheritance planning
- **Business Innovation**: Free market solutions and entrepreneurial opportunities
- **Sound Money**: Return to stable, non-inflationary monetary principles
- **National Competitiveness**: Maintaining technological and financial leadership
- **Institutional Integration**: Bitcoin adoption through trusted financial institutions
### **Bureaucrats and Regulators**
- **Regulatory Compliance**: Bitcoin adoption through proper legal frameworks
- **Framework Development**: Building regulated Bitcoin infrastructure
- **Policy Tools**: Bitcoin as mechanism for government financial programs
- **Risk Management**: Controlled Bitcoin adoption with proper oversight
- **International Coordination**: Bitcoin regulation coordination across jurisdictions
- **Consumer Protection**: Regulated Bitcoin products protecting citizens
### **Progressives and Liberals**
- **Financial Access**: Additional financial service options through Bitcoin
- **Reduced Barriers**: Lower requirements for financial service access
- **Individual Control**: Personal custody and control over financial assets
- **Technology Innovation**: Supporting innovative financial technology development
- **Alternative Systems**: Bitcoin as alternative to traditional banking monopolies
- **Voluntary Adoption**: Optional financial tools for those who choose them
### **Privacy Advocates**
- **Financial Privacy**: Pseudonymous transactions vs surveilled banking
- **Surveillance Resistance**: Financial activity outside traditional monitoring
- **Data Protection**: Reduced data collection requirements for Bitcoin use
- **Digital Rights**: Bitcoin as tool for digital civil liberties
- **Government Independence**: Financial tools independent of state control
- **Private Commerce**: Private commercial transactions
### **Anarchists and Bitcoin-Anarchists**
- **State Independence**: Money independent of government systems
- **Anti-Authority**: Rejection of centralized financial control
- **Cryptographic Freedom**: Mathematical rather than political money
- **Decentralized Systems**: Peer-to-peer systems vs hierarchical institutions
- **Individual Sovereignty**: Personal control over economic relationships
- **Systemic Alternative**: Bitcoin as alternative to existing systems
### **Technology Enthusiasts**
- **Energy Optimization**: Bitcoin mining utilizing available energy resources efficiently
- **Infrastructure Investment**: Bitcoin mining supporting energy infrastructure development
- **Market Participation**: Bitcoin providing adjustable energy demand for grid operators
- **Energy Efficiency**: Optimizing energy costs for Bitcoin mining operations
- **Geographic Arbitrage**: Bitcoin mining utilizing stranded energy resources
- **Technology Investment**: Supporting advancement in energy and computing technology
---
## 5. Employment and Economic Circumstances
How income arrives (steady salary, volatile commissions, business profit, or none) changes the role of savings, buffers, and tax planning. Bitcoin can be long-term accumulation, working capital, or a bridge between jobs, not always the same story.
### **Salary Employees**
- **401k Bitcoin Integration**: Systematic Bitcoin allocation through employer retirement plans
- **Salary Optimization**: Bitcoin bonus and compensation requests
- **Career Security**: Bitcoin wealth building reducing employment dependency risks
- **Professional Development**: Bitcoin skills enhancing employment prospects
- **Emergency Fund**: Bitcoin as financial security during career transitions
- **Long-term Wealth**: Bitcoin enabling financial independence and early retirement
### **Commission-Based Workers**
- **Income Smoothing**: Bitcoin accumulation during high-earning periods
- **Performance Investment**: Bitcoin allocation tied to sales success
- **Tax Strategy**: Bitcoin for managing variable income tax optimization
- **Client Relations**: Bitcoin knowledge for crypto-interested clients
- **Income Diversification**: Bitcoin reducing dependence on variable performance
- **Wealth Multiplication**: Bitcoin appreciation amplifying career earnings
### **Freelancers and Gig Workers**
- **Global Payments**: Bitcoin enabling instant international client payments
- **Income Stability**: Bitcoin providing stability during irregular earnings
- **Platform Independence**: Bitcoin payments reducing platform dependence
- **Tax Advantages**: Bitcoin for freelancer tax strategies and international income
- **Emergency Buffer**: Bitcoin as security during payment delays
- **Portfolio Career**: Bitcoin income streams alongside traditional work
### **Business Owners**
- **Treasury Innovation**: Bitcoin corporate cash management strategy
- **Customer Acquisition**: Bitcoin payments attracting new demographics and reducing fees
- **Supplier Payments**: Bitcoin for international business payments
- **Exit Strategy**: Bitcoin wealth building independent of business sale
- **Innovation Positioning**: Bitcoin adoption differentiating business
- **Economic Hedging**: Bitcoin protecting wealth from industry-specific risks
### **Unemployed/Job Seekers**
- **Skill Development**: Bitcoin and blockchain knowledge for employment
- **Income Generation**: Bitcoin services providing income during job search
- **Career Transition**: Bitcoin funding education and training
- **Network Building**: Bitcoin community providing professional connections
- **Emergency Resources**: Bitcoin as financial buffer during unemployment
- **Entrepreneurship**: Bitcoin enabling self-employment opportunities
### **Retirees**
- **Income Enhancement**: Bitcoin supplementing Social Security and pension payments
- **Healthcare Costs**: Bitcoin gains funding rising medical expenses
- **Estate Planning**: Bitcoin for inheritance planning and wealth transfer
- **Legacy Building**: Bitcoin wealth for family financial security
- **Income Generation**: Bitcoin strategies providing retirement cash flow
---
## 6. Use Case Specific
This section is organized around **jobs to be done**: moving value, selling online, operating under pressure, or allocating capital. The headings overlap with earlier demographics; the focus here is the activity, not the person’s age or passport.
### **Cross-Border Payments and Remittances**
People who routinely cross currencies and banking systems hit fees, delays, and documentation walls that domestic users rarely see. Bitcoin is one possible response where legal and liquidity conditions allow.
#### **Migrant Workers**
- **Remittance Cost Reduction**: Lower fees for regular money transfers to home countries
- **Speed Advantage**: Instant money transfers vs traditional banking delays
- **Banking Access**: Financial services without traditional documentation requirements
- **Family Support**: Better financial outcomes for families abroad
- **Currency Conversion**: Avoiding expensive foreign exchange fees
- **Global Mobility**: Consistent financial services across countries
#### **International Students**
- **Tuition Payments**: Bitcoin for international education expenses
- **Family Support**: Efficient money transfers from families abroad
- **Currency Risk**: Protection against exchange rate fluctuations
- **Banking Alternative**: Financial services without local banking history
- **Career Preparation**: Bitcoin skills for international opportunities
- **Investment Learning**: Understanding global financial systems
#### **Expatriate Workers**
- **Salary Transfers**: Efficient international salary transfers
- **Multi-Currency Simplification**: Bitcoin reducing international financial complexity
- **Tax Optimization**: Bitcoin strategies for international tax planning
- **Career Mobility**: Financial flexibility supporting international careers
- **Emergency Access**: Bitcoin as global emergency financial resource
- **Professional Development**: Bitcoin skills enhancing international business capabilities
### **E-commerce and Digital Payments**
Selling online forces a choice of rails: card fees, platform rules, chargebacks, and international checkout friction. Bitcoin pitches final settlement and lower variable cost, with adoption and UX as the usual bottlenecks.
#### **Online Merchants**
- **Processing Cost Reduction**: Lower fees than credit cards
- **Global Sales**: Bitcoin enabling international customer reach
- **Chargeback Elimination**: Bitcoin's irreversible payments protecting against fraud
- **Customer Acquisition**: Bitcoin payments attracting new demographics
- **Cash Flow**: Faster settlement than traditional processors
- **Innovation Marketing**: Bitcoin acceptance for competitive differentiation
#### **Digital Content Creators**
- **Platform Independence**: Bitcoin reducing platform dependence
- **Global Monetization**: Bitcoin enabling international content monetization
- **Censorship Resistance**: Bitcoin payments immune to platform policies
- **Fan Engagement**: Bitcoin enabling direct creator-fan relationships
- **Micropayments**: Bitcoin for small-value content transactions
- **Revenue Diversification**: Bitcoin income streams alongside platform monetization
#### **Gaming Participants**
- **Earned Rewards**: Bitcoin rewards for gaming achievements
- **In-Game Currency**: Bitcoin as currency for gaming economies
- **Tournament Prizes**: Bitcoin rewards for competitive gaming
- **Content Monetization**: Bitcoin for gaming content creation
- **Professional Gaming**: Bitcoin income from esports careers
- **Career Development**: Gaming industry Bitcoin skills
### **Privacy and Security Focus**
Some roles need fundraising, travel, and supplier relationships that resist account freezes, censorship, or surveillance. Tradeoffs include operational security burden and jurisdictional risk.
#### **Journalists**
- **Source Protection**: Bitcoin for anonymous information payments
- **Censorship Resistance**: Bitcoin donations for independent journalism
- **International Reporting**: Bitcoin for secure financial operations
- **Professional Independence**: Bitcoin reducing dependence on media companies
- **Travel Security**: Bitcoin for secure international travel funding
- **Emergency Operations**: Bitcoin for journalist safety during assignments
#### **Activists and Dissidents**
- **Government Independence**: Bitcoin bypassing authoritarian financial controls
- **Donation Reception**: Bitcoin for anonymous activist donations
- **International Coordination**: Bitcoin enabling global movement coordination
- **Safety Protection**: Bitcoin for activist financial security
- **Emergency Funding**: Bitcoin for rapid response during crises
- **Movement Sustainability**: Bitcoin providing long-term independent funding
#### **Privacy Advocates**
- **Program Funding**: Bitcoin for privacy program financing
- **International Operations**: Bitcoin enabling global privacy work
- **Emergency Response**: Bitcoin for rapid privacy emergency funding
- **Operational Security**: Bitcoin for secure operations
- **Legal Support**: Bitcoin for privacy legal defense funding
- **Documentation Protection**: Bitcoin funding for evidence collection
### **Investment and Trading Focus**
Here the question is portfolio role: long holding, fiduciary service to others, or performance chasing. Time horizon and mandate matter as much as the asset’s design.
#### **Long-term Investors (HODLers)**
- **Scarcity Economics**: Bitcoin's fixed 21 million supply creating value appreciation
- **Network Growth**: Increasing Bitcoin adoption driving value
- **Dollar-Cost Averaging**: Systematic Bitcoin accumulation over time
- **Generational Wealth**: Bitcoin for family wealth transfer
- **Technology Investment**: Bitcoin exposure to transformative technology
- **Monetary Hedge**: Bitcoin protecting against traditional financial system risks
#### **Institutional Portfolio Managers**
- **Client Service**: Bitcoin allocation services for institutional clients
- **Portfolio Management**: Professional Bitcoin portfolio management
- **Risk Management**: Bitcoin for portfolio diversification strategies
- **Career Development**: Bitcoin expertise for modern investment roles
- **Product Innovation**: Access to institutional Bitcoin investment products
- **Performance Enhancement**: Bitcoin allocation for superior returns
---
## 7. Lifestyle
Mobility and household structure change banking relationships, tax residency headaches, and whether wealth is stored for self, children, or extended family. Bitcoin sometimes aligns with minimal fixed geography; sometimes it is just another savings layer.
### **Digital Nomads and Remote Workers**
- **Location Independence**: Bitcoin enabling global financial management
- **Borderless Income**: Bitcoin payments for remote work and international clients
- **Cost Arbitrage**: Bitcoin enabling geographic arbitrage strategies
- **Banking Freedom**: Financial services without geographic limitations
- **Emergency Access**: Bitcoin as travel emergency financial access
- **Professional Networking**: Bitcoin community providing global connections
### **Students and Young Adults**
- **Educational Investment**: Bitcoin as introduction to investing and economics
- **Early Wealth Building**: Bitcoin investment for long-term compound growth
- **Career Preparation**: Bitcoin skills for future technology careers
- **Financial Independence**: Bitcoin enabling independence from parental support
- **Side Income**: Bitcoin services providing student income
- **Peer Learning**: Bitcoin community for social and professional development
### **Parents and Families**
- **Education Funding**: Bitcoin appreciation for children's future education
- **Family Emergency Fund**: Bitcoin as liquid family emergency resource
- **Teaching Tool**: Bitcoin for children's financial and technology education
- **Estate Planning**: Bitcoin for modern family inheritance strategies
- **Legacy Building**: Bitcoin for generational wealth creation
- **Investment Strategy**: Bitcoin as core family investment component
---
## 8. Technical Expertise
Depth of understanding changes whether someone runs infrastructure, audits narratives, or largely trusts custodians. Expertise does not imply uniform ideology, but it does change which risks feel salient.
### **Bitcoin Experts**
- **Protocol Development**: Contributing to Bitcoin core development
- **Community Leadership**: Leading Bitcoin education and adoption efforts
- **Professional Services**: Providing Bitcoin consulting and development services
- **Research Innovation**: Conducting Bitcoin technical and economic research
- **Security Expertise**: Advanced understanding of Bitcoin cryptographic security
- **Network Operations**: Running Bitcoin nodes and mining operations
### **Technology Enthusiasts**
- **Innovation Investment**: Early adoption of transformative monetary technology
- **Technical Learning**: Understanding Bitcoin's cryptographic and distributed systems
- **Community Participation**: Engaging with Bitcoin technical communities
- **Career Development**: Bitcoin technology skills enhancing professional advancement
- **Experimentation**: Testing Bitcoin applications and exploring use cases
- **Future Technology**: Understanding Bitcoin innovation implications
### **Traditional Finance Professionals**
- **Industry Evolution**: Understanding Bitcoin's impact on traditional finance
- **Client Service**: Meeting growing client demand for Bitcoin guidance
- **Product Development**: Creating Bitcoin financial products and strategies
- **Career Adaptation**: Developing Bitcoin expertise for professional relevance
- **Market Integration**: Understanding Bitcoin's integration with traditional markets
- **Risk Management**: Professional evaluation of Bitcoin's portfolio role
---
## 9. Special Circumstances
Legal status, health, family structure, or service history can gate traditional accounts, credit, or stable employment before any cryptocurrency question arises. Appeals below are conditional: accessibility, compliance, and personal risk tolerance still dominate.
### **Disabled Community**
- **Benefit Optimization**: Bitcoin investment using disability benefits
- **Medical Expense Management**: Bitcoin gains covering healthcare costs
- **Accessible Financial Tools**: Bitcoin providing financial services without physical limitations
- **Caregiver Independence**: Bitcoin reducing financial dependence on family support
- **Emergency Medical Fund**: Bitcoin as reserve for disability-related expenses
- **Employment Alternative**: Bitcoin services providing income despite employment barriers
### **Immigrants and Refugees**
- **Documentation-Free Access**: Bitcoin access without traditional banking requirements
- **Homeland Remittances**: Lower-cost money transfers to families in origin countries
- **Wealth Protection**: Bitcoin holdings immune to immigration status changes
- **Integration Capital**: Bitcoin accumulation for business creation and integration
- **Legal Fee Coverage**: Bitcoin gains funding immigration attorney costs
- **Family Support**: Bitcoin enabling financial sponsorship for family immigration
### **Military and Veterans**
- **Deployment Solutions**: Bitcoin for secure overseas military pay and family support
- **Stress Relief**: Bitcoin wealth building reducing financial anxiety
- **Benefit Optimization**: Bitcoin investment strategies using military benefits
- **Career Transition**: Bitcoin funding military-to-civilian transitions
- **Combat Pay Advantages**: Bitcoin using tax-excluded combat zone income
- **Family Security**: Bitcoin ensuring family stability during deployments
### **Religious Communities**
- **Faith-Based Investment**: Bitcoin as alternative to interest-based banking
- **Community Development**: Bitcoin for religious community investment
- **Charitable Enhancement**: Bitcoin appreciation increasing charitable capacity
- **Mission Funding**: Bitcoin donations supporting international missions
- **Pilgrimage Savings**: Bitcoin savings for religious pilgrimage expenses
- **Religious Freedom**: Bitcoin donations protecting religious liberty organizations
### **Divorced and Single Parents**
- **Support Independence**: Bitcoin reducing dependence on unreliable ex-spouse payments
- **Legal Fee Coverage**: Bitcoin gains covering divorce attorney costs
- **Asset Protection**: Bitcoin holdings protected from divorce proceedings
- **Emergency Fund**: Bitcoin as emergency fund for single parent crises
- **Education Savings**: Bitcoin accumulation for children's future education
- **Career Investment**: Bitcoin funding career development after employment gaps
---
## 10. Merchant and Business
At the till or checkout, Bitcoin competes with cards, cash, and local payment apps on cost, chargebacks, settlement speed, and whether customers actually want to pay in it. Industry and margin structure matter as much as ideology.
### **Small Business Owners**
- **Payment Cost Reduction**: Bitcoin acceptance saving 2-3% vs credit card fees
- **Customer Acquisition**: Bitcoin payments bringing new customers to businesses
- **Cash Flow Improvement**: Faster Bitcoin settlement vs traditional processing
- **Global Market Access**: Bitcoin enabling international transactions
- **Innovation Marketing**: Bitcoin acceptance for competitive differentiation
- **Independence**: Reducing dependence on traditional payment processors
### **E-commerce Retailers**
- **Fraud Prevention**: Bitcoin's irreversible payments eliminating chargeback risks
- **International Expansion**: Bitcoin simplifying global e-commerce
- **Customer Spending**: Bitcoin customers often spending more than traditional users
- **Payment Integration**: Seamless Bitcoin integration with e-commerce platforms
- **Cost Efficiency**: Reduced payment processing costs improving profitability
- **Market Leadership**: Early Bitcoin adoption positioning as innovation leaders
### **Professional Service Providers**
- **Premium Positioning**: Bitcoin acceptance signaling innovation and attracting clients
- **Global Services**: Bitcoin enabling international consulting payments
- **Cost Reduction**: Lower payment processing fees for high-value transactions
- **Client Acquisition**: Attracting Bitcoin-wealthy clients through cryptocurrency acceptance
- **Competitive Advantage**: Bitcoin acceptance differentiating in competitive markets
- **Technology Integration**: Modern payment systems enhancing practice operations
### **Restaurants and Hospitality**
- **Tourist Attraction**: Bitcoin acceptance attracting international travelers
- **Payment Speed**: Faster Bitcoin transactions improving customer service
- **Cost Savings**: Reduced payment processing fees vs traditional systems
- **Marketing Value**: Bitcoin acceptance generating social media attention
- **International Customers**: Bitcoin serving global travelers avoiding currency conversion
- **Future Preparation**: Adopting next-generation payment technology for positioning
---
# Who Controls Bitcoin
## Merge authority is capturable architecture
*A reference document for analytical reasoning about Bitcoin governance*
**Note on “one codebase” and node counts.** Reachable-node surveys in the 2025 to mid-2026 window often split clients (e.g. Bitcoin Core vs Knots; percentages shift with time and methodology). This document uses **99%** and **single lineage** to mean software traceable to the **Bitcoin Core codebase** (the Core project plus Core-derived forks that remain on Bitcoin), not a claim about every machine running the branded “bitcoind” binary. The structural claim is near-monoculture of that lineage and concentrated merge authority over its upstream.
---
## Contents
- [I. The Premise](#i-the-premise)
- [II. The Governance Reality](#ii-the-governance-reality)
- [III. The Funding Map](#iii-the-funding-map)
- [IV. The Personnel Revolving Door](#iv-the-personnel-revolving-door)
- [V. The Adversarial Layer: When Conflicts Become Visible](#v-the-adversarial-layer-when-conflicts-become-visible)
- [VI. The No-Spec Moat and Why It Matters](#vi-the-no-spec-moat-and-why-it-matters)
- [VII. The Structural Argument in Summary](#vii-the-structural-argument-in-summary)
---
## I. The Premise
Bitcoin is described, by default, as decentralized open-source software maintained by a global community of volunteers. That description is technically accurate and functionally misleading. **The network's consensus rules are decentralized. The development of the software that enforces those rules is not.** Roughly 99% of economic nodes run software from that single upstream lineage, overwhelmingly the Bitcoin Core project’s releases, with a minority on Core-derived forks that stay on Bitcoin. A small, interconnected group of funded developers decides what ships in that codebase. A smaller group holds merge authority. The people funding those developers have direct financial interests in specific protocol outcomes. When that funding map is examined alongside the personnel history and the decisions that have and have not been made over seventeen years, what emerges is not a conspiracy but **a structural capture vector:** through acculturated judgment, financial dependency, and the quiet exclusion of inconvenient arguments from legitimate venues.
This document presents the structural argument in full, supported by the adversarial funding and personnel evidence. It is intended as an analytical reference for reasoning about Bitcoin governance accurately. For a numbered argument map, see *[Bitcoin Governance: Argument Map](/articles/bitcoin-governance-argument-map)*. For why the structure produces these outcomes without requiring conspiracy, see *[The Social Layer Is the Attack Surface](/articles/bitcoin-social-capture)*.
---
## II. The Governance Reality
### The Implementation Monopoly
When the same upstream lineage supplies almost all economically relevant consensus nodes, **the distinction between Bitcoin the network and “whatever Bitcoin Core’s maintainers ship” becomes practically meaningless for what operators run.** The money rules are still what every node enforces. The program that holds those rules is still what that lineage releases. This is not a theoretical concern. CVE-2018-17144, an inflation bug that could have allowed Bitcoin to be created out of thin air, sat in production in Bitcoin Core for eighteen months. It sat unused on the chain. Another implementation replaying those blocks would have matched Core. Someone had to read the code to find it. The bug was in Core. **Core's monopoly is what made it dangerous.** Common defenses of that monopoly are addressed in *[Bitcoin Core: The Biggest Fallacies](/articles/bitcoin-core-the-biggest-fallacies)*.
A common objection points to miners: they may run any consensus-compatible software and need not adopt every release. That permission is real; the practiced behavior is not a distributed audit. Industrial mining largely follows operational defaults: pool infrastructure, hosting providers, and routine upgrades to stay compatible with peers and with the dominant client, rather than a deliberate, release-by-release review of consensus changes by the majority of hash rate. **A veto almost no one pays the cost to exercise is not the same as decentralized control over what merges.**
Bitcoin Core has never produced a formal mathematical specification of its consensus rules, and the network has never adopted one. Producing one inside Core's process has been attempted for years without meaningful progress toward an adopted specification. Without a specification, every alternative implementation must reverse-engineer undocumented behavior from Core itself, which means treating Core as the source of the rules even when the other program is built differently. That is not an accident. **Unspecified behavior creates a structural barrier to competition** that cannot be resolved without an independent mathematical specification. The absence of a spec is the mechanism that makes the implementation monopoly self-perpetuating. For the case for a human-readable formal specification, see *[Why Bitcoin Needs a Specification](/articles/why-bitcoin-needs-a-specification)*.
### The Merge Authority Structure
Seventeen years of Bitcoin Core governance data in [Bitcoin Governance Research](https://github.com/secsovereign/bitcoin-governance-research) document a **PR-weighted contribution Gini coefficient of ~0.851** historical / **~0.834** recent (and similarly extreme concentration in reviews, Gini ~0.92), with the **top three merger roles accounting for 81.1% of all-time historical merges** in the full-history rollup ([`findings/EXECUTIVE_SUMMARY.md`](https://github.com/secsovereign/bitcoin-governance-research/blob/master/findings/EXECUTIVE_SUMMARY.md), [`findings/GINI_COEFFICIENT_EXPLANATION.md`](https://github.com/secsovereign/bitcoin-governance-research/blob/master/findings/GINI_COEFFICIENT_EXPLANATION.md)). **Merge and commit permissions on [bitcoin/bitcoin](https://github.com/bitcoin/bitcoin) are authoritative;** the live roster is currently **five** merge holders. The structural point is unchanged: **a small, fixed-capacity set** of people can land code in the reference implementation, and **their institutional ties overlap the funding map**, including Chaincode employment, Brink grants, Spiral (Block’s Bitcoin arm), Localhost-style hosts, and similar channels. These are not anonymous volunteers in the aggregate; they are employees and grantees of a **small, identifiable** set of institutions, and those institutions have financial entanglements with commercial operations that benefit from specific protocol directions.
The informal merge authority structure means there is no formal process, no published criteria, and no accountability mechanism for what gets merged and what does not. Core developers disclaim ownership and authority over Bitcoin while exercising exactly that authority through PR closure and moderation. When critics name conflicts of interest on GitHub, they get moderated off. **That is not the behavior of a commons with no governance. That is governance defending itself.** Section V traces one contested change end to end.
Brink's own [Engineering Impact Report 2025](https://brink.dev/blog/2026/03/26/engineering-impact-report-2025/) documents that Michael Ford ("fanquake") merged **56% of changes in calendar year 2025** and led every major release from v28.1 through v30.0, published by the institution paying his salary as a funding success. The **2022+ window (5,747 merged PRs)** in [Bitcoin Governance Research](https://github.com/secsovereign/bitcoin-governance-research) shows the same shape (**50.2%** top-1, **70.4%** top-two, **82.2%** top-3; [`findings/GOVERNANCE_FRAMES.md`](https://github.com/secsovereign/bitcoin-governance-research/blob/master/findings/GOVERNANCE_FRAMES.md)). Those three percentages are not interchangeable. All-time top-three is 81.1%. 2022+ top-1 is 50.2%. Brink 2025 is 56%.
Fanquake also nominated Gloria Zhao for maintainership in June 2022, six months after Zhao had publicly endorsed expanding his GitHub owner permissions, including the ability to block accounts.
Since 2022 the named merger counts are fanquake 2,884, achow101 1,162, maflcko 676, glozow 313, sedited 262. Merge data keys on GitHub logins, which are unique.
Share of each author's merged work, since 2022, that passed through fanquake: theuni 73.3%, hebasto 72.7%, fanquake (self) 68.3%, willcl-ark 62.7%, maflcko 62.6%, sedited 53.7%, achow101 52.3%, glozow 52.0%. These are observational counts. Nobody is an appointed deputy. The MAINTAINERS file is a roster. The merge graph is the org chart.
Self-merge is **25.5%** of maintainer-authored merges. **45.1%** of those carry zero review, which is **11.6%** of all maintainer merges. Non-maintainers self-merge at 0%, being unable to. The spread is the argument. laanwj 77.1%, fanquake 50.4%, maflcko 35.0%. Five maintainers with over 1,200 merges between them have never self-merged. The "ordinary workflow" defense has to explain why most maintainers decline.
Merge authority decides what enters the codebase. Signing authority decides what users install. Of 339 releases, 286 were signed and 53 were unsigned. The source report does not explain the 53. Signing data keys on free-text names rather than logins, so three UID strings for the same person have to be collapsed. On the 282 published signer rows, Wladimir van der Laan 146 (51.8%), fanquake 55 (19.5%), Gavin Andresen 53 (18.8%), collapsed top-3 90.1%, top-5 98.6%. Four signed releases are unaccounted for in those rows, so the shares use 282 as the denominator. A previously published signer Gini of 0.545 used the unjoined name strings and does not apply to these collapsed counts.
First-PR outsider merge rate is about 29% all-time and about 16% since 2022. Established outsiders with five or more prior merges merge at about 69%. Median merge wait is 93.3 hours for maintainers and 145.4 hours for non-maintainers (1.41x). First review time is 12.3 hours versus 12.4 hours. Raw merge rates of about 80% maintainer against about 55% non-maintainer overstate the gap, because most of it is self-merge privilege rather than differential judgment. Peer-merge rates, excluding self-merges, are about 59% against 54% all-time, widening to about 63% against 51% since 2022.
### What the Quantitative Record Shows
The same research finds extreme merge concentration (authorship Gini ~0.851 historical / ~0.834 recent), high contributor churn (**90.7%** of **7,827** contributors inactive in the last year of the dump), and a pattern of governance paralysis on major protocol improvements that would have reduced dependence on the current institutional infrastructure.
That 90.7% is selection into a thin continuing core, not a dying project. Participants who never authored a PR exit at 95.3%, one-time contributors at 92.9%, PR authors at 81.6%, established authors at 58.1%, maintainers among the established set at 23.8%. High-merge-rate authors still exit at 83.0%, so quality does not retain.
Line authorship is a different ranking from merge share. On Bitcoin Core 32.1, Pieter Wuille last touched 44.2% of the non-blank lines in the consensus-rule files, and the median of those lines was last touched in 2017. The count is *[The Rules Are 7% of the Program](/articles/the-rules-are-7-percent)*.
Pair-level reviewer cohesion exists, but the joint-appearance counts are too small to treat as a voting machine ([`findings/CONFLICT_RESOLUTION_ANALYSIS.md`](https://github.com/secsovereign/bitcoin-governance-research/blob/master/findings/CONFLICT_RESOLUTION_ANALYSIS.md), [`findings/EXECUTIVE_SUMMARY.md`](https://github.com/secsovereign/bitcoin-governance-research/blob/master/findings/EXECUTIVE_SUMMARY.md)). Informal channels put topics on the table and GitHub finalizes. That flow was ~0.55 in the SegWit and Taproot years and **0.002** after 2022 ([`findings/GOVERNANCE_FRAMES.md`](https://github.com/secsovereign/bitcoin-governance-research/blob/master/findings/GOVERNANCE_FRAMES.md)). BIP-repo merge power is not Core merge power: **443** unique BIP mergers versus **23** on Core, and only **two** people sit in both top tens. For how paralysis became the durable outcome of the blocksize war, see *[Governance Paralysis Was The Victory](/articles/governance-paralysis-was-the-victory)*; for the stalled-proposals evidence list, see *[What Bitcoin's Stalled Proposals Tell You](/articles/what-bitcoins-stalled-proposals-tell-you)*. Review activity Gini sits near **0.92**. Many people review; almost nobody merges. Contributor accounts in Section III describe how funding dependency and institutional geography further narrow who sustains engagement in that dataset.
From findings/CONTRIBUTOR_TIMELINE_ANALYSIS.md. High churn: most participants with meaningful PR history do not stay active.
> The oligarchic structure is not a theoretical concern. It is documented across seventeen years of governance data. Reality overrides theory.
---
## III. The Funding Map
### Chaincode Labs
Founded in 2014 by Alex Morcos and Suhas Daftuar, both co-founders of Hudson River Trading, one of the world's largest high-frequency trading firms. Chaincode is self-funded by HRT trading wealth, meaning there are no external investors to disclose, but the entire operation flows from two algorithmic trading billionaires who decided to bankroll the gatekeeper layer of Bitcoin protocol development. Chaincode funds several Bitcoin Core contributors and runs the residency programs that serve as the primary pipeline into Core development.
Alex Morcos sits on the board of Coin Center, the D.C.-based cryptocurrency policy advocacy organization, giving Chaincode direct representation in the regulatory lobbying apparatus. Coin Center was itself seeded with funding from Andreessen Horowitz, Coinbase, Hudson River Trading, and Union Square Ventures. The same wealth that funds Chaincode also seeded the primary Bitcoin policy advocacy arm in Washington.
The Epstein connection is documented in the 2026 document release. A September 2014 email shows Jeremy Rubin introducing Joi Ito and Alex Morcos to Jeffrey Epstein, with Rubin writing that Morcos was a primary donor who helped organize fundraising. A 2016 email shows Rubin explicitly positioning Chaincode to Epstein as a prime example of innovative crypto R&D, with plans for a face-to-face meeting in New York. Epstein's web of influence extended through MIT's Digital Currency Initiative, which in 2015 became the institutional home for Bitcoin Core developers after the Bitcoin Foundation's collapse, with Epstein having donated $525,000 specifically earmarked for the DCI. The rescue of Bitcoin Core's institutional infrastructure after the Foundation's bankruptcy ran through an institution Epstein had directly funded.
Adam Jonas, Chaincode's current CEO, is documented as the intellectual architect of Brink, not merely a parallel figure. On October 16, 2020 (38 days before Brink's public launch), Jonas published a post arguing for a trusted nonprofit intermediary to fund Core developers, followed two days later by a detailed operational blueprint including IRS process, approval timelines, and template filings. His closing line was "Please do this." On launch day, Newbery acknowledged Jonas publicly: "Your initial research was what got the whole thing started." That acknowledgment does not appear in any Brink public materials, its IRS filings, or its launch press coverage. Jonas had also been hired into Chaincode by Newbery, his prior professional background being educational program design at the Flatiron School, not Bitcoin development. Newbery's stated reason for hiring him: "Jonas's background is in education. He was working in the Flatiron School and managing teams and projects there." The developer pipeline's chief architect was selected for program design expertise, not technical Bitcoin knowledge.
### Blockstream
Founded in 2014 by Bitcoin Core developers Gregory Maxwell, Pieter Wuille, Matt Corallo, Jorge Timon, and Mark Friedenbach, alongside Adam Back and venture capitalist Austin Hill. The founding team is literally drawn from the Bitcoin Core maintainer class, creating direct corporate interest in Core's technical direction from day one. Blockstream has raised $651 million at a $3.2 billion valuation across eight rounds, with investors including Reid Hoffman as a board member, Horizons Ventures (Li Ka-shing's fund), AXA Strategic Ventures, Digital Currency Group, Baillie Gifford, and Bitfinex. Jeffrey Epstein appears in investor databases as a Blockstream backer from the 2014 seed round, with that stake later divested due to, in the words of Adam Back, "potential conflict of interest and other concerns."
Blockstream directly employs Bitcoin Core developers. The personnel flow between Blockstream and Chaincode is continuous. Pieter Wuille co-founded Blockstream before moving to Chaincode as a full-time maintainer. Matt Corallo was an early Lightning developer at Blockstream before moving to Chaincode. Brink co-founder Mike Schmidt came from a product manager role at Blockstream. Brink's Director of Operations previously worked at Chaincode. These are not coincidences. They are the personnel structure of a tightly integrated institutional network.
### Brink
Founded in 2020 by John Newbery, who came out of Chaincode Labs, and Mike Schmidt, who came from Blockstream. Seeded by John Pfeffer and Wences Casares. Major subsequent donors include Coinbase ($3.6 million), Jack Dorsey's StartSmall initiative ($5 million over five years), and VanEck (5% of spot Bitcoin ETF profits). **Several** sitting Bitcoin Core maintainers have been funded through Brink. Nearly every developer who has entered the Core maintainer class since 2022 passed through Brink's fellowship or grant programs first. Brink is the primary selection filter for who gets to maintain Bitcoin's reference implementation.
Brink's Executive Director cited an independent grant committee as the governance safeguard for funding decisions, naming its members publicly on multiple occasions including Mike Schmidt, Gloria Zhao, Christian Decker, and David Harding. Zhao sat on the grant committee from March 2023 to March 2025 while simultaneously receiving Brink funding (a documented conflict of interest that was never formally managed. The committee's existence is contradicted by Brink's own federal filings: Schedule O of every IRS Form 990 from FY2020 through FY2023 states "The Organization did not have committees." The FY2023 filing carrying that declaration was submitted to the IRS in November 2024, ten months after Schmidt had publicly named the committee's members. Schmidt's explanation) that the committee is "Non-Governing" and therefore outside the 990's reporting requirement, is accompanied by the confirmation from Brink board member Jonathan Bier that no grant committee recommendation has ever been rejected.
Brink's founding decision, the selection of Gloria Zhao as its first fellow in December 2020, was made by a three-person board: Newbery, Schmidt, and Harding. Newbery had recruited Zhao, introduced her to the network, arranged her first meetings, and mentored her through nine months of development work before casting one of the three votes that made her Brink's first fellow. No conflict-of-interest process was followed. Two board members confirmed independently that no recusal was suggested or occurred. Harding, the third board member, had five months later co-designed the campaign to remove Luke Dashjr as BIP editor, a campaign Newbery publicly ACKed on the mailing list.
In December 2021, Newbery departed from both Brink and Bitcoin Core. According to two independent sources, the departure was not voluntary. Brink's IRS filing for FY2021 records the anomaly: Newbery received $359,044 in compensation that year (the largest single payment in Brink's documented history) compared to $0 the prior year. Schmidt's explanation is that this was deferred founding compensation. Whether any portion constitutes severance for an involuntary departure has not been confirmed or denied on the record.
John Pfeffer, one of Brink's founding donors, also invested in Alpen Labs, a ZK rollup project building on Bitcoin. Wences Casares, the other founding donor, also invested in Alpen Labs and is a founding donor to Localhost Research, the organization now housing two Bitcoin Core maintainers. These are people simultaneously funding the developers who govern the base layer and investing in commercial operations whose success depends on how those developers govern it.
Brink documents the first tier. In a later return appearance on The Bitcoin Infinity Show (2026), Jon Atack said he asked a South African contributor how he had become maintainer without a fixed desk at Chaincode, Brink, or Blockstream. Atack quoted the reply: the contributor had rotated through Core-affiliated offices on a roughly three month cycle, visiting every institution and every key person in turn. Nothing in Core's published process requires office rotation. Developers who will not relocate or stay on the road continuously are filtered out by geography and institutional access before technical merit gets a full hearing.
Contributors outside the funded pipeline describe a parallel filter: grant renewal pressure, inferred editorial lines, and decline after raising objections the institutions find inconvenient. See [§V](#suppression-and-exclusion) for documented cases.
### OpenSats and the Dorsey Concentration Problem
OpenSats operates with a nine-person volunteer board and presents itself as a decentralized funding vehicle. In 2024 it received $23.6 million in donations, of which $21 million, roughly 90%, came from Jack Dorsey's StartSmall initiative alone.
OpenSats 2024 donations by source
StartSmall 90%Other 10%
StartSmall (Dorsey)
~$21M
Total raised
$23.6M
Single-donor concentration in the primary public grant channel.
Dorsey's footprint across Bitcoin's governance infrastructure is wider than any other single actor. He is the dominant funder of OpenSats, a major donor to Brink, and the founder of Spiral, which **directly employs at least one Bitcoin Core maintainer with merge access**. He has also donated tens of millions to the Human Rights Foundation's Bitcoin Development Fund and Btrust. That means Dorsey's money touches a sitting maintainer directly through Spiral, the primary developer grant organization at 90% of its funding, and multiple secondary grant channels simultaneously. A single donor with that reach across the governance infrastructure represents a structural concentration of influence that has no parallel in Bitcoin's development history.
The 2140 Foundation, another organization appearing on "decentralization" slides, adds a further data point. Its co-founder thanked OpenSats, HRF, and Schmidt personally by name at its launch event: "as a personal shoutout I also want to mention Mike Schmidt from Brink." The organization cited as evidence of funding diversification credited Brink's director for its existence. Its primary sponsor is OKX, which also funds Brink, Vinteum, and direct grants to individual developers including Amiti Uttarwar and Marco Falke. One exchange funder; multiple logos on the same slide.
### Localhost Research
Launched in late 2024 with founding donors Mark Casey and Wences Casares and board members Matt Corallo and Denise Terry. Casares is simultaneously a founding donor to Brink, an investor in Alpen Labs (a ZK-rollup project), and now a founding donor to Localhost (the same funder appearing at both ends of the funding pipeline across multiple institutions. Casey is also a founding donor to Brink. Two logos on any decentralization slide; two funders behind both. Corallo, who sits on Localhost's board, previously co-founded Chaincode's developer residency before handing it to Newbery, worked at Blockstream, and is now a Spiral employee) connecting Localhost's governance directly into the full institutional chain. Localhost co-founder Ava Chow held Bitcoin Core merge access while housed there; Localhost co-founder Mark Erhardt ("Murch") co-hosts the Bitcoin Optech weekly podcast with Brink's Executive Director Mike Schmidt.
Casares, Casey donors; Chow merge access while housed
Funding and hosting institutions (§III). Narrative detail and primary sources in subsections above.
### The Connective Tissue
Bitcoin Optech serves a function the institutional table does not fully capture. Founded in 2018 and seeded by Wences Casares, John Pfeffer, and Alex Morcos (the same funders who would later seed Brink), Optech operates as the primary technical communication infrastructure of the network. Its weekly newsletter and recap podcast are co-hosted by Mike Schmidt (Brink's Executive Director) and Mark Erhardt ("Murch," Chaincode employee and Localhost co-founder). Steve Lee, Optech's co-founder, described its political function explicitly at founding: it was built in part to facilitate the "post-SegWit2X healing process." It is simultaneously a technical newsletter and an institutional bridge. The same two people who appear across the most consequential governance decisions (Schmidt at Brink, Murch at Chaincode and Localhost) share a microphone every week, framing the development narrative for the broader ecosystem. When the OP_RETURN uncap direction was set at the May 1, 2025 IRC meeting, Murch offered Optech as the communications vehicle before the meeting had ended. Schmidt hosted the Optech podcast the following week, presenting the change as a neutral technical correction. The communications infrastructure and the governance infrastructure are operated by the same personnel.
---
## IV. The Personnel Revolving Door
Institutional funding map (schematic)
Chaincode↔Blockstream
shared founders · cross-employment
Brink·OpenSats ~90% Dorsey
grants · fellowships · board overlap
Spiral·Localhost
Core maintainers · merge access
Schematic, not exhaustive. Shows documented employment, grant, hosting, and donor concentration described in §III–IV.
The pattern is not incidental. The people who fund Bitcoin Core development circulate through the same small set of institutions. Blockstream founders become Chaincode employees. Chaincode alumni found Brink. Brink's co-founder came from Blockstream. Brink's operations director came from Chaincode. **Current** merge holders map onto that same map (**Chaincode payroll, Localhost-style hosting, Spiral, Brink-funded paths**) in combinations that shift over time but **do not** dissolve the concentration. The governance research underlying these findings is published in [Bitcoin Governance Research](https://github.com/secsovereign/bitcoin-governance-research). The people deciding what ships in Bitcoin Core are employees and grantees of institutions whose founders and funders have direct financial interests in specific protocol directions. Contributor accounts of grant pressure and geographic filtering in Section III describe how that map operates from inside the pipeline.
The mechanism operating behind the revolving door is documented in primary sources with unusual specificity. The Optech dinner series, co-founded and organized by Newbery, functioned as a recruitment venue. Amiti Uttarwar met Newbery at an Optech dinner in early 2019, she had previously applied to Chaincode's residency and been rejected. After the dinner, she applied again and was accepted, to a cohort Newbery himself co-organized. Her first grant from Xapo was, by her own account, arranged by Newbery and Jonas. Her Chaincode mentor during the residency, AJ Towns, was simultaneously her manager at Xapo. The mentorship relationship converted directly into an employment relationship at the same institution.
Gloria Zhao's recruitment followed a parallel track. She had applied to Chaincode in 2019 and been rejected. By the end of 2019 she had decided to leave the blockchain space entirely and was planning to remove any mention of blockchain from her resume. In January 2020, Jonas cold-emailed her. Her initial response was "nah, nah, I'm good. I'm done." Jonas followed up by phone. She told him directly she was not interested. He arranged a Stanford meeting anyway. She agreed to attend partly out of curiosity. At that meeting she met Newbery and Uttarwar. Nine months of mentorship from Newbery followed, conducted in the same city. In December 2020, Newbery cast one of three votes to make her Brink's first fellow, without recusal despite recruiting and mentoring her. She became a Bitcoin Core maintainer nineteen months later.
Matt Corallo articulated the pipeline's governing principle publicly in April 2018, calling for Bitcoin community outreach to underrepresented groups, framing it as evidence-based quality improvement. He explicitly blocked a critic who called this "social-Marxist ideology." The same year he launched Chaincode's developer residency, he described recruitment as finding "alignment socially over time." When challenged in March 2026 about whether DEI had ever influenced a funding decision, he stated the criteria were intelligence, commitment, and contribution history. Both female residents of the 2019 Chaincode residency had full-time funding within weeks of completing it. No male resident did, except one who was offered a position at Chaincode directly.
[Bitcoin Governance Research](https://github.com/secsovereign/bitcoin-governance-research) quantifies the outsider side of that pipeline: first-PR contributors merge roughly **16%** of the time since 2022, while established outsiders with five or more prior merges merge roughly **68%** ([`findings/MAINTAINER_PREMIUM_REPORT.md`](https://github.com/secsovereign/bitcoin-governance-research/blob/master/findings/MAINTAINER_PREMIUM_REPORT.md)). The gate is entry and large novel work, not a blanket block on outside contribution once established.
This network is not assembled by explicit coordination but by the normal operation of financial incentives, social trust, and institutional gravity. People fund what they understand. They hire from networks they trust. They develop intellectual frameworks that align with the interests of the institutions they work for. No individual needs to be corrupt for the architecture to be capturable. The mechanism is structural, not conspiratorial.
> Power without a name is the most dangerous kind. "Bitcoin isn't governable" is the claim that protects the people who already govern it from being held accountable. It is a capturable structure that learned to call itself freedom.
---
## V. The Adversarial Layer: When Conflicts Become Visible
The funding map in Section III is not a static diagram. When a protocol change would benefit institutions already on that map, the same personnel, communication channels, and informal merge authority can move faster than the structure moves on improvements that threaten those interests. The 2025–2026 OP_RETURN controversy is the clearest documented case: a relay-policy change that benefited VC-backed base-layer data businesses, traced from a 2023 documentation amendment through merge over broad opposition. For PR-level chronology, see [hodlonaut's CAPTURE series](https://www.citadel21.com/the-merge) and [Antoine Poinsot's account](https://antoinep.com/posts/relay_policy_drama/). For measured blockspace impact, see *[The Achievable Floor, §VI](/articles/the-achievable-floor#vi-the-actual-floor)*. For what that burden costs node operators in dollars, see *[Full Cost of Running a Bitcoin Node](/articles/full-cost-of-running-a-bitcoin-node)*.
### The OP_RETURN Arc
**Documentation and framing (2023).** In June 2023, Marco Falke (newly funded by OKCoin and Paradigm) filed PR #27832, clarifying that `-datacarriersize` measures serialized `scriptPubKey` size. The PR body does not mention inscriptions. Witness and script-path inscription fields falling outside the setting is the effect. Falke filed it; AJ Towns and Greg Sanders ACKed; Gloria Zhao reviewed it; fanquake merged it over a NACK from Peter Todd. The change was not surfaced in Bitcoin Optech's recap podcast the week it merged, hosted by Brink's Executive Director. That same month, Zhao and Murch published an Optech series arguing that on-chain data publication cannot be prevented and should not live permanently in the UTXO set. The rhetorical frame deployed against Luke Dashjr's filter patch in 2024 was published before the patch existed.
**Filter patch and CVE (2023–2024).** Dashjr filed PR #28408 in September 2023 to extend `-datacarriersize` to witness and script-path data. He was not told the documentation had been narrowed four months earlier. The bypass was assigned [CVE-2023-50428](https://nvd.nist.gov/vuln/detail/CVE-2023-50428) in December 2023. When an external contributor filed a revert in January 2024, Towns, Falke, and Zhao closed it the same day. Zhao, Murch, and Towns then rejected Dashjr's filter patch using the post-amendment definition as baseline, without disclosing that the definition had changed. GitHub Issue #29187, Core's formal record of the CVE, remained open until October 2024, when Ava Chow closed it as "completed" without fixing the underlying code.
**Administrative sweep (October 2024).** The day Antoine Poinsot joined Chaincode Labs, he posted that the CVE record was being abused and should close. The next day, at a closed CoreDev PR session, Chow closed fourteen PRs in one afternoon, including inscription-related filter patches and Issue #29187. A Chaincode engineer banned an external critic within minutes. The NIST classification was extinguished administratively, not technically.
**Commission and advocacy (spring 2025).** Poinsot proposed dropping OP_RETURN limits on bitcoin-dev in April 2025, naming a ZK rollup project in the founding footnote. Peter Todd filed PR #32359 at Poinsot's request without payment disclosure. Prominent advocates for the change held disclosed financial ties to base-layer data businesses; comments requesting disclosure on the PR thread were marked ABUSE or OFF-TOPIC and hidden.
**Merge (May–June 2025).** The May 1 IRC meeting set direction toward uncap. Sanders filed PR #32406 the next day and had it locked to collaborators within seconds of announcement. A letter signed by 31 Core contributors reframed the existing 83-byte limit as "censorship" three days before merge. Gloria Zhao (who had rejoined Chaincode on March 31) merged PR #32406 on June 9 over 21 Concept NACKs. That ratio is not an anomaly in the research corpus: **2,671** conflicts across **20,166** PRs (**13.2%**), with disagreement often resolving by merge rather than acting as a veto ([`findings/CONFLICT_RESOLUTION_ANALYSIS.md`](https://github.com/secsovereign/bitcoin-governance-research/blob/master/findings/CONFLICT_RESOLUTION_ANALYSIS.md), [`findings/TEMPORAL_ANALYSIS_REPORT.md`](https://github.com/secsovereign/bitcoin-governance-research/blob/master/findings/TEMPORAL_ANALYSIS_REPORT.md)). Non-standard OP_RETURNs on chain jumped from roughly thirty in the four months before the public campaign to over thirteen thousand in May 2025 alone, showing the prior relay rule had real deterrence effect until the campaign announced its removal.
### Conflicted Advocacy on Blockspace Policy
The OP_RETURN fight exposed a recurring pattern, not a one-off. Figures with equity in base-layer data businesses publicly opposed consensus proposals that would restrict arbitrary embedding, while promoting capacity-expansion proposals such as dynamic block size schemes that would give those businesses more headroom. Testnet and early-mainnet rollup usage had already demonstrated that data-availability demand can consume a significant fraction of Bitcoin bandwidth before full adoption. Policy positions aligned with portfolio exposure without requiring explicit coordination. For the technical taxonomy of embedding channels and what consensus can close, see *[The Achievable Floor](/articles/the-achievable-floor)*. For why treating Bitcoin as general-purpose storage is a category error regardless of governance, see *[Bitcoin Is Not a Hard Drive](/articles/bitcoin-not-a-hard-drive)*. The consensus response specified as pre-proposals: *[Permanent Data Channel Closure](/bips/permanent-data-channel-closure)*, *[Static Per-Output Miner Fee](/bips/static-per-output-miner-fee)*, and *[Dynamic Escalation of the Per-Output Miner Fee](/bips/dynamic-escalation-per-output-fee)*.
### The Dual Positioning of Brink's Founders
John Pfeffer seeded Brink at founding and invested in Alpen Labs, a competing ZK rollup building on Bitcoin. Wences Casares seeded Brink at founding, invested in Alpen Labs, and is now a founding donor to Localhost Research, which **has housed multiple** Bitcoin Core maintainers. These are people on both sides of the funding-to-grantee pipeline simultaneously, with commercial interests in protocol directions that the grantees they fund are positioned to influence. The conflict of interest is not alleged. It is structural and documented.
### Suppression and Exclusion
The suppression mechanism used in the OP_RETURN controversy had a documented origin. In May 2024, Chaincode CEO Adam Jonas authored Bitcoin Core's moderation guidelines, confirmed by IRC logs where maintainer Ava Chow told the weekly developer meeting: "ajonas wrote some moderation guidelines as a place for us to start thinking about this topic." In the same meeting, a contributor named pinheadmz revealed he had already tested the guidelines against comments from the datacarrier size policy debate using ChatGPT. Jonas published a governance framework in October 2024 codifying the principle that "those with 'skin in the game' should ultimately have the loudest voices," endorsing Signal groups as preferred coordination and dismissing public IRC as having "showed limited utility and were eventually abandoned."
[Bitcoin Governance Research](https://github.com/secsovereign/bitcoin-governance-research) finds that closed-unmerged PRs most often die from **non-engagement**, not explicit NACK: the plurality close with **no formal review**, and in a high-prep outsider sample roughly **45%** never received one ([`findings/MAINTAINER_PREMIUM_REPORT.md`](https://github.com/secsovereign/bitcoin-governance-research/blob/master/findings/MAINTAINER_PREMIUM_REPORT.md), [`findings/EXECUTIVE_SUMMARY.md`](https://github.com/secsovereign/bitcoin-governance-research/blob/master/findings/EXECUTIVE_SUMMARY.md)). Silence is a governance outcome.
Three independent contributors who raised concerns the network found inconvenient experienced the same sequence: dismissal, sidelining, and a decline from which none fully recovered.
Jon Atack was among the five most prolific Bitcoin Core contributors globally by commit count in 2020 and 2021, despite contributing without affiliation to Chaincode, Brink, or any network institution. On [BIS #195](https://www.bitcoininfinityshow.com/bitcoin-core-from-the-inside-jon-atack-bis-195/), he explained withdrawing from co-authorship credit while pursuing Square Crypto funding to keep a low-controversy profile. In a later return appearance on The Bitcoin Infinity Show (2026), he described self-censoring for seven years while grant renewal sat in the background, Spiral declining to renew after four years, and a maintainer and senior developer going to the OpenSats board about his funding without telling him. His Brink grant application in June 2021 was rejected by phone two days after he raised a substantive objection to a PR Newbery had co-authored, an objection later vindicated. His contributions fell from top-four globally to near-silence. He described the result as "permanent doghouse status" extending to contributors who appeared friendly to him.
Vasil Dimov proposed himself as P2P and Networking maintainer in August 2022. He had built Bitcoin Core's privacy networking infrastructure including BIP155, Tor v3, and I2P support. Broad concept ACKs followed; his PR sat open for five months without comment from fanquake or Gloria Zhao despite direct public requests by name. In January 2023, achow101 switched from Concept ACK to NACK after consulting unnamed contributors privately. A cascade of retractions followed. Zhao posted her first substantive comment (five months in) framing opposition as a Brink conflict-of-interest concern, while herself a Brink grantee. Dimov closed the PR himself. The area he proposed to maintain has had no dedicated maintainer since.
Luke Dashjr has been Bitcoin's longest-serving BIP editor since 2012. In April 2021, Brink founding board member David Harding posted a formal plan including a call for Dashjr's resignation; Newbery ACKed within hours despite the motivating dispute already being resolved. Harding stated he would "continue to bring it up in every appropriate venue for years, if need be." On the OP_RETURN PRs in 2024 and 2025, Dashjr was muted. When he named a conflict of interest in a GitHub discussion thread, the commenter who supported his disclosure request was banned.
Atack summarized the pattern at PlanB Forum in early 2026: maintainerships are "practically pre-decided" by existing maintainers, and contributors who question the process get "moved out of the project."
---
## VI. The No-Spec Moat and Why It Matters
The most important structural element of the implementation monopoly is the one least discussed. Bitcoin Core has never produced a formal mathematical specification of its consensus rules. This is not an oversight but the mechanism that makes the monopoly permanent. Without a specification, any alternative implementation must reverse-engineer undocumented behavior from Core itself. This means Core remains what everyone else has to match, even for clients with a different architecture. Independent implementations are risky because a single validation bug can cause a chain split. So in practice, alternatives stay close to Core's codebase. Serious non-Core consensus implementations remain a **negligible fraction of deployed nodes** in public crawls, not enough to constitute real implementation competition, while everyone still validates against Core-shaped behavior without an independent spec. The market did not freely choose Core-derived code. It converged on the only option safe enough to run without a specification to validate against.
The "you can just fork it" response to governance critique is a non-answer in this context. A Core fork inherits the same monolithic architecture, the same implementation measured in *[The Rules Are 7% of the Program](/articles/the-rules-are-7-percent)*, the same undocumented consensus behavior, and the same governance capture vectors. New maintainers on the same throne are not a structural fix. The fix is multiple independent implementations with proven consensus compatibility and genuinely different governance structures. That requires a formal specification as the independent standard against which consensus compatibility can be proven. The absence of that specification, over seventeen years, is the structural condition that makes everything else in this document stable. See *[The Social Layer Is the Attack Surface](/articles/bitcoin-social-capture#vi-the-no-spec-moat-as-predictable-output)* for why the moat persists and *[Argument Map, Part XV](/articles/bitcoin-governance-argument-map#part-xv-what-alternatives-actually-require)* for what genuine alternatives require.
> Without a formal specification, the "you can fork it" response concedes the governance critique rather than refuting it. It acknowledges the enormous switching cost while offering it as proof that no governance problem exists.
---
## VII. The Structural Argument in Summary
Bitcoin's governance problem is not that bad people made bad decisions. **It is that the architecture is capturable regardless of who occupies the seats.** The mechanism operates through four interlocking components. Documented outcomes sit on that architecture: moderation of named conflicts, stall on one class of change, speed on another.
The no-spec moat makes implementation monopoly permanent by design. Without a formal specification, alternatives cannot prove consensus compatibility without depending on Core itself, which means the monopoly is structurally self-perpetuating.
Concentrated merge authority creates a small, identifiable group whose judgments determine what ships in the software that most of the network runs. Those judgments are not made in a vacuum. They are made by people whose salaries come from institutions with financial interests in specific outcomes.
The funding map creates layered conflicts of interest that are rarely disclosed and never institutionally managed. The same small group of funders appears on both sides of the governance relationship simultaneously, funding the developers who govern the base layer and investing in commercial operations whose success depends on how those developers govern it.
When these conflicts are named in public forums, critics are moderated off. That is not incidental but the behavior of a power structure defending itself. The combination of undisclosed conflicts, concentrated authority, and active suppression of critics is what a capturable architecture looks like in use.
The consequence is paralysis and, when paralysis fails to protect institutional interests, directed action. When the governance structure cannot process improvements that threaten the interests of the institutions funding it, those improvements die in review. [Bitcoin Governance Research](https://github.com/secsovereign/bitcoin-governance-research) documents the pattern in named dossiers: Erlay's full-protocol implementation set shows **0/7** matched PRs merged (scaffolding merges are not delivery; the open thread is a measurement fight, not silence); Dandelion's Core implementation PR closed unmerged after roughly eleven months because stem routing collided with the wallet's own RBF/CPFP and DOS surface ([`findings/STALLED_PROPOSALS_REPORT.md`](https://github.com/secsovereign/bitcoin-governance-research/blob/master/findings/STALLED_PROPOSALS_REPORT.md), [`findings/ARCHIVE_GEMS.md`](https://github.com/secsovereign/bitcoin-governance-research/blob/master/findings/ARCHIVE_GEMS.md)). When the governance structure can be moved to serve those interests (as in the OP_RETURN uncap, commissioned without disclosure by a Chaincode engineer and merged by a Chaincode employee over 21 Concept NACKs) it moves in weeks. **The same structure that stalled a qualified contributor's maintainer nomination for five months through undisclosed private consultations merged the OP_RETURN uncap in 38 days from mailing list post to merge.** The 56% merge concentration is no longer an estimate. It is published by Brink in its own Engineering Impact Report.
Stagnation on throughput, node cost, and payment-layer competitiveness created space centralized alternatives were happy to fill. Stablecoin transaction volume now exceeds Visa annually. Those are use cases Bitcoin should own. The governance structure left Bitcoin effectively unable to compete for them.
Implementation diversity is the structural fix, not a personnel change at Core. **Swapping one small maintainer cohort for another** without changing the monopoly implementation reproduces the same capture vector. For why that shape reconstructs itself from professional habit rather than from who occupies the seats, see *[The Vertical Layer Problem](/articles/the-vertical-layer-problem)*. The fix requires multiple independent implementations with proven consensus compatibility and different governance models, built from formal specifications that make the no-spec moat obsolete. That is not a small ask but exactly as hard as the governance problem predicts it would be.
---
## Further Reading
### On secsov.com
- *[The Vertical Layer Problem](/articles/the-vertical-layer-problem)*: the consensus layer is horizontal, the software that implements it is not
- *[Bitcoin Core: The Biggest Fallacies](/articles/bitcoin-core-the-biggest-fallacies)*: refutations of common monopoly defenses
- *[Governance Paralysis Was The Victory](/articles/governance-paralysis-was-the-victory)*: blocksize war outcome and implementation diversity path
- *[The Adversarial Default](/articles/the-adversarial-default)*: defense of toxic maximalism as immune system under capturable architecture
- *[What Bitcoin's Stalled Proposals Tell You](/articles/what-bitcoins-stalled-proposals-tell-you)*: research-complete improvements that never shipped
- *[Why Bitcoin Needs a Specification](/articles/why-bitcoin-needs-a-specification)*: human-readable spec as governance infrastructure
- *[Making Core Irrelevant](/articles/making-core-irrelevant)*: sequencing, economic-majority vs miner signaling, floor/mid/ceiling through 2028
- *[The Coordination Gap](/articles/bitcoins-hidden-crisis)*: social coordination vs technical consensus
### External
- [hodlonaut, "CAPTURE Article 1: The Network," Citadel21](https://www.citadel21.com/the-network), March 27, 2026
- [hodlonaut, "CAPTURE Article 2: The Lever," Citadel21](https://www.citadel21.com/the-lever), April 29, 2026
- [hodlonaut, "CAPTURE Article 3: The Merge," Citadel21](https://www.citadel21.com/the-merge), June 15, 2026
- [hodlonaut, X thread on Mike Schmidt's decentralization slide](https://x.com/hodlonaut/status/2079539699106943365), July 21, 2026
- [Bitcoin Governance Research, How to cut this corpus](https://github.com/secsovereign/bitcoin-governance-research/blob/master/findings/GOVERNANCE_FRAMES.md)
- [Bitcoin Governance Research, Archive gems](https://github.com/secsovereign/bitcoin-governance-research/blob/master/findings/ARCHIVE_GEMS.md)
- [Brink Engineering Impact Report 2025](https://brink.dev/blog/2026/03/26/engineering-impact-report-2025/), March 26, 2026
- [Adam Jonas, "Evolution of Bitcoin Core Priority Projects"](https://adamjonas.com/bitcoin-core-priority-projects), October 31, 2024
- [Antoine Poinsot, "Relay policy drama"](https://antoinep.com/posts/relay_policy_drama/)
- [Renaud Cuny, "Three Years of Spam," Blockspace Weekly](https://blockspaceweekly.substack.com/p/issue-3-three-years-of-spam), December 2025
- [CVE-2023-50428, National Vulnerability Database](https://nvd.nist.gov/vuln/detail/CVE-2023-50428)
*This document reflects analysis grounded in 17 years of Bitcoin Core governance data, public funding disclosures, documented personnel history, and primary source materials including GitHub records, funding announcements, and the 2026 Epstein document release.* Claims about specific individuals reflect documented institutional affiliations, not allegations of individual misconduct. For parallel failures where contributor reputation substituted for independent audit (hardware wallets and Core itself), see [Don't Trust, Verify](/articles/dont-trust-verify).*
---
# Bitcoin Governance: Argument Map
Numbered arguments for debate and analysis. Narrative evidence, funding maps, and primary sources are in *[Who Controls Bitcoin](/articles/bitcoin-governance)*; structural logic in *[The Social Layer Is the Attack Surface](/articles/bitcoin-social-capture)*. For why the adversarial culture is calibrated to that threat environment rather than a defect to be socialized away, see *[The Adversarial Default](/articles/the-adversarial-default)*. For refutations of the most common monopoly defenses in debate, see *[Bitcoin Core: The Biggest Fallacies](/articles/bitcoin-core-the-biggest-fallacies)*.
**Each numbered point is a standalone claim.** Use the cross-links for evidence; use this document for the argument structure.
---
## Contents
- [Part I. Structure and Power](#part-i-structure-and-power)
- [Part II. The Specification Problem](#part-ii-the-specification-problem)
- [Part III. "You Can Run Whatever You Want" Is Victim-Blaming](#part-iii-you-can-run-whatever-you-want-is-victim-blaming)
- [Part IV. Funding and Accountability](#part-iv-funding-and-accountability)
- [Part V. Governance Paralysis in Practice](#part-v-governance-paralysis-in-practice)
- [Part VI. Forced Participation](#part-vi-forced-participation)
- [Part VII. The OP_RETURN Case Study (2025)](#part-vii-the-op_return-case-study-2025)
- [Part VIII. Process as Veto (MtGox Case Study, 2025)](#part-viii-process-as-veto-mtgox-case-study-2025)
- [Part IX. Blocksize Wars and Institutional Capture](#part-ix-blocksize-wars-and-institutional-capture)
- [Part X. The Commons Problem](#part-x-the-commons-problem)
- [Part XI. The Talent Pipeline](#part-xi-the-talent-pipeline)
- [Part XII. Civil War as Architectural Output](#part-xii-civil-war-as-architectural-output)
- [Part XIII. The Digital Gold vs. Peer-to-Peer Cash Failure](#part-xiii-the-digital-gold-vs-peer-to-peer-cash-failure)
- [Part XIV. Competitive Consequences](#part-xiv-competitive-consequences)
- [Part XV. What Alternatives Actually Require](#part-xv-what-alternatives-actually-require)
- [Part XVI. Broader Implications](#part-xvi-broader-implications)
- [Part XVII. The Definitional Trap: Governance vs. Government](#part-xvii-the-definitional-trap-governance-vs-government)
- [Part XVIII. The 98%+ Kitchen Problem](#part-xviii-the-98-kitchen-problem)
- [Part XIX. Answering "You Can Just Ignore It"](#part-xix-answering-you-can-just-ignore-it)
- [Part XX. When Defenders Concede Every Fact](#part-xx-when-defenders-concede-every-fact)
- [Part XXI. The Language Analogy and Its Limits](#part-xxi-the-language-analogy-and-its-limits)
- [Part XXII. Blockspace Governance and Relay-Policy Failure](#part-xxii-blockspace-governance-and-relay-policy-failure)
---
## Part I. Structure and Power
1. **Merge authority is the actual governance mechanism, not miners or nodes.** **Five** people hold merge authority on the reference client ([bitcoin/bitcoin](https://github.com/bitcoin/bitcoin)) today (e.g. after Gloria Zhao stepped down from that role). **Live GitHub permissions are authoritative**; rosters change; this document does not enumerate names. They decide what code enters releases. If code never merges, there is nothing for nodes to signal for. The bottleneck is upstream of any user choice.
Full-history rollup. Merge authority is a fixed-capacity gate, not a diffuse volunteer pool.
2. **"Miners can run what they want and don't have to upgrade" misdescribes practice.** Miners can in principle run any consensus-compatible software and skip a release. In practice, industrial hash rate overwhelmingly follows the path of least operational friction: pool stacks, hosting providers, and automated deployment adopt new Core (or Core-derived) binaries on maintenance schedules. Most operators do not perform an independent line-by-line or consensus audit of every release; they stay compatible with peers, with pool software, and with what the dominant client ships. A theoretical veto that almost nobody exercises is not a distributed check on merge authority. It is latency dressed up as choice.
3. **A tiny maintainer set, not meritocracy: the oligarchy in practice.** Meritocratic by whose criteria? Defined by the **same people** who control merge authority. That is not meritocracy. That is oligarchy with a friendlier brand name.
4. **The menu problem.** Users choose from options Core provides, not from all possible options. "Just don't upgrade" is not deciding what features exist. It is choosing from the menu, not what gets put on it.
5. **Success likelihood correlates with maintainer proximity and social relationships.** Governance is political and relationship-driven: people go out of their way to stay credible with maintainers because outcomes depend on it. That is not necessarily improper; it is still a concentration of informal gatekeeping. Jon Atack, a Bitcoin Core insider since 2019, described those dynamics at the [Plan B Forum](https://rumble.com/v75tyny-bitcoin-code-governance-jon-atack-plan-forum.html). On funding self-censorship and the office path to maintainership, see [BIS #195](https://www.bitcoininfinityshow.com/bitcoin-core-from-the-inside-jon-atack-bis-195/), a later return appearance (2026), and points 19a and 58a below.
6. **The security assumption mismatch.** Bitcoin's network security model assumes adversarial nodes but not an adversarial **merge layer** (the small group that can land code in the reference client). **Merge holders are typically publicly identifiable** and often under **U.S.-adjacent jurisdiction**; that profile is **not modeled** as an adversary class in the system's usual security story. That assumption needs updating.
7. **The "rough consensus" definition is controlled by the same people who invoke it.** Ava Chow closed a PR because it "was obviously controversial and had no hope of reaching a conclusion acceptable to everyone." No external arbiter defines rough consensus. The maintainer defines it unilaterally and invokes it as justification for closure. That is unlimited discretion with a rule-shaped wrapper.
8. **The "janitorial function" framing versus material reality.** Maintainer-adjacent commentary has described merge ability as "more of a janitorial function than a position of power." The material reality is that this function determines what improvements are available for anyone to use. Janitorial framing obscures structural authority.
---
## Part II. The Specification Problem
9. **The reference client is the protocol in practice.** Core has never produced an independent mathematical specification sitting above what it ships, and the network has not adopted one. When almost all economic nodes run that lineage, the reference client and the protocol are functionally identical.
10. **The no-spec moat protects the incumbent structurally.** Without a formal specification, any alternative implementation must reverse-engineer undocumented behavior. This is not an accident. Unspecified behavior creates a structural barrier to competition that cannot be resolved without an independent mathematical specification.
11. **Code as specification means no independent verification.** When the code is the specification, there is no independent standard against which to verify correctness or detect consensus bugs before they ship. CVE-2018-17144 sat in production for 18 months. That is the consequence. For why a human-readable formal specification matters for governance, see *[Why Bitcoin Needs a Specification](/articles/why-bitcoin-needs-a-specification)*.
---
## Part III. "You Can Run Whatever You Want" Is Victim-Blaming
12. **The two actual paths and what each costs.** Option A: spend an inordinate amount of time and money reimplementing consensus that has never been formally specified in mathematics, and to date **no independent specification has been adopted as the operational standard the economy actually runs on**. Option B: fork Bitcoin Core and inherit the 32.1 implementation, 151,004 code lines with the rules as 7% of them, and 17 years of accumulated patches that Core itself is not funded enough to properly maintain. The count is *[The Rules Are 7% of the Program](/articles/the-rules-are-7-percent)*. Remember the inflation bug. Remember the wallet deletion bug. Developing and maintaining production code is not free.
13. **Structural barriers are not philosophical.** The barrier to alternatives is real. The no-spec problem, the monolithic architecture, the maintenance burden, and the absence of funding for pure replication work combine into a structural wall. Pointing at it is not paranoia. Building an alternative proves it.
14. **Core itself is underfunded to maintain what it has.** **L1 reference-client / protocol engineering grants (not total ecosystem spend):** roughly **$8.4 million** went to Bitcoin Core-related development in **2023** against a **~$2 trillion native-asset market cap**. **Ethereum L1 core development** in the **same year** is on the order of **$32 million** against a **much smaller** native-asset market cap at the time. The argument that alternatives should "just go build it" ignores that Core barely has the resources to maintain the existing codebase. (Pair **like with like**: protocol-layer funding vs protocol-layer funding; asset market cap vs asset market cap.)
15. **Active suppression of alternatives through social influence.** A Core developer killed Libbitcoin's funding by warning the prospective funder that alternatives are dangerous. This is veto power exercised through social influence, not formal authority. No power structure voluntarily diminishes itself.
---
## Part IV. Funding and Accountability
16. **The funding constellation has no coordination or user accountability.** Chaincode Labs, Blockstream, Spiral, Brink, OpenSats, HRF, MIT DCI, and Btrust fund Core development with no mechanism for user accountability, no coordination, and no obligation to the network they depend on.
17. **The funding-to-market-cap disparity is documented.** **Same pairing as §14:** **$8.4 million** (Bitcoin L1 / Core-oriented dev funding, **2023**) vs **~$2T** BTC market cap (**~0.42%** ratio). **Polkadot** (~**$16.8M** protocol/core-style spend, **2024**) vs **DOT market cap ~1.2% of BTC’s** at comparable snapshots. **Ethereum** ~**$50M** (**2024**) on similar **L1 client/protocol** definitions. Bitcoin is **among the most underfunded major L1s on a funding-to-native-market-cap basis** in this sample, not a claim about every possible definition of “protocol spend.”
L1 protocol funding per $1T native market cap (approx.)
Bitcoin
$4.2M
Polkadot
~$0.7M
Ethereum
~$125M
Normalized comparison from §14–§17 definitions. See Who Controls Bitcoin, quantitative record.
18. **Few merge gates vs enormous secured value.** [Bitcoin Governance Research](https://github.com/secsovereign/bitcoin-governance-research) documents **extreme concentration** in who authors and merges (e.g. **authorship Gini ~0.851** historical / **~0.834** recent, **review Gini ~0.92**, **top three merger roles 81.1% of all-time historical merges**, **2022+ top-1 50.2% / top-3 82.2%**; see [`findings/EXECUTIVE_SUMMARY.md`](https://github.com/secsovereign/bitcoin-governance-research/blob/master/findings/EXECUTIVE_SUMMARY.md) / [`findings/GINI_COEFFICIENT_EXPLANATION.md`](https://github.com/secsovereign/bitcoin-governance-research/blob/master/findings/GINI_COEFFICIENT_EXPLANATION.md) / [`findings/GOVERNANCE_FRAMES.md`](https://github.com/secsovereign/bitcoin-governance-research/blob/master/findings/GOVERNANCE_FRAMES.md)). Pair-level reviewer cohesion exists but **n is too small** to treat as a voting machine ([`findings/CONFLICT_RESOLUTION_ANALYSIS.md`](https://github.com/secsovereign/bitcoin-governance-research/blob/master/findings/CONFLICT_RESOLUTION_ANALYSIS.md)). **Merge rights** on the reference repo are **always a small, fixed-capacity set** (currently **five** merge holders on [bitcoin/bitcoin](https://github.com/bitcoin/bitcoin); confirm **live** permissions). Review labor is more spread than merge authority (review Gini ~0.92). Many people review; almost nobody merges. BIP-repo merge power is not portable to Core: **443** unique BIP mergers versus **23** on Core, **two** people in both top tens. Informal-before-PR flow was ~0.55 in 2015–21 and **0.002** after 2022. Separately, [`findings/CONTRIBUTOR_TIMELINE_ANALYSIS.md`](https://github.com/secsovereign/bitcoin-governance-research/blob/master/findings/CONTRIBUTOR_TIMELINE_ANALYSIS.md) (dataset [`findings/data/contributor_timeline_analysis.json`](https://github.com/secsovereign/bitcoin-governance-research/blob/master/findings/data/contributor_timeline_analysis.json)) analyzes **301** contributors who meet **≥5 authored PRs** and **average quality score ≥0.3**; of those, **72** are classified **active** and **229 inactive** (definitions per that pipeline: **PR-based**, full-history, **not** “commits in 2023”). Large commercial organizations employ tens of thousands of engineers on systems with comparable economic footprint; Bitcoin’s **permissioned merge bottleneck** and **thin sustained PR bench** sit on a **handful of merge keys** and a **small active cohort**. That gap is a **governance risk**, not “conservative engineering” by itself.
Concentration indexes (0 = equal share, 1 = one actor)
From contributor timeline analysis. Thin sustained bench relative to secured value.
19. **Pipeline control: developers on funder boards decide who gets funded next.** OpenSats has Core developers on its board making grant decisions. That is a closed loop. Brink dominates incubation. The funding pipeline is controlled by overlapping cohorts with no external accountability.
19a. **Funding shapes what contributors say before anyone sends a memo.** Contributors describe inferring editorial lines from grant renewal pressure, self-censoring to keep a low-controversy profile, and learning that funders discussed their grants without them present. See [Who Controls Bitcoin, §III–V](/articles/bitcoin-governance#iii-the-funding-map).
19b. **Brink's cited grant committee does not appear in federal filings.** Brink's Executive Director named an independent grant committee publicly, including Gloria Zhao while she received Brink funding. Schedule O of every Brink IRS Form 990 from FY2020 through FY2023 states "The Organization did not have committees." Brink board member Jonathan Bier confirmed no grant committee recommendation has ever been rejected. See [Who Controls Bitcoin, §III (Brink)](/articles/bitcoin-governance#brink).
20. **The liability contradiction.** The MIT license is what protects Core from liability for bugs like the wallet deletion incident. That license exists because Bitcoin is a commons. You cannot hide behind the commons when convenient and claim owner authority to exclude proposals when it is not.
21. **Institutional history: from Bitcoin Foundation to MIT DCI.** The Bitcoin Foundation collapsed amid scandals from 2012 to 2015. MIT DCI absorbed the developers with legacy finance partnerships intact, including donors with documented Epstein connections. Blockstream was funded by AXA. When the Foundation failed, DCI inherited the developers without cleaning the funding relationships.
22. **No published security standards, no OpSec requirements, no accountability for lapses.** Bitcoin Core has no published security requirements for maintainers, no OpSec audits, and no accountability framework when failures occur. After a **widely reported maintainer-account compromise**, much of the public response amounted to **“don’t click suspicious links”**, not a governance or OpSec remediation program.
23. **Maintainer account compromise: correlated failure risk.** A **Core maintainer with merge access** to software securing **trillions** in value **had that account compromised**. That role demands state-actor-level threat modeling. Poor public account security and poor development environment security are correlated because they reflect the same threat modeling judgment. Failures cluster in individuals, they do not distribute randomly.
24. **Luke Dashjr removal from security list: no process, no appeal.** Removed after a decade with no documented process and no accountability mechanism. Two trillion dollars in value runs on handshake agreements. Informal power becomes hierarchy when you need it most.
---
## Part V. Governance Paralysis in Practice
Stalled or deferred items with broad agreement
Improvement
Consensus
Status
Documented since
Wallet / node separation
Universal
Not shipped
~12 years
UTXO set commitments
Research-complete
Not shipped
2014
Full node sync burden
Symptom of above
~700GB (Nov 2025), growing
Solvable since 2014
Formal verification integration
Tooling exists
Not integrated into Core process
n/a
Networking upgrades
Clear wins, no opposition
Waiting in same limbo
n/a
Implementation vs consensus ossification
Conflated deliberately
Non-consensus fixes blocked
Ongoing
Stalled or deferred items with broad agreement (§25–31). Bottleneck is structural, not technical.
For the full stalled-proposals dossier and what shipping looks like from a formal spec, see *[What Bitcoin's Stalled Proposals Tell You](/articles/what-bitcoins-stalled-proposals-tell-you)* and *[Governance Paralysis Was The Victory](/articles/governance-paralysis-was-the-victory)*.
25. **Wallet and node separation: 12 years, universal agreement, not done.** Keyword PR totals are too noisy to cite as acceptance or rejection (`-disablewallet` and the kernel franchise are not a product split). The Dandelion close on [#13947](https://github.com/bitcoin/bitcoin/pull/13947) is the same bundle in prose: stem routing died against the wallet's RBF/CPFP and DOS surface. The bottleneck is structural, not a missing ACK.
26. **UTXO set commitments: the compounding opportunity cost.** Research-complete since 2014. Would reduce initial blockchain download by approximately 98% forever rolling forward. Every new node that syncs today pays the full cost of 17 years of chain history including all spam, paying in bandwidth and storage for data that UTXO commitments would have made irrelevant a decade ago. That cost compounds with every new node, every year, permanently.
27. **Full node size is now 700GB and growing.** As of November 2025 a full node requires approximately 700GB of storage. This is not a stable cost. It increases with every block. UTXO commitments would have capped that burden for new participants. Not implementing them means each successive year of new node operators pays a cost that was solvable in 2014.
28. **Formal verification infrastructure: exists, not integrated.** The tooling exists. The proofs can be written. Integration into Core's development process has not happened.
29. **Networking upgrades: clear wins, still waiting.** Improvements with obvious bandwidth benefits sit in the same limbo as contested proposals. Erlay's full-protocol PR set shows **0/7 merged** in [Bitcoin Governance Research](https://github.com/secsovereign/bitcoin-governance-research) dossiers; scaffolding merges are not delivery ([`findings/STALLED_PROPOSALS_REPORT.md`](https://github.com/secsovereign/bitcoin-governance-research/blob/master/findings/STALLED_PROPOSALS_REPORT.md)). The stall is a **measurement fight** (a NACK on efficiency versus the author reporting 20–50% savings), not an empty docket ([`findings/ARCHIVE_GEMS.md`](https://github.com/secsovereign/bitcoin-governance-research/blob/master/findings/ARCHIVE_GEMS.md)). The structure **has not reliably** distinguished between contested and uncontested. When coordination costs exceed any threshold, nothing ships.
30. **"What if something goes wrong" collapses under actual failures.** A **maintainer account was compromised**. The wallet deletion bug shipped to production. OP_RETURN was uncapped over significant opposition and with documented governance misconduct. "We can't risk improvements because something might go wrong" loses all force when the things going wrong are from inaction and from the decisions that did get made.
31. **Good and bad ossification deliberately conflated.** Consensus rules should be stable. Satoshi wrote that once 0.1 shipped, "the core design was set in stone for the rest of its lifetime." That sentence is about the consensus design, not about the rest of the program. In Bitcoin Core 32.1 the rules are 10,122 code lines and the implementation around them is 140,882. *[The Rules Are 7% of the Program](/articles/the-rules-are-7-percent)*. The slogan collapses those two things. The result is that obvious improvements with no consensus implications die alongside genuinely risky consensus changes. See [`findings/ARCHIVE_GEMS.md`](https://github.com/secsovereign/bitcoin-governance-research/blob/master/findings/ARCHIVE_GEMS.md).
---
## Part VI. Forced Participation
For the consensus-vs-policy distinction and which embedding channels consensus can close, see *[The Achievable Floor](/articles/the-achievable-floor)*. For quantified operator burden, see *[Full Cost of Running a Bitcoin Node](/articles/full-cost-of-running-a-bitcoin-node)*. The specified consensus stack: *[Permanent Data Channel Closure](/bips/permanent-data-channel-closure)*, *[Static Per-Output Miner Fee](/bips/static-per-output-miner-fee)*, *[Dynamic Escalation of the Per-Output Miner Fee](/bips/dynamic-escalation-per-output-fee)*.
32. **The actual problem with blockchain spam: you cannot opt out.** The problem is not that spam exists. It is that every full node must download, store, and validate all of it forever to participate in Bitcoin. Policy defaults and relay configurations are theater. Consensus validity is what matters.
33. **Spam filters do not resolve the structural problem.** Spam filters address only new spam. They do nothing about existing bloat. Every node operator today pays for all historical spam in bandwidth and storage. The only mechanism that would resolve this is UTXO commitments, which Core has not shipped.
34. **Spam as extortion.** Threatening to unleash a coordinated spam attack on the network unless a governance proposal is withdrawn is not a principled stand for permissionlessness. It is extortion.
---
## Part VII. The OP_RETURN Case Study (2025)
35. **Change merged despite broad, documented opposition.** The proposal was pushed through over opposition from Dashjr, Mow, and dozens of others. An open letter from 31 Core developers argued for the pro-removal position, meaning even the internal pro-change camp needed a letter to push it through. Community opposition was extensive, public, and named. It did not matter.
36. **Bitcoin Mechanic banned from GitHub for naming a conflict of interest.** On April 28, 2025, Bitcoin Mechanic tweeted: "Someone pushing for a major change to Bitcoin is affiliated with a company whose current exploit of Bitcoin was the motivation for the change. Pointing this out on the github discussion has resulted in me being banned." The contributor in question was a VC backer of a for-profit rollup project that posts data to Bitcoin's base layer and directly benefits from lifting the OP_RETURN limit. Raising a documented conflict of interest resulted in removal from the discussion platform.
37. **Luke Dashjr muted on the same PR.** A 15-plus year Bitcoin Core contributor was locked out of the discussion on the most contested change of 2025.
38. **GitHub meta thread documents mass bans.** The bitcoin-core meta repository contains a megathread documenting users banned for off-topic comments during the OP_RETURN debate. One participant wrote: "with extreme confidence I can say that this is the most contentious and contested upgrade that ever happened to bitcoin core. It's the most disputed. The most hated. The most criticized, ever. Yet it was done anyway."
39. **Auto-ban script targeting 13% of network peers.** A contributor published a public bash script to auto-ban all nodes running Bitcoin Knots, enacting a year-long ban on approximately 2,938 publicly reachable nodes representing about 13% of reachable Bitcoin peers. Policy disagreement was met with attempted network excision.
40. **Pattern matches blocksize wars.** Same suppression mechanics: opposition management, platform fragmentation, GitHub moderation used against critics, framing of dissent as illegitimate. Different proposal, identical governance behavior.
---
## Part VIII. Process as Veto (MtGox Case Study, 2025)
41. **A carefully constructed proposal received a spam lock.** Mark Karpeles submitted a pull request proposing a narrowly scoped consensus rule to recover 79,956 BTC stolen in the 2011 MtGox hack, with the activation height set to INT_MAX meaning the code does literally nothing without explicit community consensus. DrahtBot auto-closed it within hours and it was locked as spam before any substantive response appeared.
42. **CONTRIBUTING.md as unlimited discretion.** The document states consensus changes require discussion that is "extensive" and "widely perceived" as worthwhile, with the final arbiter being "the judgement of the maintainers." That is not a rule. It is unlimited discretion with a rule-shaped wrapper. No defined threshold. No accountable decision-maker. No appeal.
43. **Process violation has a correctable path; spam has none.** Applying the rule correctly would mean citing it with a link to the guideline and a clear path forward. Closing as spam tells the submitter nothing actionable and leaves no record anyone can reference. The distinction matters: a process violation can be fixed, a spam classification cannot.
44. **The mailing list redirect is not neutral routing.** Low traffic, high friction, dominated by people already inside the technical consensus, and produces no documented decision with binding weight. Redirecting an outside proposal to the mailing list is structural disadvantage dressed as procedure.
45. **Platform fragmentation is the structural output for outside proposals.** When a proposal gets closed on GitHub, redirected to the mailing list, discussed on X, mentioned on Bitcointalk, argued on Delving Bitcoin, and relitigated on the Bitcoin subreddit, the conversation splinters across five platforms with different audiences, norms, and signal-to-noise ratios. No single place can build the critical mass required to produce the consensus the process nominally requires. This is the predictable output of a governance structure that imposes maximum coordination cost on proposals originating outside the maintainer circle.
---
## Part IX. Blocksize Wars and Institutional Capture
46. **The small block position was technically stronger.** Preserving decentralization is what makes Bitcoin valuable. Larger blocks that raise node operation costs threaten that property. This is not the dispute. The dispute is whether the war itself was organic and whether the governance paralysis it produced was a side effect or the objective.
47. **Brian Armstrong email to Epstein investor network: primary source documentation.** An email from Armstrong to an Epstein-connected investor group explicitly frames the blocksize increase as a revenue play and characterizes original Bitcoin developers as obstacles. This is not pattern inference. It is a primary source document showing coordinated, revenue-motivated framing of the debate.
48. **The Epstein, MIT DCI timeline.** July 2014: Epstein provides Peter Thiel a detailed analysis of Bitcoin's "internal contradictions." April 2015: Joi Ito emails Epstein that MIT "used gift funds to underwrite this which allowed us to move quickly and win this round" and "take control of the developers." 2015 to 2017: the blocksize war **consumed the bulk of** governance bandwidth. Implementation diversity that Gavin Andresen had identified as critical **did not materialize at scale** in that window (whether from war fatigue, technical risk, or both); the **observable outcome** is the missing diversity, not a single causal story.
49. **Gavin Andresen's confidence threshold.** Andresen called for multiple independent implementations when Bitcoin was at $6 billion and the problem was tractable. A confidence threshold was set for when implementation diversity should be built. That threshold **was not met in practice** while the blocksize conflict **absorbed maintainer and community attention** that might otherwise have gone to **specification and multi-client work**. The claim is **opportunity cost**, not that no one could have built in parallel under counterfactual peace.
50. **CVE-2018-17144: the technical proof.** An inflation bug in Bitcoin Core sat in production for 18 months. It could have allowed Bitcoin to be created out of thin air. No block exploited it, so differential replay of the live chain would have matched Core. The find was in the source. The bug was in Core, not in Bitcoin. Core's implementation monopoly is what made the bug dangerous.
51. **Who benefits if L1 competitive upgrades stall?** Stablecoins: over $300 billion in market cap, 49% annual growth, over $33 trillion in annual transaction volume often compared to Visa (see **empirical sourcing** note: on-chain volume ≠ card settlement). Banks: trillions annually in transaction fees on legacy rails. States: Bitcoin framed as non-threatening digital gold rather than bearer money competing with state monetary monopolies. **Listing aligned interests is not proof of coordinated intent**; it maps **who gains when base-layer payment competitiveness moves slowly.** For **structure without conspiracy** and **outcomes without requiring individual malice**, see [Who Controls Bitcoin, IV. The Personnel Revolving Door](/articles/bitcoin-governance#iv-the-personnel-revolving-door) and [VII. Summary](/articles/bitcoin-governance#vii-the-structural-argument-in-summary).
52. **Paralysis as default outcome.** You do not need Bitcoin to make wrong decisions. You only need it to make no decisions. [Bitcoin Governance Research](https://github.com/secsovereign/bitcoin-governance-research) fair-cite dossiers include Erlay (**0/7** full-protocol PRs merged) and Dandelion (implementation PR closed unmerged); see [`findings/STALLED_PROPOSALS_REPORT.md`](https://github.com/secsovereign/bitcoin-governance-research/blob/master/findings/STALLED_PROPOSALS_REPORT.md) and [Who Controls Bitcoin, §VII](/articles/bitcoin-governance#vii-the-structural-argument-in-summary). The result can **function like** controlled opposition: revolutionary origin story, implementation that **defaults to** not shipping contested upgrades. The governance structure **tends to preserve** paralysis while merge bottlenecks and incentive maps in §51 persist. **Not every actor need intend that outcome.** Same **intent vs structure** distinction: [§IV](/articles/bitcoin-governance#iv-the-personnel-revolving-door), [§VII](/articles/bitcoin-governance#vii-the-structural-argument-in-summary).
53. **BCH failed as a solution.** Bitcoin Cash forked the chain and moved the same governance vulnerabilities to different maintainers with the same monolithic architecture, the same informal merge authority, and the same capture vectors. The problem was governance structure, not block size. See *[The Social Layer Is the Attack Surface, §VII](/articles/bitcoin-social-capture#vii-controlled-opposition-and-the-chain-fork-trap)*.
---
## Part X. The Commons Problem
54. **Bitcoin as a codebase commons and the authority/liability contradiction.** Core cannot claim authority to exclude proposals and simultaneously disclaim liability for bugs. The MIT license provides liability protection precisely because Bitcoin is a commons. You cannot invoke the commons when it protects you and deny it when it constrains you.
55. **Closing proposals as spam while claiming no authority to exclude.** Core developers regularly disclaim ownership and authority over Bitcoin while exercising exactly that authority through the PR closure and moderation process. Calling governance critique a DDOS is admitting inability to engage on merit.
---
## Part XI. The Talent Pipeline
56. **Brain drain mechanism.** Contributors funnel into Core because it is the only game. They hit blocked PRs, ossification culture, and political gatekeeping. They then either burn out and leave the industry entirely or redirect to altcoins where they can actually ship something. The altcoin ecosystem has absorbed enormous Bitcoin engineering talent through exactly this mechanism.
57. **Nobody gets paid to replicate.** The open source economy rewards innovation and improvement, not unglamorous consensus-correctness work. Pure replication has no intellectual reward and no natural funding mechanism. The incentive structure selects against the exact work that implementation diversity requires.
58. **Major alternative implementations to date each carried a distinct agenda.** Libbitcoin abandoned the UTXO set and mempool. Btcd prioritized its own architecture. The mindset required to build a pure consensus-compatible alternative with no improvement agenda is exactly what the entire pipeline selects against.
58a. **Office rotation as an unwritten maintainership path.** In a later return appearance on The Bitcoin Infinity Show (2026), Atack said he asked a South African contributor how he reached maintainership without a fixed Core-affiliated office and quoted the reply: rotation through those offices on a roughly three month cycle. The requirement appears in no published Core process. Points 56 through 58 describe a thin talent pool; geography and physical presence narrow it further. See [Who Controls Bitcoin, §III (Brink)](/articles/bitcoin-governance#brink).
59. **The talent pool is structurally thin before funding and gatekeeping constraints even apply.** The multi-domain requirement spanning C++, applied cryptography, distributed systems, security engineering, economics, and open source governance narrows the globally available pool to dozens to hundreds of people. This is not a Bitcoin-specific problem. It is a structural constraint on the entire development ecosystem.
---
## Part XII. Civil War as Architectural Output
60. **The monolith forces civil war as the only mechanism for change.** Any significant disagreement requires either winning inside Core or executing a contentious chain split with chain-split risk. Both paths carry enormous cost. The community normalized perpetual conflict as "how Bitcoin works" when it is actually an architectural constraint produced by having one implementation with no governance alternatives.
61. **"Who started it" framing protects the monolith.** The framing makes governance improvement advocates the aggressors rather than the people maintaining the structure that makes conflict inevitable. Pointing at the cage is not the same as building it.
---
## Part XIII. The Digital Gold vs. Peer-to-Peer Cash Failure
62. **Governance paralysis and the “digital gold” framing.** Full **causation** is messy: risk-off macro, custody products, fee markets, and **L1 throughput limits** all mattered. The narrower claim: the governance structure **could not process** the class of **base-layer (and tightly coupled) improvements** needed for **retail p2p cash at scale** at pace, while **“digital gold”** remained a narrative path that **did not require those upgrades to ship**. That **enabled** digital-gold positioning to dominate **by default** among public narratives. It does **not** mean governance alone **mechanically caused** every holder’s worldview.
63. **Lightning and trust (scope: typical retail / product reality).** For **many users** on **custodial wallets, exchanges, and routing-heavy retail flows**, Lightning **often** reintroduces **trusted-counterparty patterns** (custody, compliance, liquidity providers). **Self-custodied Lightning** remains viable for sophisticated operators; the critique targets **dominant product and UX patterns**, not a claim that the protocol **cannot** be used in a less trusted way.
64. **The unbanked contradiction.** "Bitcoin banks the unbanked" is incompatible with "self-custody is for the few." If the honest answer is that self-custody requires technical sophistication most people do not have, and that the alternative is custodial services that recreate traditional finance, then Bitcoin has not solved the problem it claimed to solve. Both claims cannot be true simultaneously.
65. **UTXOs-per-person arithmetic.** **Base layer alone** cannot serve **8 billion people** with **current on-chain throughput** for everyday micro-payments. **Scaling paths** (L2, channel design, blockspace policy) were the **realistic** routes under the “payments for everyone” story; **governance paralysis removed or delayed several of those paths in practice.** That is a claim about **shipped history and political viability inside Core’s process**, not that **no alternate design** is imaginable in theory.
66. **Stablecoins and the payment market.** Stablecoin growth rode **regulatory arbitrage, dollar unit-of-account demand, exchange plumbing, and UX**, not **merge authority alone**. Bitcoin’s **slow movement on base-layer throughput and payment-competitive features** was **necessary but not sufficient** for stablecoins to occupy that space: it **opened margin** centralized issuers exploited. The combined story is **alignment of incentives**, not a single-cause history.
---
## Part XIV. Competitive Consequences
67. **Stablecoin transaction volume now exceeds Visa annually.** Over $33 trillion in annual transaction volume, over $300 billion in market cap, growing 49% annually. These are use cases Bitcoin should own. Bitcoin's governance structure **left** it **effectively unable** to compete for much of that flow **on comparable product timelines** (see **empirical sourcing** note on volume definitions).
68. **CBDC rails and tokenized deposits filling governance voids.** Every governance failure that prevents Bitcoin from serving a legitimate monetary use case creates space for state-controlled alternatives. The governance paralysis is not neutral. It has a directional consequence.
69. **The compounding opportunity cost.** Each year that UTXO commitments did not ship, each year that node operation costs remained artificially elevated, each year of delayed improvements compounds into a larger gap between what Bitcoin is and what it could have been. The opportunity cost is not a fixed number. It grows.
70. **Bitcoin is not competing badly. Bitcoin is not competing.** The governance structure **has not allowed** the reference implementation path to **adapt quickly enough** to compete in several payment-adjacent markets. This is a **structural / process** condition, not a claim that **no Bitcoin use case** thrives.
---
## Part XV. What Alternatives Actually Require
71. **Forking Core is not a solution.** A Core fork inherits the same monolithic architecture, the same technical debt, and the same capturable-architecture vectors. New maintainers on the same throne are not a structural fix.
72. **Existing alternatives each fail for documented reasons.** Core-derived forks that stayed on Bitcoin have the same structural problems and more concentrated maintainer control. Luke's Knots followed a BLAKE2b proof-of-work hard fork and left Bitcoin. Btcd abandoned active development. Libbitcoin abandoned the UTXO set and mempool, requiring ecosystem retooling and accepting isolation. None of these are genuine alternatives.
73. **Mathematical specification is necessary, not optional.** The only way to prove consensus compatibility without inheriting Core's governance is to specify the consensus rules independently in mathematics and prove correctness against that specification. Differential testing against Core's historical behavior is the validation methodology that bridges the gap. See *[Why Bitcoin Needs a Specification](/articles/why-bitcoin-needs-a-specification)* for the verification-methodology argument.
74. **Differential testing proves what IBD cannot.** An Initial Block Download proves a node can sync. It does not prove the node matches the network's consensus rules, because IBD has no reference to compare against. Differential testing runs both implementations against the same blocks and treats any mismatch as a bug in the alternative. That is the proof of consensus compatibility. It is not optional. It is the only honest claim to consensus validity.
75. **Implementation diversity is the structural fix, not a personnel change at Core.** **Swapping one small maintainer cohort for another** without changing the **monopoly implementation + informal merge** structure reproduces the same capture vector. The fix is eliminating the single point of failure, which requires multiple independent implementations with proven consensus compatibility and different governance models.
Existing alternatives and the fix they fail to provide
Approach
Relationship to Core
Why not a structural fix
Fork Core
Same codebase lineage
Same architecture, debt, and merge capture
Knots
Core fork (~95% shared code)
Same structural problems; more concentrated control
Btcd
Independent implementation
Active development abandoned
Libbitcoin
Independent implementation
Dropped UTXO set and mempool; ecosystem isolation
Formal spec + differential testing
Independent mathematical standard
Required path; not yet deployed at scale (§73–74)
Existing alternatives and the fix they fail to provide (§71–75).
---
## Part XVI. Broader Implications
76. **Quantitative analysis over 17 years: data over theory.** The oligarchic structure is not a theoretical concern. It is documented in **[Bitcoin Governance Research](https://github.com/secsovereign/bitcoin-governance-research)** from Git history: **PR-weighted authorship Gini ~0.851** historical / **~0.834** recent (and **review activity Gini ~0.92**), **merge share** concentrated in a **tiny set of merger accounts** (**81.1%** of merges from **top three** in the full-history rollup; **50.2% / 82.2%** top-1 / top-3 in 2022+), **self-merge 25.5%** of 9,793 maintainer-authored merges, and **90.7%** one-year exit among 7,827 contributors; see [`findings/EXECUTIVE_SUMMARY.md`](https://github.com/secsovereign/bitcoin-governance-research/blob/master/findings/EXECUTIVE_SUMMARY.md), [`findings/GINI_COEFFICIENT_EXPLANATION.md`](https://github.com/secsovereign/bitcoin-governance-research/blob/master/findings/GINI_COEFFICIENT_EXPLANATION.md), [`findings/GOVERNANCE_FRAMES.md`](https://github.com/secsovereign/bitcoin-governance-research/blob/master/findings/GOVERNANCE_FRAMES.md), [`findings/RESEARCH_METHODOLOGY.md`](https://github.com/secsovereign/bitcoin-governance-research/blob/master/findings/RESEARCH_METHODOLOGY.md). Pair-level “voting blocs” are **suggestive only**. Those are **repository-activity metrics**, not every possible definition of “who is a developer.” Qualitative accounts from Core insiders about **process** (e.g. maintainer influence) can sit alongside those numbers without implying any insider **audited or endorsed** the Bitcoin Governance Research pipeline.
77. **Concentrated development is a FOSS-wide threat, not Bitcoin-specific.** Network effects override license terms. The "open source therefore free" framing ignores that infrastructure control matters regardless of license. The Linux Foundation facing pressure for identity verification requirements illustrates that open source projects with network effects face the same capture dynamics as closed ones.
78. **Geographic and jurisdictional concentration.** **Merge holders are typically publicly identifiable** and often under **U.S.-adjacent** jurisdiction. State-level compulsion does not require compromise. It requires a subpoena or a quiet conversation. Geographic and jurisdictional diversity among both maintainers and implementations is structural defense, not cosmetic.
79. **PoW and implementation diversity.** Proof-of-work and proof-of-stake face **different security and capture surfaces**; PoW does not make Bitcoin immune to **upstream software monoculture**. Governance failures that concentrate the reference implementation **erode part of what PoW is supposed to secure**, a **diversely validated** rule set, without claiming PoS and PoW are identical on every axis.
80. **Telling Bitcoin's governance truth is more useful than sugar-coating it.** If governance truth turns people off, lying will not help long-term. The protocol is sound. The development infrastructure needs work. New participants deserve accuracy, not marketing.
81. **Bitcoin needs ultra-conservative consensus rules and urgently better governance infrastructure.** These are not in tension. Conservative consensus rules are exactly right. The implementation monopoly, the governance paralysis, and the funding failure are separate problems that do not require touching the consensus rules to fix.
---
## Part XVII. The Definitional Trap: Governance vs. Government
*These arguments address the most common sophisticated deflection: conflating governance with government to deny that Bitcoin has governance at all.*
82. **Governance is not government. Etymology clarifies ordinary usage.** The word governance comes from the Greek kubernao, meaning to steer a ship. Plato applied it early in the Western tradition to how a state should be run. Governance means the mechanism by which decisions get made and a system is steered. **Any live system that persists is steered somehow**; the live question is **by whom and under what accountability**, not whether steering happens. Notably, Kubernetes, the container orchestration system, derives from the same Greek root. In ordinary English, the word concerns **steering**, not necessarily **coercion**.
83. **There is no ship without a helmsman.** If governance means steering a ship, and Bitcoin is moving in a direction, someone is steering it. The question is not whether the ship has a helmsman. The question is who the helmsman is, whether anyone knows their name, and whether anyone can hold them accountable for where the ship is going. Denying governance exists is claiming the ship steers itself.
84. **The conflation is doing political work.** Calling informal power "not governance" is not a neutral semantic position. It protects the people exercising that power from accountability. Once you accept that Bitcoin has no governance, nobody did anything wrong, nobody owes anyone an explanation, and the people who banned critics and buried conflicts of interest get to walk away clean. The definitional move has a beneficiary.
85. **Unnamed power is not absent power. It is unaccountable power.** Power does not need a name to be real. It needs a name to be seen. And power that cannot be seen cannot be contested. Defending unnamed power as a feature of Satoshi's design is defending the condition that makes capture permanent.
86. **The self-defeating competition argument.** A common defense holds that competition is always better than governance and that Bitcoin is ungovernable. It then names exit rights and competition between implementations as how Bitcoin should work. Those are governance mechanisms. It describes the cure while denying the disease exists. Competition between implementations IS a governance mechanism. Saying otherwise doesn't change what it is.
87. **"If it can be ignored it isn't governing anything" proves too much.** You can ignore the FDA too, if you are willing to accept the consequences. Exit rights do not erase the fact that power was exercised, a conflict of interest was buried, and a critic was banned for naming it. The test for whether something is governance is not whether it can be ignored. It is whether one group's decisions structurally shape the choices available to everyone else on the network.
---
## Part XVIII. The 98%+ Kitchen Problem
*These arguments address the claim that Knots provides meaningful competition to Core.*
Effective Core codebase share on reachable nodes (2025 to mid-2026)
77% + (22.5% × 95% Core code) ≈ 98%. Node share alone understates how much of the network runs the same implementation lineage.
88. **One kitchen is preparing 98%+ of the menu.** In the 2025 to mid-2026 window, Core ran on roughly 77% of nodes directly. Knots ran on roughly 22.5%. That Knots was 95% Core's codebase. That means one kitchen was preparing 98%+ of the menu, because the only other kitchen was using 95% the same recipes. Luke's Knots later followed a BLAKE2b proof-of-work hard fork and left Bitcoin. Core-derived forks that stayed on Bitcoin are still that Core kitchen. No dated measurement exists for what share stayed after the split. Nobody is forcing you to eat anything. But if one kitchen is preparing every dish on every menu in every restaurant in town, that kitchen is governing what you eat whether they hold a gun to your head or not.
89. **A Core-derived fork is the counterargument to Core's dominance. It is 95% Core. That is not a counterargument.** A Core-derived fork inherits Core's architecture, Core's codebase, and Core's technical debt. The only people who can maintain it are people who understand Core deeply enough to track its changes and merge them selectively. A bug that still lives in the shared code is a bug in the fork. Maintainers can patch after the fact. They cannot escape Core's architecture. If that architecture makes something impossible, the fork cannot do it either. Luke's Knots leaving Bitcoin on a BLAKE2b proof-of-work hard fork does not create a second Bitcoin implementation. That is not a free market in implementations. That is one implementation with a small permission slip to disagree on policy at the margins.
90. **The Knots surge proves the governance problem, not refutes it.** Knots peaked at 25.45% of reachable nodes on September 14, 2025, according to [Coin Dance](https://coin.dance/), as a direct response to the 2025 OP_RETURN decision. That was the largest coordinated user response in Bitcoin's recent history, triggered by one policy decision made by a handful of people with no accountability mechanism. Thousands of node operators had to mount a significant response just to push back against a change they didn't consent to. That is governance working badly, not the absence of governance.
91. **The safety constraint reproduces Core's authority in every alternative.** Independent implementations are risky because a single validation bug can cause a chain split. So practical diversity stays close to Core's codebase. **Serious non-Core consensus clients are a negligible share of what operators actually run** on public node crawls, too small to behave like a competitive discipline, while the ecosystem still **implicitly treats Core as the reference**. That is not a free market in implementations **and** a separate safety story; the same structure produces both.
92. **The no-spec moat makes the safety constraint permanent without intervention.** Core has never produced a formal mathematical specification of its consensus rules. Efforts to develop one inside Core's process have continued for years without an adopted specification. Without a spec, every alternative has to reverse-engineer undocumented behavior from Core itself, which means staying dependent on Core by definition. **The effect is self-reinforcing:** it is what makes the implementation monopoly self-perpetuating **without a countervailing mechanism** (formal spec, funded diversity), whether or not anyone intended that lock-in.
---
## Part XIX. Answering "You Can Just Ignore It"
*These arguments address a common position: that the ability to exit proves there is no governance.*
93. **The 22.5% proves the cost, not the freedom.** When the evidence offered for a free market is that 22.5% of node operators, in the 2025 to mid-2026 window, staged a significant coordinated response to one decision by a handful of maintainers, that proves exit is expensive and exceptional, not easy and routine. A genuinely free market doesn't require a revolt to change suppliers.
94. **Building around the problem is evidence the problem was real.** Bitcoin Commons spent seven months building a ground-up Rust implementation from a formal mathematical specification precisely because ignoring Core's process while staying on its codebase is not a real alternative. That is the cost the governance problem predicts. One kitchen. Enormous switching cost to cook your own food. Not a gun. Still power.
95. **The absence of coercion is not the absence of governance.** Elinor Ostrom won the Nobel Prize in Economics for demonstrating that commons can be governed successfully through voluntary, self-organized institutions with no coercive authority whatsoever. Her work documented hundreds of cases. The question is not whether Bitcoin's governance uses coercion. The question is whether it has the properties Ostrom identified as necessary for commons governance to work: visible rules, visible decision-making, accountability to participants, and genuine alternatives. Bitcoin currently fails most of those tests.
96. **Ostrom's failure modes describe Bitcoin's current situation closely.** Ostrom documented how commons fail: rules are invisible, decision-making is captured by a small group, participants cannot see who is making decisions on their behalf, and exit options are theoretical rather than practical. A small group controls what 77% of the network ran in the 2025 to mid-2026 window, banned critics for naming conflicts of interest, and kept Core from adopting a formal spec for seventeen years. That is not friction. That is Ostrom's failure pattern.
97. **Good governance and formalized government are not the same thing.** The goal is not foundations, steering committees, or stakeholder processes. Those are capture vectors. The goal is the same thing Ostrom's successful commons had: visible rules, visible decision-making, accountability to participants, and genuine alternatives so that exit is real rather than theoretical. That is compatible with everything Bitcoin's defenders claim to value. It is what they are not currently delivering.
Ostrom's successful-commons criteria
Ostrom requirement
Bitcoin Core development today
Visible rules
Informal process; no adopted formal consensus specification
Critics moderated off conflicts; no appeal mechanism
Genuine alternatives
Core lineage runs ~98%+ of nodes; exit is costly and exceptional
Ostrom's successful-commons criteria applied to reference-client governance (§95–97).
---
## Part XX. When Defenders Concede Every Fact
*These arguments address the endgame when sophisticated defenders concede all the material facts and argue only about the label.*
98. **Conceding the facts and arguing the label is conceding the argument.** When a defender agrees that one dominant kitchen exists, that disproportionate influence is real, that critics were banned, that a formal spec was blocked for seventeen years, that switching costs are enormous, and then argues only that you should not call this governance, the substance of the argument is over. The word is now doing accountability work, not descriptive work.
99. **Unnamed influence framed as non-power.** A sophisticated defense characterizes the relevant influence as having "no name and no authority precisely so it can never become legitimate power." That is not a defense of decentralization. It is a defense of unaccountable influence: power that refuses identification refuses accountability. Unnamed power does not stay contestable. It stays invisible.
100. **Power without a name is the most dangerous kind in this context.** "Bitcoin isn't governable" is the claim that protects the people who already govern it from being held accountable. It is a political position that benefits exactly the people it refuses to name. That is not a neutral semantic preference. That is capture that learned to call itself freedom.
---
## Part XXI. The Language Analogy and Its Limits
*These arguments address the claim that Bitcoin is like a language with no governance.*
101. **Languages do have governance where stakes are high enough.** Legal English, medical terminology, and financial contracts are heavily standardized precisely because precision matters when money and lives depend on it. The claim that languages have no governance is only true for casual speech. Bitcoin is the high-stakes version of language. High stakes are exactly what create the power Core maintainers hold.
102. **People coming to agreement is governance.** Voluntary consensus, exit rights, competing implementations, people deciding together what words mean, these are all governance mechanisms. Describing them while arguing governance doesn't exist is self-defeating: those mechanisms are what governance is. The question has never been whether governance should be coercive. The question is whether the current informal governance is visible, accountable, and contestable.
---
## Part XXII. Blockspace Governance and Relay-Policy Failure
*These arguments address the blockspace governance crisis of 2025 to 2026: relay-policy collapse, consensus paralysis, and design-purpose drift. For the documented OP_RETURN timeline, see [Who Controls Bitcoin, §V](/articles/bitcoin-governance#v-the-adversarial-layer-when-conflicts-become-visible). For measured impact, see [The Achievable Floor, §VI](/articles/the-achievable-floor#vi-the-actual-floor). For operator cost accounting, see [Full Cost of Running a Bitcoin Node](/articles/full-cost-of-running-a-bitcoin-node). For the design-purpose argument, see [Bitcoin Is Not a Hard Drive](/articles/bitcoin-not-a-hard-drive). The consensus stack that implements that response: [Permanent Data Channel Closure](/bips/permanent-data-channel-closure), [Static Per-Output Miner Fee](/bips/static-per-output-miner-fee), [Dynamic Escalation of the Per-Output Miner Fee](/bips/dynamic-escalation-per-output-fee).*
103. **The policy enforcement collapse.** For approximately 14 years, the blockspace policy against non-monetary data held because Bitcoin Core's single dominant implementation enforced it. Relay bypass infrastructure (direct submission APIs, alternative relay networks, private pool peering) hollowed enforcement before inscriptions arrived. Core v30's OP_RETURN uncap ratified a surrender the infrastructure had already produced; it did not cause the failure. The correct engineering response was to move protections to consensus. The actual response was to remove the policy and call it pragmatism. That consensus response is specified in *[Permanent Data Channel Closure](/bips/permanent-data-channel-closure)* and the per-output fee pre-proposals.
104. **When documented consensus proposals stall.** Full-chain analysis now exists at scale. Proposals to cap dedicated embedding channels at consensus can cite that record and face no credible technical refutation. Activation support nonetheless stays negligible. When empirical support cannot convert into forward movement against coordinated social pressure and incumbent inertia, the bottleneck is governance structure, not technical merit.
105. **The impedance mismatch.** Bitcoin's original OP_RETURN limit was intentional friction between Bitcoin's design as a settlement layer and demand to use it as a subsidized data bus. Removing the limit accommodates a governance capture outcome, not revealed legitimate demand. That premise was never established. See *[Bitcoin Is Not a Hard Drive, §II and §VII](/articles/bitcoin-not-a-hard-drive#ii-the-type-confusion)*.
---
*105 arguments across 22 sections. Last updated July 2026.*
---
# The Social Layer Is the Attack Surface
## Table of Contents
- [Preface](#preface)
- [I. The Paradox](#i-the-paradox)
- [II. What Social Enforcement Actually Means](#ii-what-social-enforcement-actually-means)
- [III. The Protocol Is Permissionless. The Social Layer Is Not.](#iii-the-protocol-is-permissionless-the-social-layer-is-not)
- [IV. Social Graphs Are Targets](#iv-social-graphs-are-targets)
- [V. The Blocksize War as Case Study](#v-the-blocksize-war-as-case-study)
- [VI. The No-Spec Moat as Predictable Output](#vi-the-no-spec-moat-as-predictable-output)
- [VII. Controlled Opposition and the Chain Fork Trap](#vii-controlled-opposition-and-the-chain-fork-trap)
- [VIII. The Permissionless Mythology as Defense System](#viii-the-permissionless-mythology-as-defense-system)
- [IX. Structural Capture Does Not Require Bad Actors](#ix-structural-capture-does-not-require-bad-actors)
- [X. What Proof Requires and What It Implies](#x-what-proof-requires-and-what-it-implies)
---
## Preface
This document addresses the structural logic underneath Bitcoin's governance problem. The evidentiary case, the funding maps, the personnel history, and the primary source documentation live in **[Bitcoin Governance Research](https://github.com/secsovereign/bitcoin-governance-research)** and in the on-site articles *[Who Controls Bitcoin](/articles/bitcoin-governance)* and *[Bitcoin Governance: Argument Map](/articles/bitcoin-governance-argument-map)*. This document is concerned with why the structure produces the outcomes it produces, regardless of individual intent.
For the fiscal and access-layer frame (why states capture assets through ownership rather than destruction, and how the industry built the surveillance infrastructure voluntarily), see the companion piece *[The Last Uncaptured Asset](/articles/the-last-uncaptured-asset)*.
---
## I. The Paradox
Bitcoin is described as trustless. That description is both the most important thing about it and, taken too literally, **the source of a dangerous confusion.**
Bitcoin did not eliminate trust. **It redistributed it.** The protocol replaced trust in banks, governments, and payment processors with trust in mathematics, distributed computation, and the collective agreement of network participants to enforce a common set of rules. That is a genuine achievement and it is the foundation of Bitcoin's value as sound money. But redistribution is not elimination. The trust went somewhere, and where it went has a surface that can be manipulated.
This is the paradox at the center of Bitcoin's governance problem. **The same social layer that makes Bitcoin's rules enforceable also makes those rules vulnerable** to the forces that shape every other social layer: funding, credentialing, platform control, and the accumulated weight of institutional interest.
---
## II. What Social Enforcement Actually Means
Start at the bottom of the stack.
The 21 million cap is not a law of nature but a rule that every participant in the network agrees to enforce by running software that rejects blocks violating it. The proof-of-work difficulty adjustment, the block reward schedule, the UTXO model: none of these are written into the structure of the universe. They exist because people keep running software that enforces them, and because other people keep accepting outputs from that network as valuable on the basis that the enforcement is real.
**The cryptography enforces the math. The social layer enforces the cryptography's relevance.** Strip the social agreement away and the cryptography becomes an elaborate puzzle with no monetary significance. Bitcoin is worth what it is worth because enough people agree that the rules are real, that they will continue to be enforced, and that no one can unilaterally change them. That agreement is social. It happens to be expressed through cryptographic coordination, but the coordination serves the agreement rather than replacing it.
Satoshi understood this. The design is not an attempt to escape the social substrate but to restructure it so that the incentives for maintaining the rules are distributed broadly enough that no single actor can corrupt them. The genius is in how those incentives are aligned, not in somehow making Bitcoin independent of human agreement. Satoshi built a social institution with unusually robust properties, which is a different and more interesting thing than building something that transcends social reality entirely.
The distinction matters because it locates the attack surface accurately. Bitcoin's cryptography has not been broken and is unlikely to be. **The attack surface was never there.** It is in the social layer, specifically in the mechanisms that determine what software gets written, what changes get made, who gets funded to do the work, and whose voices shape what counts as legitimate participation in the network's development. For a concrete case where credentialed endorsement substituted for verification on the seed generation path, see *[Don't Trust, Verify](/articles/dont-trust-verify)*.
---
## III. The Protocol Is Permissionless. The Social Layer Is Not.
The most effective ideological defense Bitcoin has is the conflation of two things that are genuinely different.
The Bitcoin network is permissionless. Anyone can transact. Anyone can run a node. Anyone can mine. The base layer enforces no identity requirements, no institutional approval, no permission from any authority. This is true and it is important.
**The Bitcoin development process is not permissionless in any meaningful sense.** Getting a proposal taken seriously requires social legitimacy among the people who control the channels through which proposals move. Getting funded to build alternative implementations requires social legitimacy with funders who have decided, by and large, that Core's existing structure is not a problem worth solving. Getting criticism heard requires not being removed from the platforms where the criticism would matter. Getting code merged requires the approval of a small number of people whose judgments are shaped by the same funding relationships and social networks that shape everything else.
Permission in this context is not called permission but legitimacy, or rough consensus, or community acceptance. The word changes but the function is identical. **A social layer that determines whose contributions count, whose criticisms are heard, and whose proposals advance is a permissioned layer** regardless of what it calls itself.
Two layers, two permission models
Bitcoin network
Anyone can transact
Anyone can run a node
Anyone can mine
Core development
Proposals need social legitimacy
Funding flows through funder networks
Merge requires maintainer approval
The conflation of the left column with the right is the move that makes structural critique sound like confusion.
The conflation of network-layer permissionlessness with development-layer permissionlessness is the move that does the most political work in Bitcoin discourse. Once accepted, it makes structural critique impossible by framing it as a misunderstanding.
"Anyone can fork it" sounds like a complete answer until you examine what forking actually requires: a consensus-compatible implementation without a formal specification to validate against. That means reverse-engineering undocumented behavior from the incumbent and treating that incumbent as the definition of correct behavior, even if the new program is built differently. The exit right was theoretical for seventeen years because the conditions for exercising it safely did not exist. Pointing to the absence of anyone exercising it as proof that the freedom was real is circular.
---
## IV. Social Graphs Are Targets
A developer community has identifiable nodes of disproportionate influence. It has credentialing mechanisms that determine whose technical judgment is treated as authoritative. It has funding pipelines that shape what work gets done. It has platform hierarchies that determine where important conversations happen and who can participate in them. All of these are manipulation surfaces that require no technical access whatsoever.
The methodology is not novel. Academic institutions provide both credentialing authority and a plausible non-intelligence funding mechanism. When the right institution funds the right research program at the right moment, the effects propagate through the community through entirely ordinary social mechanisms. Researchers learn what gets funded. Developers learn what gets merged. Critics learn what gets them removed from venues where their criticism would matter. No handler required.
The concentration that makes Bitcoin's governance structurally fragile also makes its social graph unusually easy to map and influence. Concentrated social graphs require fewer interventions to shift than distributed ones. That is not a coincidence that should be dismissed. The outputs look coordinated whether or not anyone coordinated them. For how developer coordination failure becomes an existential vulnerability at Bitcoin's current scale, see *[The Coordination Gap](/articles/bitcoins-hidden-crisis)*.
---
## V. The Blocksize War as Case Study
The blocksize war of 2015 to 2017 is the clearest documented example of what social graph manipulation produces when applied to Bitcoin's developer community.
The surface dispute was about block size. The structural outcome was the permanent consumption of all governance bandwidth at the exact moment when implementation diversity was most tractable. Bitcoin was valued at a few billion dollars. The technical problem was manageable. The window for building independent implementations that could have resolved the implementation monopoly was open. The war closed it.
Primary source documentation exists for the coordinated institutional interest in shaping that outcome: emails placing legacy financial institutions in direct contact with the developers and institutions involved in the debate; funding relationships between the organizations arguing for specific technical outcomes and the commercial operations whose revenues depended on those outcomes; academic institutions whose rescue of Core's development infrastructure after the Bitcoin Foundation's collapse was financed through channels with documented conflicts of interest.
The point is not that the small block position was wrong. Preserving decentralization is genuinely important and the arguments for it are technically sound. **The point is that the war itself, regardless of which side was correct on the technical merits, consumed the governance bandwidth that implementation diversity required and produced governance paralysis as its durable output.** You do not need Bitcoin to make wrong decisions. **You only need it to make no decisions.** Paralysis was a victory condition for every institutional interest threatened by functional peer-to-peer money, and the blocksize war delivered it. For the full narrative on that outcome and the path to implementation diversity, see *[Governance Paralysis Was The Victory](/articles/governance-paralysis-was-the-victory)*.
Whether that outcome was coordinated or emergent from the collision of financial interests that happened to align is ultimately less important than the structural reality it produced. The outcome is identical in both cases and it is documented.
---
## VI. The No-Spec Moat as Predictable Output
Bitcoin Core has never produced a formal mathematical specification of its consensus rules. Seventeen years of technically capable, well-funded developers working on software that secures trillions of dollars of economic value, and the network has not adopted one.
The usual explanation is that a specification would ossify the protocol, or that the code is the specification, or that the problem is harder than it looks. None of these explanations survive contact with the incentive structure underneath them.
A formal specification would make it possible for alternative implementations to prove consensus compatibility without inheriting Core's codebase. It would break the architectural dependency that keeps every alternative tethered to Core by definition. It would transform the "just build an alternative" dismissal from a theoretical option into a practical one. Every one of those consequences threatens the social conditions that make the current governance structure stable.
The absence of a spec is not an oversight. **It is the most important structural element of the implementation monopoly**, and it is self-perpetuating. Any alternative serious enough to run on mainnet stays close to Core's codebase and inherits Core's governance vulnerabilities. The monopoly reproduces itself through the same mechanism that makes breaking it appear to require the monopoly's cooperation.
A social environment shaped to treat the spec as perpetually not-quite-the-right-time does not need to issue that judgment explicitly. It just needs to make other work feel more urgent, more legitimate, more fundable. Over seventeen years, that is exactly what happened. The absence has a beneficiary, and the beneficiary is the existing structure.
---
## VII. Controlled Opposition and the Chain Fork Trap
The blocksize war showed how this routing works in practice. The critics who came closest to identifying Bitcoin's actual governance problem were channeled toward a solution that left the underlying structure intact.
Bitcoin Cash is the clearest example. The critique of Core's implementation monopoly was real. The solution, forking the chain, moved the same governance vulnerabilities to different maintainers operating the same monolithic architecture with the same informal merge authority and the same capture vectors. **The problem was never which people held the throne. The problem was the existence of a single throne.** Forking the chain built a second throne and called it revolution.
The structural consequence was that the critique became about block size rather than the governance layer that made block size a battleground in the first place. Bitcoin's capture vector survived intact because the most energetic opposition directed its energy at the consensus rules rather than the development infrastructure.
This pattern is not unique to Bitcoin. Institutional capture reliably produces critics who identify the right problem and get routed toward solutions that exhaust their energy without threatening the structure. The routing does not require conscious direction. It emerges from a social environment where the chain fork is fundable, narratable, and executable, while genuine governance reform requires building infrastructure that the existing social graph treats as unnecessary or dangerous. The path of least resistance runs away from the structural fix.
---
## VIII. The Permissionless Mythology as Defense System
The most durable form of capture is one that does not need to be maintained because its subjects maintain it for themselves. The conflation of network permissionlessness with development permissionlessness functions as exactly that kind of self-sustaining immune system.
People who hold this belief sincerely (who are not assets of any operation and have no financial stake in Core's monopoly) repeat it in every governance debate. They do so because they believe it is true, because it follows logically from premises they have accepted, and because the social environment of Bitcoin discourse has consistently rewarded it and punished the alternative.
The mythology does suppression work without requiring anyone to coordinate the suppression. Every time someone raises the governance critique and gets back "anyone can fork it" from a dozen independent voices, the effect is identical to coordinated dismissal even if every one of those voices is acting in complete good faith. The social proof looks organic because it is organic. The ideology has been successfully installed at the level of common sense.
This is why personnel changes at Core do not resolve the governance problem. The problem is not that the current maintainers hold wrong beliefs. The problem is that the social environment reproduces those beliefs regardless of who occupies the relevant positions, because the beliefs are structurally advantageous to the existing funding and credentialing apparatus and because that apparatus shapes what new entrants to the community learn to treat as obvious.
An ideology that makes structural critique feel like confusion rather than insight is more robust than one that makes it feel like heresy. Heresy can be argued with. Confusion just needs to be cleared up, and the people best positioned to clear it up are the ones whose authority the ideology protects.
The same dynamic shows up when critics demand a softer Bitcoin culture. Asking the network to drop its adversarial register before the structural conditions change is another version of asking the immune system to stand down while the infection remains. For the case that the adversarial default is calibrated to the threat environment rather than a personality disorder, see *[The Adversarial Default](/articles/the-adversarial-default)*.
---
## IX. Structural Capture Does Not Require Bad Actors
The argument in this document does not depend on the existence of bad actors and would be weakened by insisting on them.
Acculturated judgment, funding dependency, and shaped incentive environments produce the same outputs as deliberate coordination. A developer who has spent years inside a funding and social structure that treats implementation diversity as dangerous does not need to be consciously protecting that structure to reliably produce arguments that protect it. The acculturation did the work. The judgment is genuine. The output serves the same function as if the judgment had been purchased.
This is the serious version of the governance critique and it is more serious than the conspiracy version for a specific reason. **Conspiracies can be disrupted by exposing the coordination. Structural capture cannot be disrupted by exposing anything**, because there is no coordination to expose. The people involved are largely acting in good faith according to values they genuinely hold. Replacing them with different people who enter the same structural environment will produce the same outputs through the same mechanisms. **The capture is in the structure, not the personnel.** The fix has to be structural.
This is also why the "show me the smoking gun" dismissal fails as a counter-argument. The absence of documented coordination is not evidence that the structure is healthy. It is evidence that the structure is working as designed, because structures that produce capture through incentives rather than instructions do not leave smoking guns. They leave funding maps, personnel histories, and seventeen years of a formal specification that never got written.
---
## X. What Proof Requires and What It Implies
If the no-spec moat made genuine alternatives structurally impossible for seventeen years, the empirical answer is building one from a formal specification and checking consensus compatibility through differential testing against chain history. That is not a theoretical proposal. The test is underway.
The Bitcoin Commons project is a from-scratch Rust client built from the Orange Paper, a human-readable mathematical specification of Bitcoin's consensus rules. Same chain, same 21 million, not a new coin. Full-chain differential replay against Bitcoin Core is the scale test. `blvm-bench` targets on the order of 900,000 blocks. Those runs are operator-driven and resource-heavy. That is not a claim every CI job has zero-divergence proof to tip. Methodology lives in the [differential testing guide](https://docs.thebitcoincommons.org/development/differential-testing.html). The BLVM Specification Lock uses Z3 to check annotated implementation paths against the spec. Cryptographic merge authorization is designed and stays off until security review, key management, and community validation. This is what it looks like to break the no-spec moat rather than argue about it.
If the permissionless mythology were correct, this work would have been unnecessary because alternatives would have been easy to build and numerous. If the no-spec moat were an oversight rather than a structural feature, the response to this work would be welcome rather than hostile. The structural predictions the governance critique makes are testable, and the test is underway.
Implementation diversity with a written specification is not an attack on Bitcoin. **It is the completion of what Bitcoin's design actually requires.** A network that runs one implementation governed by a capturable social layer is not decentralized where decentralization matters.
The consensus rules are sound. The development infrastructure built around them is fragile in ways that the cryptography cannot fix, because **the fragility is social rather than mathematical.** Social enforcement stays durable when rules are visible, decisions are accountable, and alternatives can be built without the incumbent. It should not depend on the continued good behavior of a small number of institutions whose interests do not always align with the network's.
**Bitcoin survived because it redistributed trust more robustly than anything that came before it.** The next step is applying the same logic to the layer that maintains it.
---
*Evidentiary basis: [Bitcoin Governance Research](https://github.com/secsovereign/bitcoin-governance-research); companion articles [Who Controls Bitcoin](/articles/bitcoin-governance), [The Vertical Layer Problem](/articles/the-vertical-layer-problem), [Argument Map](/articles/bitcoin-governance-argument-map), [Governance Paralysis Was The Victory](/articles/governance-paralysis-was-the-victory), [The Adversarial Default](/articles/the-adversarial-default), [The Coordination Gap](/articles/bitcoins-hidden-crisis), and [The Last Uncaptured Asset](/articles/the-last-uncaptured-asset).*
---
# Governance Paralysis Was The Victory
## Bitcoin is not captured. The implementation that writes the defaults is capturable.
## Contents
- [The Block Size War](#the-block-size-war)
- [CVE-2018-17144: The Bug That Proved Gavin Right](#cve-2018-17144-the-bug-that-proved-gavin-right)
- [Who paid the seats](#who-paid-the-seats)
- [The PTSD: Good Ossification vs. Bad Ossification](#the-ptsd-good-ossification-vs-bad-ossification)
- [Lightning: A Partial Answer That Proves the Problem](#lightning-a-partial-answer-that-proves-the-problem)
- [The Market Bitcoin Should Own](#the-market-bitcoin-should-own)
- [The Path: Implementation Diversity in 2026](#the-path-implementation-diversity-in-2026)
- [The Only Move Left](#the-only-move-left)
- [Sources](#sources)
---
Bitcoin is not captured. The implementation that writes the defaults is capturable.
Those are not the same thing. Bitcoin is a network, a set of consensus rules, and a fixed supply of 21 million coins secured by proof of work. Bitcoin Core is one software implementation, the only one anyone runs in meaningful volume, that enforces those rules. **Bitcoin Core's merge process is informal, but Bitcoin's properties are not broken.**
The problem is not Bitcoin. The problem is that Bitcoin runs on one dominant implementation, written by a small merge roster, and that single point of failure is capturable. The solution is not to leave Bitcoin. **The solution is to build a second implementation** that runs on Bitcoin's network, enforces Bitcoin's consensus rules, and can be checked against a written specification. Same chain, same 21 million. That is what implementation diversity on Bitcoin actually means. Everything else is abandoning the only asset that actually works. For the funding map, merge concentration, and adversarial cases, see *[Who Controls Bitcoin](/articles/bitcoin-governance)*. For why the block size war consumed the bandwidth that diversity required, see *[The Social Layer Is the Attack Surface, §V](/articles/bitcoin-social-capture#v-the-blocksize-war-as-case-study)*. For the stalled-proposals evidence list and common monopoly defenses, see *[What Bitcoin's Stalled Proposals Tell You](/articles/what-bitcoins-stalled-proposals-tell-you)* and *[Bitcoin Core: The Biggest Fallacies](/articles/bitcoin-core-the-biggest-fallacies)*.
---
## The Block Size War
In the early days of Bitcoin, Gavin Andresen, Satoshi’s handpicked successor, called for multiple independent implementations of the Bitcoin protocol. The reasoning was straightforward: if one implementation has a consensus bug, others catch it, so you don’t run a monetary network on a single codebase. Andresen set a threshold for when this work should be done, but that threshold was never met. The conversation moved on, and Bitcoin remained a single-implementation network, every node running variations of the same code and all sharing the same blind spots.
At the time Bitcoin was a $6 billion asset and the engineering problem was solvable. The conversation moved on, and Bitcoin remained a single-implementation network.
In 2015, the block size debate consumed Bitcoin’s governance. On one side, increase block size to allow more transactions per block, enabling Bitcoin to scale as a payment network. On the other, keep blocks small to preserve decentralization, the property that actually makes Bitcoin valuable. This framing made it feel like a technical disagreement, but it wasn't. **It was a resource war.**
Exchanges needed throughput because every transaction on Bitcoin’s network drove trading volume and trading volume drove revenue. Brian Armstrong, co-founder and CEO of Coinbase, was one of the most vocal advocates for block size increases. He publicly experimented with BitcoinXT and framed scaling as an election: “What’s happening right now is an election in the bitcoin space.” He pushed Coinbase to actively support scaling proposals behind the scenes. Armstrong’s position didn’t prevail and the early idealists held, but the damage wasn’t in losing the block size argument. The damage was in what the argument consumed.
It is worth acknowledging that the small-block position was not purely defensive. Greg Maxwell and others argued, correctly, that keeping blocks small preserved the decentralization that made Bitcoin’s security model work. Full nodes are the backbone of Bitcoin’s trustless verification, and every kilobyte added to block size raises the hardware and bandwidth requirements to run one. If running a node becomes expensive, verification concentrates in the hands of exchanges and institutions, the exact entities whose interests don’t align with Bitcoin’s original design. The small-block position protected something real. **The problem was not that it won. The problem was that the war to win it consumed everything else.**
Bitcoin Cash forked off in 2017, but it wasn’t a solution. Bitcoin Cash left Bitcoin’s network, left Bitcoin’s hash power, left Bitcoin’s adoption, and carried the exact same single-implementation structure into a smaller, less secure chain. Its block size increase didn’t fix governance. It just moved the same problem to a network that fewer people use and fewer miners secure.
---
## CVE-2018-17144: The Bug That Proved Gavin Right
On September 17, 2018, a developer known as Awemany responsibly disclosed a vulnerability to Bitcoin Core developers. It was initially presented as a denial-of-service bug, but within hours, Bitcoin Core contributor Matt Corallo determined it was also an inflation vulnerability. A miner could create Bitcoin out of thin air by spending the same inputs multiple times within a single transaction.
The bug was introduced in Bitcoin Core 0.14.0 in March 2017 and had been present in the codebase for over a year and a half before anyone found it. It was created by an optimization that removed a costly duplicate-input check during block validation. The duplicate-input path was never mined. Replaying the live chain would have matched Core. The find was in the source. A second client would have seen it on a crafted transaction, not on those blocks.
Bitcoin Core developers chose to initially patch and release only the denial-of-service fix, deliberately withholding full disclosure of the inflation vulnerability to encourage upgrades before the attack surface was public knowledge. Eight months after the patch, more than half of Bitcoin’s full nodes were still running vulnerable software. Luke Dashjr, Bitcoin Core developer, stated plainly: “The inflation bug is in practice a network-wide risk. It would allow a 51% miner attack to cause inflation, something such attacks can’t normally do.”
**The bug was in Bitcoin Core, not in Bitcoin**, and Bitcoin Core's monopoly is what made the bug potentially catastrophic for Bitcoin.
---
## Who paid the seats
The block size war coincided with a period when Bitcoin’s core development was funded through MIT’s Digital Currency Initiative. On April 25, 2015, MIT Media Lab Director Joichi Ito emailed Jeffrey Epstein a primary source document later released by the House Oversight Committee. Ito forwarded his own internal message describing what had just happened:
“The way that Bitcoin is organized currently is that there are five core developers and around a hundred contributors to the core code. The five core developers are like Linus Torvalds of Linux. They decide what changes are made to the core code.”
“Gavin, Wladimir and Cory were being paid out of a non-profit organization called the Bitcoin Foundation. A few weeks ago, it blew up when one of the board members declared the foundation bankrupt. Many organizations scrambled to step into the vacuum created by the foundation and take control of the developers. We moved quickly talking to all of the various stakeholders and the three developers decided to join the Media Lab. This is a big win for us.”
Then Ito’s note directly to Epstein: “Used gift funds to underwrite this which allowed us to move quickly and win this round. Thanks.”
The language in Ito's email is not charity. "Take control." "Win this round." He is reporting that he has placed Bitcoin Core development inside an institution during the foundation's collapse.
Epstein’s reply was “gavin is clever.” Between 2002 and 2017, Epstein donated $850,000 to MIT. A portion of this funded the DCI, which employed Bitcoin Core’s lead maintainer Wladimir van der Laan, Cory Fields, and Gavin Andresen. These were the three most important developers working on the protocol during the block size war, and they had no knowledge of the funding source. MIT deliberately concealed it, marking donations as anonymous to bypass vetting.
In July 2014, Peter Thiel emailed Epstein asking: “Do you think this is the first step in upping the anti-BTC pressure?” Epstein’s reply mapped Bitcoin’s internal contradictions, store of value versus currency versus property versus payment system, and the tension between anonymity and a transparent ledger. By October 2016, in the middle of the war, Epstein was emailing associates that he had “spoken to some of the founders of bitcoin who are very excited.” He met with Brock Pierce and Larry Summers to discuss Bitcoin before it became mainstream.
Those are documented financial relationships, not a claim that the developers in the seats were conspirators. The war still consumed the bandwidth Gavin had said a second independently specified client required.
---
## The PTSD: Good Ossification vs. Bad Ossification
The block size war ended and Bitcoin Cash forked off. The community “won” in the sense that block size didn’t increase, but the war left a scar on how Bitcoin Core handles any change at all.
Bitcoin Core developers argue this conservatism is deliberate and necessary. The consequences of a consensus bug in a trillion-dollar asset are devastating, and extreme caution on consensus rule changes is correct. But none of the blocked improvements touch consensus rules. Separating wallet functionality from node functionality has been a recognized improvement for over twelve years. It would allow Bitcoin to be used by a wider range of software without requiring full node operation. The multiprocess capnp objection on PR [#10102](https://github.com/bitcoin/bitcoin/pull/10102) is a sovereignty complaint about an outside-library approach, not a technical case against `-disablewallet`. It hasn’t happened because the informal merge process can no longer distinguish between “don’t change the consensus rules” and “don’t change anything.”
The result is that good ossification, the properties that should never change like the 21 million cap and proof of work, looks the same as bad ossification, the improvements that everyone agrees on but that can’t get through. And while Bitcoin Core sits frozen on the changes it should be making, it is accumulating technical debt. Every improvement that can’t get merged forces workarounds, workarounds breed complexity, and complexity breeds bugs. The codebase gets worse over time precisely because the process that is supposed to protect it can no longer process anything at all.
Bitcoin the network is fine. **Bitcoin Core the implementation is locked, and it is rotting from the inside.**
---
## Lightning: A Partial Answer That Proves the Problem
The Lightning Network is the most successful scaling solution Bitcoin has produced. By early 2026 it processes millions of transactions with sub-second settlement and near-zero fees. Major exchanges have integrated it, and wallets like Strike and Phoenix have made it genuinely usable for everyday payments at small values. Lightning is real and works within its design constraints, which does not answer this essay’s thesis.
Lightning solves throughput for micropayments, but it does not solve the bigger jobs stablecoins are capturing: large-value cross-border transfers, corporate treasury management, remittance corridors. These require on-chain finality that Lightning cannot provide. More importantly, Lightning does not address the governance problem at all. It is a layer built on top of a frozen base layer. If Bitcoin Core cannot implement UTXO set commitments, wallet-node separation, or formal verification, none of which touch consensus rules, then Lightning inherits those limitations. A second layer on a frozen first layer is still a frozen system.
---
## The Market Bitcoin Should Own
Bitcoin educated hundreds of millions of people on what money could be. Then it didn’t do much with that knowledge.
Stablecoins are filling the gap. As of February 2026, the total stablecoin market cap sits at $312 billion, up from $205 billion at the start of 2025, a 49% increase in twelve months. USDT dominates at roughly 60% market share, and total on-chain stablecoin transaction volume hit $33 trillion in 2025, a headline often compared to Visa’s annual payment volume. Raw on-chain volume includes exchange internals, MEV, and bot churn. Visa’s figure is settled consumer payments. The comparison is not like for like. The payment use cases still moved.
Every dollar moving through a stablecoin is a dollar moving through a system with a central issuer, a kill switch, and blacklist capability. Tether can freeze funds and Circle can comply with government seizure orders. These are the exact properties Bitcoin was designed to eliminate, and yet the use cases Bitcoin was designed to own, payments, remittances, and cross-border settlement, are being captured by systems that have them. Not because of technical impossibility, since the throughput problem is solvable and Lightning proves it at small scale, but because governance paralysis prevents the base-layer changes needed to compete at scale.
Meanwhile, 137 countries representing 98% of global GDP are exploring CBDCs. China’s e-CNY is the most advanced, having processed 3.48 billion cumulative transactions worth 16.7 trillion yuan by November 2025, with 230 million verified wallets. On January 1, 2026, China made the e-CNY interest-bearing, the first CBDC in the world to do so. Wallet balances now accrue interest, receive deposit insurance, and are treated as commercial bank liabilities. The e-CNY just moved from a pilot to a core financial instrument, and adoption is accelerating.
The GENIUS Act, signed in 2025, established the first federal regulatory framework for stablecoins in the US. Stablecoin issuers received provisional banking charters, and PayPal, Stripe, and Circle are integrating stablecoin rails into mainstream financial infrastructure. The regulatory environment is being built specifically for centralized digital money. Bitcoin, the asset that should have been the decentralized alternative to all of this, can’t participate because Bitcoin Core can’t adapt.
The answer is not a new chain. Ethereum runs multiple client implementations, including Geth, Nethermind, Lighthouse, and Teku, and this has genuinely improved its resilience. But Ethereum is not Bitcoin. It does not have Bitcoin’s security model, Bitcoin’s fixed supply, Bitcoin’s credibility, or Bitcoin’s role as digital money. Multi-client architecture works. It just needs to happen on Bitcoin.
---
## The Path: Implementation Diversity in 2026
The call for implementation diversity is not new and not theoretical. The movement already exists, incompletely and with significant obstacles.
Bitcoin Knots, then maintained by Luke Dashjr, was the most visible example, a Bitcoin Core derivative with stricter transaction relay policies, filtering what it considers spam transactions including Ordinals and Runes data. In January 2024, Knots ran on fewer than 70 nodes, but by September 14, 2025 it had peaked at 25.45% of reachable nodes according to [Coin Dance](https://coin.dance/), staying above 19% through that stretch, driven by backlash to Bitcoin Core’s planned removal of OP_RETURN data limits in version 30. That was the largest shift in Bitcoin node software outside of a hard fork event, and no chain split occurred. Core and Knots enforced identical consensus rules and diverged only on relay policy. That is how a policy exit on Bitcoin is supposed to work.
Luke's Knots later followed a BLAKE2b proof-of-work hard fork and left Bitcoin. The Core-derived forks that stayed on Bitcoin are still that Core lineage. They are still policy forks, not an architectural alternative. They share Core’s codebase, Core’s architectural assumptions, and by extension Core’s structural limitations.
btcd, written in Go, has been in production since 2013 and deliberately separates wallet functionality from the node. That is the exact architectural improvement Bitcoin Core has failed to implement for twelve years. But btcd has a problem that undermines its entire value proposition: it keeps getting the consensus rules wrong. In 2022, a developer intentionally crafted transactions that stalled btcd nodes twice in one month, first by exploiting a witness size parsing failure, then by triggering a script size limit that btcd still enforced after Taproot removed it. In 2024, two more consensus bugs were disclosed: a misimplementation of BIP 68 and BIP 112, and a FindAndDelete bug in legacy signature verification. Each one meant btcd would have accepted or rejected blocks differently from Core. The whole point of a second implementation is to catch exactly these divergences. btcd keeps being the thing that diverges.
libbitcoin, written in C++ and created by Amir Taaki, is now maintained by Eric Voskuil. It implements Bitcoin’s protocol from scratch rather than forking Core, which is architecturally ambitious. But it abandons the UTXO model entirely. There is no UTXO set and no mempool. It stores transactions, headers, and a relationship table linking the two. To check whether an input has been spent, it looks up whether a spending transaction exists, the inverse of Core’s approach, which maintains a live index of what is unspent. Every wallet, exchange, block explorer, and Lightning node in the Bitcoin ecosystem is built to query a UTXO set and Libbitcoin does not have one. It is a crystal castle, architecturally interesting, but the ecosystem cannot plug into it without being rebuilt almost entirely.
Bcoin, written in JavaScript and created by Christopher Jeffery, was built as backend infrastructure for Purse.io. Purse.io shut down in 2020. Bcoin has no known production deployment since then and commit activity has gone sparse. It is effectively orphaned.
A Core-derived fork is a derivative. btcd diverges. libbitcoin is incompatible. Bcoin is dead. Each fails for a different reason, but the failure is the same: none of them can prove they enforce the same consensus rules as every block Bitcoin has ever produced. Without that proof, a second implementation is just another codebase asking the network to trust it.
Bitcoin Commons is one public attempt to build that proof on the same chain, a from-scratch Rust client built from the Orange Paper, a human-readable mathematical specification of Bitcoin's consensus rules. Full-chain differential replay against Core is the scale test. `blvm-bench` targets on the order of 900,000 blocks. Those runs are operator-driven and resource-heavy. That is not a claim every CI job has zero-divergence proof to tip, so Commons has not yet passed the bar in the paragraph above. Methodology lives in the [differential testing guide](https://docs.thebitcoincommons.org/development/differential-testing.html). Cryptographic merge authorization is designed and stays off until security review, key management, and community validation. No previous alternative shipped that mix of a readable spec, a Specification Lock, and a full-chain differential program.
The 2025 OP_RETURN controversy proved something important: that migration is latent demand, not apathy. The Bitcoin community will move when Core’s direction conflicts with its values. It just needs somewhere worthy to move to.
---
## The Only Move Left
Most people on both sides of the block size war believed what they were arguing. But the people who stood to benefit from Bitcoin's inability to adapt didn't need the argument to go their way. **They just needed it to consume enough time and energy to break coordination, and it did. Paralysis was the victory condition, and it was met.**
But paralysis is not permanent because it is a governance failure, not a protocol failure. Bitcoin’s consensus rules are sound, its fixed supply can’t be changed, and its proof-of-work security is unmatched. What Bitcoin lacks is a second implementation, written in different code, that can be checked against a specification rather than reverse-engineered from Core.
Bitcoin Core’s monopoly is not a law of nature but a historical accident, sustained by governance trauma and the absence of a viable alternative, and that alternative is now buildable. The tools exist, the community has demonstrated it will migrate, and the only question is whether someone builds the thing that Gavin called for fifteen years ago and proves it works before the window closes.
Stay on Bitcoin. Make the implementation layer cheaper to leave.
For why the adversarial culture that followed that trauma is still doing work, see *[The Adversarial Default](/articles/the-adversarial-default)*. For what has to happen next, in what order, see *[Making Core Irrelevant](/articles/making-core-irrelevant)*.
---
## Sources
- [Epstein files, DOJ document releases](https://www.justice.gov/epstein): July 20–21, 2014 Epstein to Peter Thiel correspondence; October 13, 2016 Epstein to Alsabbagh/Alahmadi; Epstein-Pierce-Summers meeting (December 2025 release)
- [Brian Armstrong, "Scaling Bitcoin: The Great Block Size Debate," Coinbase Blog](https://www.coinbase.com/blog/scaling-bitcoin-the-great-block-size-debate), May 2016
- [House Oversight Committee documents](https://oversight.house.gov/): Epstein to MIT/DCI/Core developer funding chain; Joi Ito email to Epstein, April 25, 2015 (November 2025 release)
- [Bitcoin Core notice, CVE-2018-17144](https://bitcoincore.org/en/2018/09/20/notice/), September 20, 2018
- [Luke Dashjr inflation bug quote](https://cointelegraph.com/news/bitcoin-developer-luke-jr-says-inflation-bug-was-worse-than-reported), Cointelegraph, May 2019
- [DefiLlama stablecoin market cap](https://defillama.com/stablecoins): live data, February 2026
- [CoinGecko](https://www.coingecko.com/): stablecoin market cap cross-check (~$314B same date)
- [DeFi Llama / Yahoo Finance year-end report](https://finance.yahoo.com/): stablecoin growth $205B to $312B, December 30, 2025
- [Bloomberg / Artemis Analytics; a16z State of Crypto 2025](https://a16zcrypto.com/posts/article/state-of-crypto-report-2025/): stablecoin transaction volume ~$33T
- [Yahoo Finance](https://finance.yahoo.com/): GENIUS Act / stablecoin banking charters, December 30, 2025
- [Atlantic Council CBDC Tracker](https://www.atlanticcouncil.org/cbdctracker/): 137 countries / 98% GDP, July 2025
- [People's Bank of China via gov.cn](https://www.gov.cn/); [BeInCrypto](https://beincrypto.com/): e-CNY transactions, wallets, interest-bearing framework, December 29, 2025
- [Bitbo](https://bitbo.io/); [BitcoinNews.com](https://bitcoinnews.com/); [Bitfinex blog](https://blog.bitfinex.com/): Bitcoin Knots surge, September 2025
- [Coin Dance](https://coin.dance/): Knots peak 25.45% of reachable nodes, September 14, 2025; trajectory 69 to 4,713 nodes
- [Yellow.com research](https://yellow.com/); [CryptoSlate, August 31, 2025](https://cryptoslate.com/): Bitcoin Core v30 / OP_RETURN
- [btcsuite/btcd on GitHub](https://github.com/btcsuite/btcd)
---
# Bitcoin Core: The Biggest Fallacies
## Inspired by [Jude Nelson's 2014 analysis of systemd](http://judecnelson.blogspot.com/2014/09/systemd-biggest-fallacies.html)
## Contents
- [Fallacy 1: Contributor count](#fallacy-1-bitcoin-core-has-hundreds-of-contributors-therefore-it-is-not-controlled-by-a-small-group)
- [Fallacy 2: Adoption proves merit](#fallacy-2-widespread-adoption-proves-technical-merit)
- [Fallacy 3: Critics dislike change](#fallacy-3-critics-of-bitcoin-core-just-dont-like-change)
- [Fallacy 4: Not monolithic](#fallacy-4-bitcoin-core-is-not-monolithic)
- [Fallacy 5: Rough consensus](#fallacy-5-rough-consensus-governs-bitcoin-core-decisions)
- [Fallacy 6: Technical merits alone](#fallacy-6-you-should-judge-bitcoin-core-on-technical-merits-alone)
- [Fallacy 7: Conservative by design](#fallacy-7-bitcoin-core-is-conservative-by-design-and-thats-a-feature)
- [Fallacy 8: Reviewer resources](#fallacy-8-spreading-reviewer-resources-across-multiple-implementations-weakens-bitcoin)
- [Conclusion](#conclusion)
---
There is a set of arguments that appears repeatedly in defense of Bitcoin Core's implementation monopoly. This post is meant to serve as a repository of those arguments and to explain why they are logically invalid. I will direct people here when they appear.
Core's engineering record is not the dispute. Review culture, release engineering, and reluctance to rush consensus changes are why the money rules have held. The question of whether Bitcoin Core is the right client for a given operator is separate from whether these eight defenses of the implementation monopoly survive scrutiny. The governance critique here is also separable from any opinion about Bitcoin's consensus rules. **This is not an argument that Bitcoin is broken.** For the numbered argument map, see *[Bitcoin Governance: Argument Map](/articles/bitcoin-governance-argument-map)*. For narrative evidence and funding maps, see *[Who Controls Bitcoin](/articles/bitcoin-governance)*.
---
### Fallacy 1: "Bitcoin Core has hundreds of contributors, therefore it is not controlled by a small group"
This is a non sequitur. **Contributor count and merge authority are independent measurements**, and conflating them is either naive or deliberate misdirection. Hundreds of people have opened pull requests. A handful of accounts land them.
Analysis of 25,122 pull requests, 430,613 IRC messages, and 17 years of data tells the merge-authority story. The top three merger accounts control 81.1% of all-time historical merges, with Wladimir J. van der Laan at 34.8%, Michael Ford at 25.8%, and Marco Falke at 20.5%. In the 2022+ window (5,747 merged PRs) the top merger takes 50.2%, the top two take 70.4%, and the top three take 82.2%. Those windows are not interchangeable with Brink's 56% for calendar year 2025. The authorship Gini is 0.851 historical / 0.834 recent. Power is not distributing over time. Top-10 authorship increased from 42.7% to 47.8%. Of 7,827 contributors across the project's history, 90.7% have exited with no activity in the past year of the dump. Named merger counts, author funnels, and release-signing shares live in *[Who Controls Bitcoin, §II](/articles/bitcoin-governance#ii-the-merge-authority-structure)*. The contributor count is not the governance count, and one does not imply the other.
### Fallacy 1.1: "The process has improved, therefore the structural problem is being addressed"
Process improvements are real. Zero-review merges dropped from 30.3% to 3.3%. First-review clocks are nearly equal (12.3 hours for maintainers, 12.4 for everyone else). These are genuine workflow gains. The self-merge rate, however, is **25.5%** of 9,793 maintainer-authored merges (95% CI 24.7–26.4). Raw maintainer versus non-maintainer merge rates of about 80% against 55% overstate the gap, because most of it is self-merge privilege. Peer-merge rates, excluding self-merges, are about 59% against 54% all-time, widening to about 63% against 51% since 2022. The review weight bias between maintainers and non-maintainers has held at 5.5 to 1. Top-10 authorship increased. The authorship Gini is essentially unchanged. Non-maintainers wait 1.41× longer to merge. The oligarchy got more efficient at processing pull requests and the concentration of authority did not move. **Those are two different things.**
### Fallacy 1.2: "Maintainers are just janitors, not decision-makers"
This framing appeared in mainstream Bitcoin commentary as early as 2018 and has been repeated since. The data does not support it. Maintainers self-merge **25.5%** of their own pull requests, and **45.1%** of those self-merges carry zero reviews (**11.6%** of all maintainer-merged PRs). One historical maintainer self-merged 77.1% of his own pull requests. Five maintainers with over 1,200 merges between them have never self-merged. The "it is ordinary workflow" defense has to explain why most maintainers decline. Merge authority over the lineage that almost all economic nodes run **is not a janitorial function** by any honest definition of the term.
---
### Fallacy 2: "Widespread adoption proves technical merit"
This is a self-serving bias. It assumes that the mechanism of adoption was active preference rather than the absence of alternatives, and that assumption does not hold up.
Other clients exist. A Core-derived fork that stays on Bitcoin is still a Core fork. Btcd abandoned active development and is not positioned to confront Bitcoin Core. Libbitcoin abandoned the UTXO set and mempool, requiring ecosystem retooling and accepting isolation. Running Bitcoin Core is not a positive selection on merit but the predictable outcome of path dependency, exchange requirements, and wallet vendor defaults. Adoption through switching cost is not adoption through technical merit, and treating it as such is begging the question.
### Fallacy 2.1: "Alternative implementations exist, therefore there is no monopoly"
The existence of alternatives on paper is not the same as viable alternatives in practice. Forking Bitcoin Core inherits that 151,004-line implementation, 17 years of accumulated patches, and the same capturable-architecture vectors under new management. Without a formal specification floating above the implementation, any alternative must reverse-engineer undocumented behavior from the reference client itself, which makes the reference client the de facto specification by default. The lack of a specification protects the incumbent by making independent implementation structurally more expensive than it would otherwise need to be. To date, no alternative implementation has successfully replicated Bitcoin Core's consensus implementation entirely unless it is directly forked from Bitcoin Core.
---
### Fallacy 3: "Critics of Bitcoin Core just don't like change"
This is an ad hominem that routes around the substantive argument by attacking the character or motivation of the critic rather than the content of the criticism.
Jon Atack has been a Bitcoin Core contributor since 2019, a BIP editor, and a developer. In March 2026, he stated on record that maintainer selection involved favoritism and double standards, that preferred successors were picked and groomed explicitly, and that the record would speak for itself when laid out. He stated directly that the ship has sailed for someone like him to make change from within Core because the entrenched are entrenched. These are the words of a longtime insider with no competing implementation to promote, not the words of someone who dislikes change.
Beyond Atack, 31 Bitcoin Core developers signed an open letter against the OP_RETURN change and were overridden. Developers were banned from GitHub for raising a documented conflict of interest involving a contributor with a direct financial stake in the outcome. Luke Dashjr was removed from the Bitcoin Core security list after a decade of contribution with no documented process and no appeal. The pattern is insiders with documented grievances, not outsiders resistant to progress.
---
### Fallacy 4: "Bitcoin Core is not monolithic"
Bitcoin Core's first-party implementation, Bitcoin Core 32.1 at commit `f0de87f`, is 151,004 code lines. Seven percent of those lines are the consensus rules. The wallet, the GUI, networking, and RPC are the rest of the same program. The count is *[The Rules Are 7% of the Program](/articles/the-rules-are-7-percent)*. Those pieces are entangled rather than independently composable. The fact that it has internal modules does not make it non-monolithic any more than the Linux kernel's loadable modules make it non-monolithic. Modularity and monolithism are independent properties and a codebase can be both simultaneously.
The deeper issue is that no formal specification exists above what Bitcoin Core ships. When almost all nodes run that lineage, the reference client and the protocol become functionally identical regardless of what anyone claims about their separability. The absence of a specification is not a neutral technical choice. It protects the incumbent by ensuring that any alternative implementation must reverse-engineer undocumented behavior rather than implement against an independent mathematical standard.
---
### Fallacy 5: "Rough consensus governs Bitcoin Core decisions"
Rough consensus is defined and invoked by the same maintainers who close pull requests, which means there is no external arbiter, no defined threshold, and no appeal mechanism. The same CONTRIBUTING.md file says there is "no particular concept of 'Bitcoin Core developers' in the sense of privileged people," and then requires consensus changes to have "widely perceived technical consensus... based on the judgement of the maintainers." The first sentence is process culture. The second is who closes the question.
Jon Atack argued on PR [#26868](https://github.com/bitcoin/bitcoin/pull/26868) (2023-01-13) that outsiders overestimate maintainers as gatekeepers rather than as people implementing the rough consensus of reviewers, and undervalue the reviewers who shape it. Long-term reviewers do shape what gets attention. That does not make the closing mechanism an external process. If the people who define sufficient consensus are the same people who merge, invoking rough consensus as a legitimizing mechanism is circular.
The stronger evidence is who can close the file. Pair-level reviewer cohesion exists, but the joint-appearance counts are too small to treat as a voting machine. What is not small is merge share: one account lands 50.2% of 2022+ merges, three land 82.2%, and the implementation PR for package relay was titled `[NO MERGE]` until maintainers declared rough consensus on approach. The outcome is not emerging from an external process. The process is ratifying a judgment the merge key already holds.
---
### Fallacy 6: "You should judge Bitcoin Core on technical merits alone"
Judging software on technical merits alone requires a formal specification that defines precisely what the software does and does not do, and a formal proof that the implementation satisfies that specification. Bitcoin Core has neither. In the absence of both, developer trustworthiness, funding relationships, governance behavior, and conflicts of interest are not irrelevant considerations to be excluded from the analysis.
Their track record is not reassuring. A Bitcoin Core maintainer had their security compromised while holding merge access to infrastructure securing over $1 trillion in network value, and the community response was effectively silence. A wallet deletion bug shipped to production. The OP_RETURN change was merged over documented opposition that included a signed letter from 31 contributors, with at least one developer banned from the GitHub repository for pointing out that a contributor pushing the change was affiliated with a for-profit project that directly benefited from it. These are not external attacks on the project. They are governance failures that originated inside the structure itself. For the same reputation-over-verification pattern applied to hardware wallets, see *[Don't Trust, Verify](/articles/dont-trust-verify)*. For why irreversible stakes make a softer culture the wrong prescription while those failures continue, see *[The Adversarial Default](/articles/the-adversarial-default)*.
---
### Fallacy 7: "Bitcoin Core is conservative by design, and that's a feature"
The conservation of consensus rules is a genuine and important property of Bitcoin. What gets conflated with it, consistently and conveniently, is the conservation of the implementation itself. These are two distinct things and treating them as the same thing is either confused or dishonest.
Wallet and node separation has had universal agreement among contributors for approximately 12 years and has not shipped. UTXO commitments have been research-complete since 2014, would reduce the initial block download burden for new nodes by approximately 98%, and have not shipped. Every year that UTXO commitments do not ship, every new node operator pays the full cost of downloading 17+ years of chain history including all spam and bloat that UTXO commitments would have made irrelevant. That cost compounds with every passing year and every new participant: quantified in *[Full Cost of Running a Bitcoin Node](/articles/full-cost-of-running-a-bitcoin-node)*. The governance structure cannot distinguish between a proposal that is contested on the merits and a proposal that has unanimous agreement, and the practical result is that nothing ships either way. For the evidence dossier on stalled improvements, see *[What Bitcoin's Stalled Proposals Tell You](/articles/what-bitcoins-stalled-proposals-tell-you)*.
---
### Fallacy 8: "Spreading reviewer resources across multiple implementations weakens Bitcoin"
This argument assumes that the global pool of qualified reviewers is fixed and that diverting any portion of it to alternative implementations reduces the total security of the network. Atack addressed this directly in March 2026, describing it as a collectivist framing that treats the pie as a fixed size to be divided rather than something that can grow. His point was that developers who cannot be productive in Bitcoin Core's social environment for whatever reason, whether personal situation, work style, or geography, could contribute productively in a different organizational context. Welcoming them into alternative implementations grows the total reviewer pool rather than redistributing a fixed one.
Bitcoin Core's power nexus sits in approximately three or four locations across the US, UK, and a handful of European cities. The developer population capable of contributing to Bitcoin infrastructure is global, and the constraint on participation is not a shortage of qualified people but a set of structural and social barriers that the current governance model imposes and benefits from maintaining.
---
## Conclusion
This post will be updated as additional fallacies appear, and I will direct people here when these arguments come up in discussion.
Bitcoin was designed to eliminate the need for trusted intermediaries in money. **Its reference implementation is governed by a small, concentrated group of them.**
---
## Sources
- [Bitcoin Governance Research](https://github.com/secsovereign/bitcoin-governance-research): merge concentration, Gini, and process metrics cited in Fallacies 1–2 and 5 ([`findings/GOVERNANCE_FRAMES.md`](https://github.com/secsovereign/bitcoin-governance-research/blob/master/findings/GOVERNANCE_FRAMES.md), [`findings/ARCHIVE_GEMS.md`](https://github.com/secsovereign/bitcoin-governance-research/blob/master/findings/ARCHIVE_GEMS.md))
- [Jon Atack, Plan B Forum (Rumble)](https://rumble.com/v75tyny-bitcoin-code-governance-jon-atack-plan-forum.html): maintainer selection and governance dynamics
- [Jude C. Nelson, "Systemd: The Biggest Fallacies"](http://judecnelson.blogspot.com/2014/09/systemd-biggest-fallacies.html): template for this article's structure
---
# What Bitcoin's Stalled Proposals Tell You
## Why Bitcoin's most wanted improvements haven't shipped, and what it looks like when they do.
## Contents
- [The Governance Reality](#the-governance-reality)
- [Stalled Proposals](#stalled-proposals)
- [Policy Monoculture and Revealed Preference](#policy-monoculture-and-revealed-preference)
- [What Better Looks Like](#what-better-looks-like)
- [The Proof](#the-proof)
- [Sources](#sources)
---
Bitcoin's consensus rules are sound, covering a small, well-defined set of operations: signature validation, UTXO accounting, block structure, and script execution. **Bitcoin Core is not those rules.** In Bitcoin Core 32.1 it is a 151,004-line implementation that carries 10,122 lines of them. *[The Rules Are 7% of the Program](/articles/the-rules-are-7-percent)* is the count. The sacredness of the consensus layer does not extend to the monolith surrounding it, and **conflating the two is the primary mechanism by which the status quo defends itself.**
Bitcoin’s long-term value proposition depends on it being genuinely ungovernable by any single entity, whether a state, a corporation, or a development team. That property requires infrastructure diversity, meaning multiple independent implementations, multiple funding sources, and governance that no single party can capture. What exists today is the opposite: one implementation, a handful of maintainers, and funding concentrated in a small number of grant organizations. The infrastructure surrounding them is a single point of failure, and it has been producing the same failure mode for years.
Caution is appropriate for consensus changes. **It is not an explanation for why networking and privacy improvements with no consensus implications sit unmerged for years.** The features below are not controversial. They are not dangerous. They are research-complete improvements that a functional governance structure would have shipped. **The fact that they haven't shipped is the data.** For governance evidence behind the stall, see *[Who Controls Bitcoin](/articles/bitcoin-governance)*. For the blocksize-war paralysis narrative, see *[Governance Paralysis Was The Victory](/articles/governance-paralysis-was-the-victory)*. For numbered arguments and monopoly-defense refutations, see *[Bitcoin Governance: Argument Map](/articles/bitcoin-governance-argument-map)* and *[Bitcoin Core: The Biggest Fallacies](/articles/bitcoin-core-the-biggest-fallacies)*. For what consensus can close on blockspace, see *[The Achievable Floor](/articles/the-achievable-floor)* and the three-BIP stack ([Permanent Data Channel Closure](/bips/permanent-data-channel-closure), [Static Per-Output Miner Fee](/bips/static-per-output-miner-fee), [Dynamic Escalation](/bips/dynamic-escalation-per-output-fee)).
---
## The Governance Reality
When one implementation controls the defaults for the entire network, every improvement has to clear one gatekeeping process with a thin reviewer pool, a thin funding base, and institutional incentives that do not always align with node operators.
Across 17 years of Core commit history, the authorship Gini is ~0.851 historical / ~0.834 recent, where 0 is perfectly equal and 1 means one person controls everything. The top three merger accounts control 81.1% of all-time historical merges and 82.2% of merges since 2022. In calendar year 2025, over half of all merges flowed through one Brink-funded individual, a figure Brink itself published. Bitcoin Core has never had more than a handful of active maintainers in its entire history. That concentration is not a distribution that ships a long backlog of improvements. **It is a distribution that produces exactly the list below.**
---
## Stalled Proposals
Dandelion (2017): research-complete, never merged
UTXO Commitments (~2014): research-complete, never merged
Erlay (~2019): years of research, still in the queue
Formal Specification: never written down; Core’s behavior is the de facto spec
Wallet/Node Separation (2016): still bundled after a decade of universal agreement
Formal Verification: recommended by Quarkslab, not implemented
Package relay / BIP331: designed on the list as policy, not consensus; implementation PRs spent years under `[NO MERGE]`
and more…
## Privacy and Relay
Dandelion has been research-complete since 2017. The mechanism is a two-phase propagation model: transactions travel a random path through the network in the stem phase before diffusing outward, making it significantly harder for a passive observer to determine which node originated a transaction. It was never merged.
The close comment on the Core implementation PR ([#13947](https://github.com/bitcoin/bitcoin/pull/13947), opened 2018-08-12 by maflcko, closed unmerged 2019-07-11) is author-close, not an external veto. The author, a maintainer, cited RBF and CPFP interaction plus DoS vectors, and pointed at a thinner “Dandelion Light” first step. Thirty reviews, no NACKs in the review-state field. BIP 156 status is Closed.
The stated grounds do not hold. Stempool DoS is manageable with rate limiting and size constraints. The RBF and CPFP interaction was an engineering problem, not an impossibility. Monero has run Dandelion++ in production since 2020. The strongest honest objection was never DoS. It was propagation latency, one to one and a half minutes versus seconds, which the closure folded into the DoS framing rather than stating directly. That latency is load-bearing for the privacy guarantee, not a defect.
Tor became the ambient fallback without Core formally endorsing it or subjecting it to comparable scrutiny, despite documented DoS and Sybil exposure of its own. Seven years later nobody has picked Dandelion back up. That is a priority decision dressed as a technical one. See [`findings/ARCHIVE_GEMS.md`](https://github.com/secsovereign/bitcoin-governance-research/blob/master/findings/ARCHIVE_GEMS.md).
What eventually landed in Core was private broadcast, merged years after Dandelion was first proposed. Private broadcast protects your IP from the specific peer you connect to. That is a narrower threat model. Both are useful. They are not substitutes, and private broadcast landing does not close the Dandelion argument.
Erlay would cut node bandwidth on transaction relay using set reconciliation rather than flooding. Scaffolding shipped. `SENDTXRCNCL` and `TxReconciliationTracker` are in the tree. The full bandwidth protocol is **0 of 7** merged. BIP 330, assigned 2019-09-25, is still Draft. PR [#21515](https://github.com/bitcoin/bitcoin/pull/21515) opened 2021-03-23 and closed unmerged 2024-06-21. PR [#35591](https://github.com/bitcoin/bitcoin/pull/35591) opened 2026-06-23, still open, still tagged `[DO NOT MERGE]`. The author’s measurements on the full-protocol PR sit in the 20–50% range; a reviewer in the same thread disputed the efficiency on accepted transactions. There was no numeric gate that would have resolved it. “Bitcoin has Erlay” is wrong. “Core did nothing on BIP 330” is also wrong. The handshake merged. The bandwidth protocol did not, five years after the BIP. See [`findings/STALLED_PROPOSALS_REPORT.md`](https://github.com/secsovereign/bitcoin-governance-research/blob/master/findings/STALLED_PROPOSALS_REPORT.md).
Package relay was announced on bitcoin-dev as mempool policy, “not consensus or P2P protocol changes.” The large implementation PR is titled `[NO MERGE]` until maintainers have rough consensus on approach ([#27742](https://github.com/bitcoin/bitcoin/pull/27742)). That is the 2022+ informal-before-PR flow of 0.002 in prose. The list still names the topic. GitHub refuses to treat the first large PR as a decision.
## Sync and Verification
UTXO commitments date to at least 2014. The idea is to commit the current state of all unspent outputs in a form a new node can verify against the proof-of-work chain, rather than replaying over a decade of transaction history from genesis. Initial block download currently takes days to weeks. A working commitment scheme could cut that to hours or less while keeping the trust anchor in the chain itself. Keyword PR counts on this topic are too noisy to use. What shipped is AssumeUTXO. James O'Beirne proposed it on bitcoin-dev on 2019-04-02 as an optimization in the spirit of assumevalid, with a snapshot hash hardcoded in the software. That is a weaker trust model than a verifiable commitment. What that unrecovered IBD burden costs operators is modeled in *[Full Cost of Running a Bitcoin Node](/articles/full-cost-of-running-a-bitcoin-node)*.
Formal Verification. The Quarkslab audit, the first external professional security audit in Core’s history, was scoped primarily to the P2P networking layer over 100 man-days. Quarkslab states directly that existing harnesses “do not fully exercise the complete range of consensus checks” and that “most existing harnesses target narrow, well-scoped portions of the code in isolation.” Based on their documented scope and the gaps they identify, the audit covered an estimated 20 to 30% of consensus-critical code paths. Finding no critical issues against that baseline is a different claim from confirming the consensus code is secure.
Quarkslab explicitly recommended formal verification as the path forward. Not an external critic making that call, but the auditors who spent 100 man-days inside the codebase, commissioned by Brink, telling the Core development community what the next step should be. It has not happened.
## Structural Issues
The Missing Specification. Bitcoin Core has never produced an independent mathematical specification of its consensus rules that the network treats as a pass-or-fail standard sitting above any one program. BIPs record proposals. They are not that spec. A specification written outside Core does not dissolve the moat until operators and implementations actually use it. Every mature protocol at the infrastructure level has a formal specification that exists independently of any single implementation: TCP/IP, HTTP, TLS, SMTP. The specification defines the protocol. Implementations conform to it. When an implementation diverges from the spec it is wrong, and you can say so precisely. When the network has no adopted spec, the dominant implementation is the spec by default, which means whoever controls the dominant implementation controls the protocol definition. Not through any explicit authority, but through the structural fact that there is nothing else to appeal to.
This is not an accident that nobody got around to fixing but a condition that has been actively maintained. The response to calls for a formal specification has been consistent. The code is the spec. Bitcoin is too complex to specify formally. Any written spec would inevitably diverge from the implementation. Each of these objections has the same practical effect, which is keeping the no-spec condition in place, keeping Core as the sole authority on what the rules actually are, and making it structurally impossible for any independent implementation to prove consensus compatibility without deferring to Core.
Without a specification, any alternative implementation must reverse-engineer undocumented behavior from Core itself. Core stays the thing you check against, even when the other program is built differently. When a consensus-critical behavior changes in Core, an independently written client that wasn’t tracking that specific change becomes a chain split risk. Following Core closely is the safe path, which is why most serious attempts stay Core forks. Independently written clients exist. btcd keeps diverging. libbitcoin exists and the ecosystem cannot use it without being rebuilt. This is why the “just fork it” response to governance criticism is a non-answer. A Core fork inherits the same undocumented behavior, the same 151,004-line implementation, and the same capture vectors. The governance problem follows the code.
This is why no independently written client has been a real check for 17 years, not because writing one is impossible but because the no-spec condition makes proving consensus compatibility structurally impossible without deferring to Core. The moat protecting Core’s position is not technical excellence. It is the absence of a document. libbitcoinkernel, the project intended to extract Core’s consensus logic into a reusable library, confirms rather than refutes this. The proposed solution to implementation monoculture is having every other implementation run Core’s code. That is not diversity. That is a franchise.
Wallet and Node Separation has been a recognized improvement since GitHub issue 7525 in 2016. Running with -disablewallet is not separation. The wallet code is still present in the binary, still compiled, still part of the same release process. An objection on PR [#10102](https://github.com/bitcoin/bitcoin/pull/10102) (still open as draft) treats the outside-library multiprocess approach as a sovereignty problem. That is not an objection to `-disablewallet`. The governance problem follows the dependency regardless of which version of Core’s code you ship.
---
## Policy Monoculture and Revealed Preference
When one implementation sets policy defaults for the entire network, every policy disagreement becomes an all-or-nothing fight for control of what that implementation ships. The OP_RETURN debate was not about 80 bytes. The mempool policy fights, the dust limit arguments, the RBF debates are structurally identical, civil wars over a throne that exists only because there is one throne to capture.
The OP_RETURN debate is worth dwelling on because it illustrates the mechanism precisely. Bitcoin Core merged a change in 2025 raising the default OP_RETURN data limit, a relay policy decision with no consensus implications. Operators who disagreed had no meaningful recourse inside the Core process. For many, the only way to enforce a different policy was to run different software. That is what they did. In 2025 Knots, a Core fork with stricter defaults, went from under 2% to a Coin Dance peak of 25.45% of reachable nodes on September 14, 2025, and stayed above 19% through that stretch. That was a policy switch on Bitcoin, still Core's code. A move in reachable nodes driven by a relay policy disagreement.
Policy does not bind miners who bypass relay. The 83-byte cap belongs at consensus; that is *[Permanent Data Channel Closure](/bips/permanent-data-channel-closure)*.
The demand for policy plurality was always there. The monoculture was suppressing it. When a conservative alternative presented itself, a significant fraction of the network moved to it immediately.
---
## What Better Looks Like
Bitcoin Commons is a from-scratch Rust client built from a human-readable mathematical specification called the Orange Paper. Same chain, same 21 million. It is not a Core fork or a thin wrapper around Core’s consensus logic. Cryptographic merge authorization is designed and stays off until security review, key management, and community validation. The design is meant to make the merge path harder to capture than informal GitHub authority.
## The Orange Paper and the BLVM
The Orange Paper is a formal mathematical specification of Bitcoin’s consensus rules. It defines signature validation, UTXO accounting, script execution, and block structure as mathematical objects with precise definitions rather than as the emergent behavior of a C++ codebase. The BLVM consensus layer is a pure implementation of that spec: deterministic, side-effect-free functions that directly implement the mathematical definitions with no room for undocumented behavioral drift.
The spec is a public good that extends beyond Commons. Any implementation can verify against it. Consensus rule disputes can be resolved by appealing to a document rather than deferring to whoever controls the dominant codebase. The no-spec moat dissolves the moment the spec is published, for everyone.
## The BLVM Specification Lock
The BLVM Specification Lock uses Z3 to check annotated implementation paths against the Orange Paper. Coverage will expand. That is not a claim every consensus property is proven on every merge, or that every CI job has zero-divergence proof to tip. When a locked check fails, the merge fails because the contract failed, not because a reviewer happened to notice.
That is the direction Quarkslab named as the next step for Bitcoin consensus code. Commons is building it.
The Specification Lock also changes who can safely contribute. The primary risk with AI-generated code is subtle behavioral changes that pass code review but alter consensus-critical behavior in ways that are hard to catch. A lock that actually covers the changed path makes that tractable. The barrier shifts from years of pipeline navigation toward writing code that satisfies the contracts.
## UTXO Commitments Without a Consensus Change
The Commons UTXO commitments implementation achieves fast sync without modifying block headers, without a soft fork, without any consensus change. It operates entirely at the P2P layer using a sparse Merkle tree commitment verified against the existing proof-of-work chain.
The trust model is an honest majority of diverse peers, not a single snapshot publisher. The mechanism requires 80% agreement across peers spread by ASN, country, and subnet, so no one peer or one hosting region can feed you a fake set. You download headers, select a checkpoint, query those peers for their UTXO commitment at that height, check it against the header chain and accumulated proof of work, then sync forward with full incremental validation. A hybrid mode does this while verifying the full chain from genesis in the background.
The result is fast sync with no hardcoded hashes, no dependency on any release team, and no new consensus rules required, under that peer-majority assumption rather than under a baked-in release hash.
## Networking and Protocol
Dandelion++ is in the build, covering the threat model that private broadcast does not. The networking layer runs on Iroh and QUIC with NAT traversal alongside the standard Bitcoin P2P transport, so nodes behind residential connections that currently struggle to maintain reliable peer connections get real improvement. High-performance block relay uses Fibre with UDP transport and Reed-Solomon forward error correction. Package relay per BIP331 is implemented. The mempool supports four configurable RBF modes.
Policy is modular. You can configure your own relay and mempool defaults without affecting anyone else’s consensus participation. The dynamic that turns policy disagreements into civil wars under the monolith loses most of its energy when there is no single default to capture.
## Architecture
All consensus logic lives in blvm-consensus, fully separated from storage, networking, and RPC. The architecture is six clean layers from the Orange Paper down to governance enforcement, with explicit interfaces between them. A developer working on the consensus layer cannot accidentally break the networking layer because the boundary is enforced architecturally, not by convention. That separation is what makes formal verification tractable. You cannot formally verify the whole entangled implementation. The 32.1 count is 151,004 implementation lines, 7% of them the rules. You can formally verify a bounded, well-defined consensus module.
The BLVM’s secp256k1 implementation is pure Rust and benchmarks 10 to 22% faster than libsecp256k1 across signature verification workloads.
## Governance
Cryptographic merge authorization is designed and stays off until security review, key management, and community validation. The design has no self-merge at protocol level. Maintainers cannot simultaneously propose and merge their own code. Crate-scoped voting weights contributions proportionally to the subsystem being changed, conflict of interest disclosure is a required part of the process, and the reviewer pool is not gated by years of pipeline navigation through fellowship programs that select for ideological alignment as much as technical capability. The barrier to safe contribution is writing code that satisfies the contracts, which is a technical bar, not a social one.
---
## The Proof
The bottleneck was never engineering. The Dandelion papers are published. The UTXO commitment schemes are fully specified. Erlay has years of development behind it. Formal verification tooling exists and works.
Erlay's measurement dispute is a real technical objection. The structure has no mechanism to resolve it, so the bandwidth protocol dies. Five years later it is still unmerged.
Dandelion's close cited DoS and RBF. Those grounds do not hold. Seven years of nobody picking it up is a priority decision dressed as a technical one.
The stalled list shares a governance structure that cannot process improvements when the coordination cost exceeds the threshold the structure can clear, or when the improvement threatens the institutional position of the people whose funding depends on the status quo. An authorship Gini of 0.851 across 17 years of commit data is not an accident. It is the predictable output of a system where access to merge authority is controlled by a small group with aligned institutional interests and no formal accountability to the node operators running the software.
The conservative governance argument has merit for consensus changes. It has no application to a P2P privacy proposal sitting unmerged for seven years after a priority decision dressed as a technical close. At some point the distinction between intentional conservatism and structural paralysis requires evidence, and the evidence is the list.
Bitcoin is the only monetary network in history not ultimately controlled by a state. That property is fragile. It depends on the network remaining genuinely decentralized at every layer, including the software layer. A network where one development team controls the only production-grade node implementation, where that team’s funding flows from a handful of grant organizations, and where the protocol definition exists only as the emergent behavior of that team’s codebase is not decentralized at the software layer. It is a single point of failure dressed in the language of decentralization.
Commons demonstrates the technical problem is solvable as a program, not as a finished certificate. The Orange Paper exists. The Specification Lock checks annotated paths. Full-chain differential replay against Core is the scale test, operator-driven, and not a CI-to-tip claim. UTXO commitments and Dandelion++ are in the Commons build as engineering answers to the stalled list. That is not a claim the money already runs on those tools. The features that sat unmerged for years can be built from a specification rather than reverse-engineered from that implementation.
The argument is the artifact: a spec, a second client, and a differential program, not a speech about Core.
---
## Sources
- [Fanti, G. et al., "Dandelion: Redesigning the Bitcoin Network for Anonymity"](https://arxiv.org/abs/1701.04439), arXiv:1701.04439, 2017
- [BIP 156: Dandelion, Privacy Enhancing Routing](https://github.com/bitcoin/bips/blob/master/bip-0156.mediawiki)
- [BIP 330: Transaction Announcements Reconciliation](https://github.com/bitcoin/bips/blob/master/bip-0330.mediawiki): Naumenko, G. and Wuille, P., created 2019-09-25
- [Bitcoin Optech: Erlay](https://bitcoinops.org/en/topics/erlay/)
- [Bitcoin Core Issue #7525: Separate Node and Wallet Functions](https://github.com/bitcoin/bitcoin/issues/7525), filed February 12, 2016
- [Rusty Russell, "Pettycoin Revisited Part I: UTXO Commitments"](https://rustyrussell.github.io/pettycoin/2014/11/29/Pettycoin-Revisted-Part-I:-UTXO-Commitments.html): Friedenbach, M., Todd, P., Miller, A. et al., 2014
- [Quarkslab, "Bitcoin Core Security Audit"](https://blog.quarkslab.com/bitcoin-core-audit.html), November 2025: [full report](https://github.com/quarkslab/public-reports)
- [Bitcoin Governance Research](https://github.com/secsovereign/bitcoin-governance-research): 16-year commit history / merge concentration
- [Brink Engineering Impact Report 2025](https://brink.dev/blog/2026/03/26/engineering-impact-report-2025/)
- [Bitcoin Core PR #32359: Remove OP_RETURN size limits](https://github.com/bitcoin/bitcoin/pull/32359), 2025
- [Bitnodes.io](https://bitnodes.io): Bitcoin Knots node statistics
---
# The Last Uncaptured Asset
## Contents
- [I. The Eternal Problem](#i-the-eternal-problem)
- [II. The Three Exits That Were Never Real](#ii-the-three-exits-that-were-never-real)
- [III. The Historical Playbook](#iii-the-historical-playbook)
- [IV. Why Hard Assets Were Always the Refuge, and Always Failed](#iv-why-hard-assets-were-always-the-refuge-and-always-failed)
- [V. The Property That Changes Everything](#v-the-property-that-changes-everything)
- [VI. The Human Layer Is the Attack Surface](#vi-the-human-layer-is-the-attack-surface)
- [VII. The Undefended Social Graph](#vii-the-undefended-social-graph)
- [VIII. They Don't Need to Break It. They Need to Own It.](#viii-they-don-t-need-to-break-it-they-need-to-own-it)
- [IX. The Access Layer Is the Asset](#ix-the-access-layer-is-the-asset)
- [X. The Window](#x-the-window)
---
## I. The Eternal Problem
Every government in history has faced the same structural temptation. Spending buys loyalty, wages wars, builds empires, and wins elections. Taxation is unpopular and has limits. The gap between what governments want to spend and what they can extract from their populations always widens over time, and the mechanism for filling that gap is always the same: borrow, defer, and let the next generation worry about it.
This is not a modern pathology. The Roman Empire debased its currency across three centuries, shaving the silver content of the denarius from near purity down to a thin plating over bronze. The Spanish crown defaulted on its debts fourteen times between 1557 and 1696 despite controlling the most productive silver mines in the world. Revolutionary France issued assignats backed by confiscated church property and watched them collapse to worthlessness within five years. The British Empire financed two world wars through bond issuance, then spent much of the twentieth century in managed decline, liquidating assets to service debts its economy could no longer outgrow.
The pattern is not coincidental. It is structural. Governments that can borrow will borrow. Debt that accumulates long enough becomes impossible to repay at face value. At that point the math forces a reckoning, and the reckoning always takes one of three forms.
---
## II. The Three Exits That Were Never Real
When a government's debt becomes visibly unsustainable, it offers its citizens three exits: grow the economy out of the problem, cut spending until the books balance, or tax the wealthy until the gap closes. **These are not failed solutions. They are political theater**, and the distinction matters.
Growth does not resolve a compounding debt problem. It delays the reckoning while the underlying dynamic continues. A government that borrows faster than its economy grows is not on a path that growth can fix, because the borrowing accelerates alongside the growth, and the interest compounds regardless. Growth is offered as an exit because it asks nothing of anyone in the present. It is a promise about the future made by people who will not be in office when the future arrives.
Austerity asks something of the present, which is why it never survives contact with democratic politics long enough to matter. The constituencies that depend on government expenditure are concentrated, organized, and loud. The taxpayers who would theoretically benefit from fiscal discipline are diffuse, distracted, and quiet. Every serious austerity program in a democratic system has been reversed before completion, usually by the same political parties that imposed it. Greece endured a decade of external compulsion and still did not close the gap. Austerity is offered as an exit because it sounds responsible. It is not designed to succeed.
Taxation runs into the one thing that capital does better than almost anything else: move. Raise rates to the level required to close a gap of the magnitude we are discussing, and the assets being taxed restructure, relocate, or disappear into complexity before the revenue arrives. This is not tax evasion as an aberration. It is capital behaving exactly as capital behaves. Tax revenue does not rise linearly with tax rates; at some point, further increases change the behavior being taxed rather than capturing it. The observation is mechanical, not ideological.
These three exits are not offered in good faith. They are offered because **a government that acknowledges no exit exists cannot sustain the legitimacy it needs to continue operating.** The performance of trying the conventional options buys time and political cover while the actual resolution proceeds through other mechanisms entirely.
The retail cover for staying inside is the index. Headline S&P 500 returns compared to official CPI are sold as the private exit from the same debasement. Sequential accounting of what that comparison leaves out is in [The_SP500_Sleight_of_Hand.md](../03-analytical/capture-apparatus/The_SP500_Sleight_of_Hand.md). That is not a fourth public exit. It is how the playbook in §III keeps looking like wealth creation.
Public exits vs actual resolution
Offered publicly
GrowthAusterityTaxation
while debt resolves via
Actual playbook
Inflation→Repression→Seizure
Political theater buys time. The mechanisms in §III deploy in combination, usually while one of the public exits is still being debated.
---
## III. The Historical Playbook
The actual resolution of sovereign debt crises is not growth, austerity, or taxation. **It is inflation, financial repression, and seizure**, deployed in combination, usually while the government is publicly committed to one of the three exits above.
Inflation is the oldest and most reliable mechanism. If the debt is denominated in a currency the government controls, printing enough money to repay it in nominal terms is always technically available, regardless of what it does to the real value of those repayments. Creditors are repaid in full in a currency that buys half of what it did when they lent it. The debt vanishes without a formal default. Germany inflated its World War I debt into oblivion between 1921 and 1923. The United States inflated away a substantial portion of its World War II burden through the sustained moderate inflation of the 1940s and 1950s. Every major fiat currency has lost the vast majority of its purchasing power over the past century, and most of that loss was a policy outcome, not an accident. Why monetary sovereignty is load-bearing for every other form of independence is in [Conditions_Of_Flourishing.md](../03-analytical/civilizational/Conditions_Of_Flourishing.md).
Financial repression is inflation's quieter mechanism. Rather than printing money visibly, the government uses regulation to force captive pools of capital to hold government debt at below-market rates. Banks are required to hold Treasuries as tier-one capital. Pension funds are required to allocate minimum percentages to government bonds. Insurance companies are regulated into portfolios heavy with sovereign paper. The real return is negative after inflation, but the holders cannot exit because the regulations prohibit it. The wealth transfer is real and sustained, and it happens slowly enough that most people never identify the mechanism that is impoverishing them. The United States used financial repression extensively from 1945 through the early 1970s to bring its war debt ratio down from above 100 percent of GDP to manageable levels. The 401k equity sleeve is the retail form of the same captive pool. Pension and insurance mandates force government paper. The 401k forces a different capture, continuous retail inflow into the index, recruited by the headline return, with real purchasing power after tax, fees, and honest inflation far below the number used to justify the contribution. The accounting is in [The_SP500_Sleight_of_Hand.md](../03-analytical/capture-apparatus/The_SP500_Sleight_of_Hand.md).
Seizure is the bluntest instrument and the most honest. When inflation and repression are insufficient, governments reach directly for the assets. Franklin Roosevelt's Executive Order 6102 in 1933 required American citizens to surrender their gold to the Federal Reserve at $20.67 per ounce. Once transferred, Roosevelt revalued it to $35 per ounce, capturing the appreciation for the state. The citizens who had held gold as a hedge against exactly this kind of monetary manipulation were paid a price that reflected none of the scarcity value they had correctly anticipated.
The playbook runs in this order because each step is more politically costly than the last. Inflation is invisible until it isn't. Financial repression is bureaucratic and dull. Seizure is naked and remembered. But when the debt is large enough and the crisis acute enough, governments reach all the way to the end.
Actual debt-resolution playbook
Mechanism
How it works
Historical example
Political cost
Inflation
Repay nominal debt in debased currency
Weimar 1921–23; US WWII debt (1940s–50s)
Low until visible
Financial repression
Force captive capital into sovereign debt at negative real rates
US 1945–early 1970s (debt/GDP >100% → manageable)
Low (bureaucratic)
Seizure
Direct transfer of assets at below-market price
EO 6102 (1933): gold at $20.67, revalued to $35
High (remembered)
Actual debt-resolution playbook, usually deployed while public exits in §II are still debated.
---
## IV. Why Hard Assets Were Always the Refuge, and Always Failed
Every generation that lived through a fiat currency crisis learned the same lesson: hold something real. Gold, land, foreign currency, productive assets that the government cannot conjure into existence. The flight to hard assets is rational, historically documented, and almost universal among people who understood what was happening to the money around them.
And it almost never worked.
Gold was the canonical hedge for most of monetary history. It is scarce, durable, fungible, and recognized across cultures and centuries. It has no counterparty risk in the sense that it doesn't depend on any institution's promise to be gold. And yet it is dense, detectable, and physical. You cannot hide a significant quantity of gold from a government that has decided to find it.
Roosevelt's confiscation order worked for the reasons the seizure playbook already established: gold is bulky enough that meaningful quantities cannot be quietly moved, and the financial system of the era made identification trivial through bank records and safe deposit box inventories. People who buried gold in their yards kept it, but they could not use it, and using it was the point.
Real estate is the other traditional hard asset. Land doesn't disappear. Productive property generates income. And yet governments can tax real property into effective confiscation through property taxes that exceed rental income. They can zone it, condemn it, nationalize it outright, or simply regulate its use until its economic value evaporates. Agricultural collectivization across the Soviet bloc in the late 1920s and 1930s transferred the productive value of farmland from private holders to the state through a combination of legal mandate and violence. It was the most comprehensive seizure of a hard asset class in modern history, and the holders had no recourse.
Foreign accounts and foreign currency offered partial escape. Move assets into a jurisdiction with stronger rule of law, a harder currency, or less political instability. This works until the home government decides it doesn't. Capital controls have been imposed by dozens of governments in crisis, from Argentina's corralito in 2001 to Cyprus's bank deposit haircut in 2013 to Greece's ATM withdrawal limits in 2015. The SWIFT messaging system and correspondent banking relationships give the United States extraordinary leverage over cross-border asset movement, leverage used explicitly as a foreign policy tool and available for domestic use in a sufficiently severe fiscal crisis.
Every hard asset, without exception, has a physical location or a jurisdictional address. **That location or address is the attack surface.** A sufficiently motivated government with adequate enforcement capacity can reach it.
Hard assets and seizure surfaces
Asset
Attack surface
Historical example
Why refuge failed
Gold
Physical bulk; bank and safe-deposit records
EO 6102 (1933)
Detectable; unusable if hidden
Real estate
Fixed jurisdiction; tax, zoning, condemnation
Soviet collectivization (1920s–30s)
Location is the title
Foreign accounts / FX
Capital controls; correspondent banking; SWIFT
Argentina 2001; Cyprus 2013; Greece 2015
Cross-border rails are jurisdictional
Bitcoin (theoretical)
No physical object; key is a number
n/a
Self-custody can avoid location; access layer reintroduces it (§VI–IX)
Hard assets and seizure surfaces. Bitcoin's theoretical case rests on combining scarcity, jurisdictionlessness, and self-custody (§V).
---
## V. The Property That Changes Everything
Every generation that encountered a new hard asset made the same argument: this one is different, this one they can't reach. The argument was always partially true and ultimately wrong, because every asset has a surface and every surface can eventually be found. Bitcoin's advocates make the same claim, and the skeptic's instinct is to file it with the others. The difference is structural rather than rhetorical, and it is worth examining precisely.
The theoretical case for Bitcoin as a genuinely seizure-resistant asset rests on a specific set of properties that no prior asset class has combined.
It is mathematically scarce. The supply schedule is encoded in the protocol and enforced by every node on the network. No government, no corporation, and no developer can create more Bitcoin than the protocol allows. This is a different kind of scarcity than gold's. Gold's scarcity is geological and economic: higher prices eventually bring more supply to market. **Bitcoin's scarcity is definitional.** The twenty-one million coin limit is not a convention that can be revised by a regulatory body or a corporate board.
It is jurisdictionless. Bitcoin transactions propagate across a global peer-to-peer network without passing through any single country's infrastructure. There is no Bitcoin headquarters, no Bitcoin CEO, no Bitcoin regulatory address. A transaction broadcast in one country can be confirmed by miners in another and received by a node in a third. **The asset itself has no nationality.**
Most importantly, it is potentially self-custodied. A private key is a number. A number can be memorized. A memorized key controls Bitcoin that exists as entries in a distributed ledger maintained by thousands of computers globally. There is no physical object to confiscate, no vault to open, no safe deposit box to inventory. **If the key exists only in a person's memory and the coins have never touched a system that knows the owner's identity, the government's normal seizure toolkit does not engage.**
These three properties together describe something that has never existed before in monetary history: **a scarce asset that can be held without a physical location, transferred without a financial intermediary, and potentially kept beyond the reach of any state actor.** Whether that theoretical potential survives contact with the actual systems humans have built around Bitcoin is a different question. The asset can still be uncaptured while the access layer is not.
Sound money and privacy are layers of one stack, not two projects. Self-custody is bearer settlement at the base. It does not make the transaction graph private. Chain analysis can reconstruct who paid whom from the ledger even when the legal name behind a key is still unknown. Vocabulary for disclosure, secrecy, and anonymity is in [Privacy_Disclosure_Control.md](Privacy_Disclosure_Control.md).
---
## VI. The Human Layer Is the Attack Surface
The rules that define Bitcoin are not the same thing as the system that implements them. Those rules run as software written by specific people, mined by hardware operators in specific jurisdictions, and accessed through interfaces built by companies subject to specific laws. **The gap between the rules and the system is where every serious attack vector lives.**
Mining is the process by which transactions are confirmed and new blocks are added to the chain. Miners are not abstract participants. They are companies running data centers, consuming electricity purchased from utilities in specific jurisdictions, operating hardware manufactured in a handful of facilities globally. The geographic distribution of mining hashrate has shifted over time, but significant concentrations exist in western jurisdictions including the United States. **A dominant mining pool within reach of a sufficiently determined government is not a theoretical vulnerability. It is an operational one.**
Software development is more concentrated still. Bitcoin Core, the dominant implementation of the Bitcoin protocol, is maintained by a small number of developers who are identifiable, located primarily in western jurisdictions, and reachable through ordinary legal process. The repository lives on GitHub, an American company subject to American law. The communication channels where development decisions are made are monitored and archived. **There is no anonymity in the Bitcoin Core developer community worth speaking of.** If those people fold under legal or personal pressure, the software layer folds regardless of what the cryptography says.
Cheap governance exit on the same chain is what makes that pressure fail. That is *[The Vertical Layer Problem](/articles/the-vertical-layer-problem)*, not a claim that more implementors will automatically resist.
Node operators are the network's validators, the participants who enforce the rules and reject blocks that violate them. Running a node is the deepest form of participation in the network's consensus. But node operators are also individuals running software on hardware connected to the internet in physical locations. The jurisdictional reach problem applies to them as directly as it applies to miners.
What this means is that **Bitcoin's human layer has the properties of any other human institution:** identifiable people in specific locations, with social relationships, financial dependencies, and legal exposure. The protocol's properties do not transfer automatically to the people who implement and maintain it.
---
## VII. The Undefended Social Graph
Bitcoin Core's governance, by design and by philosophy, is informal. Core has never produced an independent mathematical specification of the consensus rules that the network treats as a pass-or-fail standard. There is no governance structure with defined roles, decision rights, or accountability mechanisms. The authority to merge code into the dominant implementation rests with a small number of maintainers whose legitimacy derives from social consensus within a community whose membership and norms are themselves informally defined. For the funding map, merge concentration, and documented adversarial cases, see *[Who Controls Bitcoin](/articles/bitcoin-governance)*.
This was intended to make the system resistant to capture by any single actor. Instead it created what might be called **an undefended social graph:** a network of trust relationships between identifiable people, with no threat modeling applied to those relationships, no awareness that the relationships themselves are an attack surface, no documentation trail that would make influence visible, and no protocols for detecting when someone in the network has been compromised or turned. The structural logic of why that graph is so easy to influence (and why cryptography was never the relevant battleground) is developed at length in *[The Social Layer Is the Attack Surface](/articles/bitcoin-social-capture)*.
Intelligence agencies and influence operations have been working social graphs for as long as intelligence agencies have existed. The Bitcoin developer community is an unusually legible, concentrated, and high-value target. **The absence of formal governance doesn't make it harder to influence. It makes it easier**, because there are no formal accountability structures to work around.
The informality that Bitcoin Core describes as organic and decentralized is actually the highest-value attack surface in the entire system. **You don't need to compromise the code. You just need to compromise the relationships**, or threaten the people, or write a regulation that requires disclosure to a designated authority. Each of those is well within the operational capacity of any serious state actor, and none of them requires touching a single line of cryptography.
---
## VIII. They Don't Need to Break It. They Need to Own It.
State capture of Bitcoin follows the same logic as historical asset seizure: **not destruction of the asset, but transfer of control over who holds it and on what terms.**
The naive model of government Bitcoin suppression involves banning it, attacking the network, or somehow breaking the cryptography. **None of these is the actual threat model** for a government sophisticated enough to understand what it's dealing with.
A government facing a fiscal crisis doesn't want to destroy a scarce asset whose value it needs. It wants to control that asset, capture its appreciation for the state's balance sheet, and prevent private holders from using it as an escape hatch from the monetary system the government is debasing. This is a very different objective, and it calls for a very different set of tools.
Roosevelt didn't melt the gold. **He transferred it.** The confiscation order of 1933 moved gold from private vaults to government vaults, preserved its value, and then revalued it upward once the transfer was complete. The private holders who complied were paid the pre-revaluation price. The government captured the appreciation. **The mechanism was not destruction but transfer of title.**
Applied to Bitcoin, the equivalent operation looks less like a cyberattack and more like a regulatory framework. Declare Bitcoin a strategic financial asset requiring registration. Mandate disclosure of all holdings above a threshold. Make unregistered holdings a criminal offense rather than merely an unregulated one. Use the existing surveillance apparatus to identify and prosecute high-profile non-compliant holders as examples. Offer a compliance window with favorable terms to encourage voluntary registration before enforcement begins.
**The Bitcoin industry has been building the infrastructure for this operation voluntarily**, in exchange for legitimacy and growth. The mechanism is not a cyberattack. It is the access layer, detailed in the next section. These decisions were rational for the companies that made them. **They are catastrophic for the system's seizure resistance properties in aggregate.**
---
## IX. The Access Layer Is the Asset
There is a distinction that most Bitcoin holders don't fully reckon with: **the difference between holding Bitcoin and holding access to Bitcoin's economic utility.**
A private key controls Bitcoin. But a private key is economically inert unless it can be connected to a system where Bitcoin can be exchanged for goods, services, or other currencies. That connection runs through the access layer, and **the access layer is fully mapped, regulated, and in most jurisdictions already operating under government oversight.**
ETF providers have accumulated a meaningful and growing share of the total Bitcoin supply in regulated custodial vehicles. They recreate the exact counterparty and confiscation surface that self-custody eliminates, at a scale that shifts the center of gravity of the asset toward the captured layer.
Every exchange with Know Your Customer verification is a registry of Bitcoin holders, their holdings, and their transaction histories. Every regulated on-ramp that has processed a deposit links a government identity to a Bitcoin address. The Travel Rule, which requires financial institutions to share sender and receiver information for transactions above threshold amounts, is being extended in most major jurisdictions to cover transfers to and from unhosted wallets.
The infrastructure for a comprehensive registry of Bitcoin ownership is not being built. **It has been built.** It went live gradually over the past decade, each step framed as compliance with anti-money laundering regulations, each step adding another layer to a surveillance apparatus that now covers the majority of economically significant Bitcoin activity.
Self-custody of coins that have never touched a Know Your Customer system is genuine escape from this registry. But it is a vanishingly small fraction of the total Bitcoin by value, concentrated among early holders and technically sophisticated users who understood the access layer problem before most of the industry was built to obscure it.
The coins exist on the ledger. The private keys are real. And yet for the majority of holders, those coins are accessible only through systems already subject to the same government whose monetary policy they were supposed to escape. The theoretical properties of the protocol do not change this. **The access layer is the asset for most people, and the access layer is already captured.**
---
## X. The Window
Every asset that governments have eventually captured went through the same phase: a period when the asset was valuable enough to matter, the capture mechanisms were not yet in place, and the people who understood what was happening had time to act. **That window is always shorter than it looks from inside it.**
For gold, the window between the Federal Reserve Act of 1913 and Roosevelt's confiscation order of 1933 was twenty years. People who understood monetary history used those years to accumulate gold and move it beyond government reach. Most people didn't, because the scenario seemed extreme until the morning it happened.
Bitcoin's window opened when its value registered as a fiscal resource worth capturing. It has been closing ever since, from the first regulated on-ramps and custodial products through the access-layer capture described above. **The window is not yet closed.** Self-custody works. Peer-to-peer transactions work. The parts of the protocol that matter are still intact.
What would keep the window open is not primarily a technical question. **The cryptography is not the vulnerability.** What would keep it open is implementation diversity across jurisdictions, so that no single government can reach the entire developer community through ordinary legal process. It is formal specification of the consensus rules, so that the protocol's definition exists in mathematics rather than in the social consensus of a small group of identifiable people. It is node operation distributed widely enough that the enforcement cost of shutting down participation exceeds the political benefit of attempting it.
These are not wishful abstractions. They are engineering problems, and engineering problems can be solved. **The question is whether they get solved before the window closes**, or after, when solving them becomes an act of resistance rather than an act of construction.
The window is still open. What anyone does with that fact is up to them.
*Companion to [Who Controls Bitcoin](/articles/bitcoin-governance), [The Social Layer Is the Attack Surface](/articles/bitcoin-social-capture), and [Why Shitcoins Are Shitcoins](/articles/why-shitcoins-are-shitcoins) (structural case against altcoins as monetary assets).*
---
# The Achievable Floor: What Consensus Can and Cannot Close on Arbitrary Data
## Contents
- [I. Framing the Problem](#i-framing-the-problem)
- [II. Taxonomy of Channels by Cost](#ii-taxonomy-of-channels-by-cost)
- [III. What Consensus Can Actually Close](#iii-what-consensus-can-actually-close)
- [IV. Why the Free Channels Resist Closure](#iv-why-the-free-channels-resist-closure)
- [V. Custody of Data That Already Exists](#v-custody-of-data-that-already-exists)
- [VI. The Actual Floor](#vi-the-actual-floor)
- [VII. Implementation Path](#vii-implementation-path)
- [VIII. Conclusion](#viii-conclusion)
---
## I. Framing the Problem
The Bitcoin spam debate blurs **two layers.** Consensus forces every validating node to accept whatever is in a valid block, monkey jpegs included. **Relay and storage are policy.** No node must forward a transaction before it confirms, and no node must keep every byte forever after validation. Pruning exists because long-term storage is optional.
Pruning has a cost. A pruned node cannot re-check the full chain from its own disk without asking someone else for old blocks. Pruning also does not remove the first-sync cost. Every pruned node still downloads and validates the whole history, including non-monetary data, during initial block download. The spam still passes through every new node at first sync, whether that node keeps the data afterward. Bandwidth and validation time at join are permanent costs on every participant who syncs. **Pruning changes when you pay for storage. It does not remove the download.**
**Refusing to relay is not banning.** Miners and permissive nodes still include transactions that pay competitive fees, regardless of one operator's mempool policy. Relay limits on `OP_RETURN` and similar fields are per-node settings: any operator can tighten them, loosen them, or turn them off. **Consensus caps bind every participant or fail to activate.**
The fight is usually about consensus capture, forking risk, and who decides which use cases are legitimate. For OP_RETURN and data-embedding politics, see *[Who Controls Bitcoin, §V](/articles/bitcoin-governance#v-the-adversarial-layer-when-conflicts-become-visible)* and *[Argument Map, Parts VI–VII and XXII](/articles/bitcoin-governance-argument-map#part-vi-forced-participation)*.
Set politics aside. If consensus could change freely, how much non-monetary data could rules actually eliminate, and where is the hard floor?
Spam has a workable definition. A spam transaction does not settle money, and it imposes lasting costs on every validating node. Lightning channel opens and closes settle money. Timelocked outputs and multisig setups settle money. A JPEG stuffed into a Taproot envelope does not. That follows from how Bitcoin works: every validating node must process the full chain history to know current balances. Using the payment layer as a cheap bulk data store pushes costs onto a network built for transfers, not file hosting. For the full case against non-monetary embedding, see *[Bitcoin Is Not a Hard Drive](/articles/bitcoin-not-a-hard-drive)*.
Demanding a definition that can never be met is not a technical objection.
## II. Taxonomy of Channels by Cost
Non-monetary data can enter blocks through several different fields and transaction shapes. Those paths are not equally cheap. The ladder below ranks them by what it costs the person embedding the data.
*Channel cost ladder from free to dedicated embedding channels*
*Figure: Channel cost ladder. Consensus can close dedicated and unenforced paths without breaking normal payments.*
**Free channels** cost nothing beyond the ordinary transaction fee.
The main free path is any field that stores a hash of a key or script instead of revealing the key or script itself: P2PKH or P2WPKH destinations, Lightning hash locks, and P2SH or P2WSH script hashes. A fake 20 or 32 byte string looks the same as a real hash. Pay-to-Fake-Key and Pay-to-Fake-Multisig (payments to fake keys or multisig that look like real addresses) predate `OP_RETURN`. The 2010 WikiLeaks Cablegate dump used this method.
Inviscription is one such scheme: it splits encrypted data across hash-locked outputs, multisig key slots, or timelock fields. The decryption key may appear in a later transaction or never on chain.
Output amounts are free too. Consensus cannot tell whether a chosen value encodes data or is just a payment. Attackers can hide data in the satoshi amounts of outputs, not only in scripts or witness data.
Structural fields add more. `nSequence` and `nLockTime` can each carry a few bytes of data. Input and output order is unconstrained. Consensus could force fixed values for all of these, but that would break how ordinary wallets build transactions. **You would harm normal payments without stopping spam**, the same problem as trying to ban flexible output amounts.
**Near-free channels** cost a small number of trial attempts.
Taproot's 32 byte pubkey field is the standard example. Roughly half of all 32 byte strings are valid public keys on Bitcoin's curve. Hiding a chosen payload as a fake pubkey takes about two random tries on average.
The same low cost applies to other standard address fields: P2WPKH and P2PKH hash slots accept any 20-byte string, and P2TR pubkeys need only a few tries. Researchers measuring real blocks have found hundreds of kilobytes of data embedded this way.
**Expensive channels** require brute-force search. The attacker keeps trying random keys or signatures until one matches a desired bit pattern. Cost grows exponentially with how many bits they want to fix. Vanity addresses use the same trick, pointed at chosen targets.
**Unenforced channels** have no content rules today.
Undefined witness versions and OP_SUCCESS opcodes are upgrade hooks. Consensus treats anything after an OP_SUCCESS byte in Tapscript as valid, no matter what it contains. The Taproot annex is extra witness data left out of the signature that authorizes the spend, with no limit on what it holds. **The annex can hold raw bytes. Nothing has to be disguised as a hash or public key.**
**Dedicated channels** exist to carry data, or hold large script blobs with no payment meaning.
`OP_RETURN` is an output that cannot be spent. Core v30 relay policy allows up to 100,000 bytes of `OP_RETURN` data per transaction, across multiple outputs (`MAX_OP_RETURN_RELAY = MAX_STANDARD_TX_WEIGHT / WITNESS_SCALE_FACTOR`). Consensus itself places no byte limit. In June 2023, PR #27832 (maflcko, opened 2023-06-06, merged 2023-08-03) clarified that `-datacarriersize` measures serialized `scriptPubKey` size, with tests at `datacarriersize=0` rejecting even an empty `OP_RETURN`. The PR body does not mention inscriptions. Witness and inscription fields falling outside that knob is the effect. Core v30 then removed the relay cap entirely in 2025. Separately, the Taproot envelope hides data inside an `OP_FALSE OP_IF` branch that never runs. SegWit's witness discount and Taproot's removal of the old 10,000 byte script ceiling made large envelope payloads practical.
Consensus measure
Channel closed
Independent soft fork?
OP_RETURN hard byte cap
Dedicated (OP_RETURN outputs)
Yes
Taproot envelope push cap
Dedicated (OP_FALSE OP_IF branches)
Yes
Witness version restriction
Unenforced (OP_SUCCESS hooks)
Yes
Annex disallow or cap
Unenforced (Taproot annex)
Yes
Control block size cap
Unenforced (deep Merkle path hiding)
Yes
Per-output miner fee
Low-value UTXO spam (output count)
Yes
UTXO set commitments
Permanent storage burden for data already on chain (§V)
*Closability by channel type*
## III. What Consensus Can Actually Close
Closable and unclosable paths are not the same problem. `OP_RETURN` and Taproot envelope embedding can be closed at consensus. Sending a transaction straight to a mining pool, private miner peering, and other off-relay paths cannot be closed at consensus without redesigning how mining works. After closing what consensus can close, some spam may still reach blocks through paths consensus cannot shut. **That is not an argument against closing the paths consensus can shut.** Treating those as one objection is a mistake.
Dedicated and unenforced channels can close at consensus. Ordinary payments do not need them.
A consensus hard cap on `OP_RETURN` closes bulk dedicated-data outputs and binds every participant. Relay limits bind only the operators who choose them.
Consensus can also cap data hidden in script branches that never run, including the `OP_FALSE OP_IF` envelope used for inscriptions. *[Permanent Data Channel Closure](/bips/permanent-data-channel-closure)* does that by invalidating `OP_IF` and `OP_NOTIF` anywhere in Tapscript, even unexecuted. Current P2WSH Lightning is unaffected. Taproot Miniscript and taproot-channel HTLC leaves must split those branches into separate leaves.
Consensus can also restrict unused witness versions, ban or cap the annex, and cap the Taproot control block (the path that reveals which script branch is being spent) so large unused branches cannot smuggle big payloads.
A consensus per-output miner fee makes creating many outputs expensive. Unlike a minimum output value (capital the spammer can recycle on spend), the fee is paid to the miner as ordinary transaction fee and does not come back. That hits spam that spreads data across lots of small outputs. Higher fees make each of these limits cost the embedder more. See *[Static Per-Output Miner Fee](/bips/static-per-output-miner-fee)*.
The rows below close dedicated and unenforced embedding channels. **§V addresses data already on chain** through UTXO set commitments (less UTXO state to store). That layer is independent of the caps here. Initial block download still carries the full history; AssumeValid does not remove that cost.
*Closable measures. First five rows: Permanent Data Channel Closure. Per-output fee: Static Per-Output Miner Fee plus optional Dynamic Escalation. Commitments remain a parallel track (§V). §IV fields omitted because monetary design requires them.*
Closable at consensus→Higher cost
fee market
Structural fields→Brute-force limit
*Consensus-closable channels versus the irreducible embedding floor*
*Figure: §III closes OP_RETURN, envelope, annex, control block, and per-output fee. §IV fields cannot.*
## IV. Why the Free Channels Resist Closure
Closing free or near-free channels either breaks normal payments or barely raises the cost of spam.
**Checking whether a fake pubkey is a valid curve point** barely helps. With near-free channels, an attacker can keep trying random values until almost any payload passes the check, so the filter blocks almost nothing.
**Requiring the real pubkey, or a zero-knowledge proof of one, when an output is created** closes hash-based channels but ends hash-then-reveal privacy for every user. P2PKH and P2WPKH withhold the pubkey until spend time so funds stay safe if the cryptography behind the address is ever broken. **That protects all users; giving it up to chase spam would be a bad trade.**
The zero-knowledge variant keeps privacy but still fails. An attacker can brute-force a real keypair until its hash encodes a payload, and every payment would need extra zero-knowledge verification overhead.
**The amount channel** costs the attacker nothing. Sequence numbers, locktimes, and input or output ordering work the same way.
Rounding all amounts to coarser units removes some low bits, not the channel. The attacker still picks which multiple to use. Across 21 million bitcoin, coarsening still leaves tens of bits per output, and every user loses payment precision.
Fixing input order or mandating single sequence and locktime values hits the same wall. There is no single correct value, only a range. One mandated choice breaks ordinary wallet use.
**Encrypted amount schemes**, as in Liquid and Mimblewimble, hide amounts on chain but remove the ability for anyone to audit total supply.
Inscriptions, BRC-20, and Rune issuance pay fees and look like ordinary payments at the consensus layer. Users will keep paying for them. Closing those paths gets politically harder; the free channels stay open.
Bitcoin was built for payments, not token registries, inscriptions, or bulk data availability. The free fields exist because payments need them.
## V. Custody of Data That Already Exists
Sections I–IV are about new data reaching the chain. **Two separate problems remain for data already stored:** how much history a new node must download at first sync, and how much UTXO state every node must keep afterward.
**Initial block download.** A full node still downloads the chain from genesis: every block, every transaction, every witness, including years of non-monetary data. Bitcoin Core's AssumeValid setting can skip script verification for blocks before a trusted hash, which cuts CPU during sync. **It does not skip the download.** The spam still crosses the wire for every new node. AssumeValid does not close embedding fields for new transactions, and it is not a substitute for consensus caps on dedicated channels.
**UTXO set commitments.** Fake hash outputs stay in the UTXO set until spent. Without the secret behind the hash, no one knows whether an output will ever move. Inscription outputs already dominate UTXO count while holding almost no monetary value.
UTXO set commitments let a node keep a short root hash instead of the full set, and check spends using proofs the spender provides. Every node no longer has to store the whole set locally; spenders supply what is needed to prove ownership. Utreexo is one design. Putting that root in the block header under consensus rules removes the need to trust special bridge nodes that hand out set data.
Some production designs ask peers to agree on the root rather than committing it in consensus rules. That requires trusting that most peers report the same value. Commitments change ongoing set storage. They do not remove the IBD download cost above.
## VI. The Actual Floor
`OP_RETURN`, the Taproot envelope, undefined witness versions, and the annex can close at consensus. Payments do not need them.
Dedicated channels and witness-discounted envelopes drove most of the bandwidth. What remains is built into payment design: hash fields, amounts, sequence, locktime, and ordering. Close those and you lose hash-then-reveal privacy, satoshi precision, or supply auditability. **UTXO commitments can reduce how much old state each node stores. AssumeValid can cut script-check CPU during sync; it does not cut the download. Neither removes the embedding floor in §IV.**
Some embedding capacity is built into payment fields on purpose. **Those fields exist for security and privacy, not as spare storage.**
The blockspace impact is measured, not guessed. A full chain scan across 912,723 blocks and roughly 1.235 billion transactions finds spam's share of blockspace about 17 times higher than its pre-inscription baseline. Non-monetary data accounts for an estimated 12 to 19% of total chain storage; for the full operator-cost model behind those figures, see *[Full Cost of Running a Bitcoin Node](/articles/full-cost-of-running-a-bitcoin-node)*. Per Mempool Research, 29.6% of all UTXOs are inscription-related, holding about 415 BTC in total value. Blocks ran between 91 and 97% full across multiple weeks in 2026. After Core v30 removed the relay cap on `OP_RETURN`, [Renaud Cuny's December 2025 analysis](https://blockspaceweekly.substack.com/p/issue-3-three-years-of-spam) found large OP_RETURN activity starting immediately while inscription witness data continued at scale, roughly 36% of blockspace non-financial as of December 2025. The policy change opened a new channel without closing the old one. Claims that the impact is negligible require ignoring documented methodology and published measurements. For the governance timeline behind removing the relay cap, see *[Who Controls Bitcoin, §V](/articles/bitcoin-governance#v-the-adversarial-layer-when-conflicts-become-visible)*.
Another reply says the block weight limit already makes spam acceptable: each block is capped at roughly four million weight units (often called a four-megabyte ceiling), so damage has an upper bound.
That is a per-block validation rate limit, not a verdict on what the capacity is for. The cap keeps one block finite to validate. It does not bound the cumulative stock of confirmed non-monetary bytes. Every spam byte still hits every future IBD, still occupies archival storage, and for fake-hash or dust-shaped outputs still accumulates in the UTXO set. **A capped rate over years is still a large permanent burden.**
The same ceiling is the monetary settlement budget. Blocks at 91 to 97% full with a large non-financial share are non-monetary demand competing for scarce payment capacity, not harm already contained. BIP141 makes the bound asymmetric: witness bytes cost one weight unit and non-witness bytes cost four, so envelope payloads buy more raw data per weight unit than base-transaction payment data. Weight also rate-limits new outputs per block without forcing never-spent spam UTXOs out of the set afterward. The inscription-related UTXO share above is bounded rate with unbounded accumulation of the wrong state.
What the weight limit does
What the spam debate is about
Caps bytes (by weight) in one block
Permanent IBD, storage, and UTXO costs across all future nodes
Keeps one-block validation finite
Whether non-monetary use should consume the scarce settlement budget
Same MWU budget for all tx types
Witness discount admits more envelope payload per MWU than base payment data
Rate-limits new outputs per block
Does not evict unspendable or never-spent spam UTXOs afterward
Block weight is a DoS bound on one block, not a verdict that filling it with non-monetary data is acceptable.
*Block weight is a DoS bound on one block, not a verdict that filling it with non-monetary data is acceptable.*
The weight limit answers whether one block can overwhelm a node. The spam problem asks who permanently pays bandwidth, disk, and UTXO set for non-monetary state. Those are different threats. For the same point as a justification failure, see *[Bitcoin Is Not a Hard Drive, §VI](/articles/bitcoin-not-a-hard-drive#vi-the-justifications-and-their-failures)*.
**Cost per embedded byte.** The figures below are structural arithmetic from §II channel sizes, BIP141 weight rules, and Core v30 relay defaults. They are not a measurement of the live chain.
**Payload size.** Core v30 defaults `-datacarriersize` to **100,000 bytes** of aggregate `OP_RETURN` `scriptPubKey` per transaction. Consensus imposes no byte cap. Both dedicated rows use **1,024 bytes** of payload. The per-transaction size limit binds before the datacarrier limit. The hash row uses 20 bytes per fake P2WPKH output; the near-free row uses 32 bytes per fake P2TR pubkey (§II).
**Witness discount (BIP141).** Witness bytes count one weight unit; non-witness bytes count four. Envelope payload sits in witness. Hash and pubkey payloads in `scriptPubKey` are non-witness, so they cost about four times as much per embedded byte.
**Bytes used.** An `OP_RETURN` with a 1,024-byte push is 1,039 vbytes (8-byte value, 3-byte varint, 1,028-byte script). P2WPKH with a 20-byte fake hash is 31 vbytes. P2TR with a 32-byte fake pubkey is 43 vbytes. Envelope at 1,024 witness payload bytes is 43 vbytes of output plus 256 vbytes of witness (wrapper and spend overhead omitted; full minimal spend ≈377 vbytes).
**After closing dedicated channels.** Dust defaults at 3 sat/vbyte (`DUST_RELAY_TX_FEE = 3000` sat/kvB) are 294 sat for P2WPKH-shaped outputs and 330 sat for P2TR-shaped. `OP_RETURN` outputs are zero-value and omitted. Dedicated rows show fee cost only; hash and pubkey rows add the dust floor because embedding creates spendable-looking outputs.
*BIP141 accounting, Core v30 `-datacarriersize` (100k), dust at 3 sat/vB. Fee columns: (vbytes × rate + dust where applicable) ÷ payload bytes.*
Closing dedicated channels does not make embedding cheaper. It removes witness-discounted envelopes and bulk `OP_RETURN`, and forces data into hash and pubkey outputs that each pay a dust floor. At every fee rate in the table, hash and pubkey rows cost more per byte than `OP_RETURN` at 1,024 bytes.
Policy and fees still matter. Consensus can close high-bandwidth channels and reduce per-node storage load. Eliminating all non-monetary data would mean stripping payment properties Bitcoin needs. The realistic goal is to keep non-monetary use costly and unwelcome.
## VII. Implementation Path
The §III dedicated and unenforced caps are specified as one pre-proposal: *[Permanent Data Channel Closure](/bips/permanent-data-channel-closure)* (output templates, 83-byte OP_RETURN `scriptPubKey`, 256-byte item caps, aggregate witness limits, annex ban, control-block cap, Tapscript `OP_IF`/`OP_NOTIF` invalid, Tapleaf and P2WSH unreferenced-push analysis). Envelope closure is by invalidating `OP_IF` in Tapscript, not by a payload cap on skipped branches; Miniscript and taproot-channel HTLC leaves must split into separate leaves. Undefined witness versions cannot be created or spent; a future version is added by amending the template list in the same soft fork that defines spending. BIP141 weight is unchanged.
The per-output fee is *[Static Per-Output Miner Fee](/bips/static-per-output-miner-fee)*: a consensus floor on `tx_fee` of `static_fee × n_outputs`, paid as ordinary miner fee, not minted. *[Dynamic Escalation of the Per-Output Miner Fee](/bips/dynamic-escalation-per-output-fee)* is the optional anti-decay layer on top of that floor.
Consensus caps on dedicated embedding channels do not close every cheap field on the input side. Inputs still carry low-cost fields such as `nSequence`, `nLockTime`, and ordering. A permanent per-output creation cost closes those paths indirectly. Inputs spend outputs created earlier. If new outputs cost something to create under consensus rules, stuffing data into later spend fields still requires paying that creation cost up front. The floor does not ban input fields directly. It removes the incentive to mint cheap outputs just to encode data when they are spent. Dedicated-channel caps and a consensus per-output fee work together; they are not competing proposals. The three pre-proposals are meant to be considered as one stack. Separate activation is possible. The combined effect is stronger.
**UTXO commitments are an optional parallel layer.** Each §III embedding cap can soft-fork on its own. Commitments change how much set state a node must keep; they are not a prerequisite for the caps, and the caps are not a prerequisite for commitments. Outputs that would fail a new rule need grandfathering.
Policy tools (mempool filters, envelope detection, miner fee multipliers) stay useful but do not bind the network. A transaction that pays a willing miner still confirms. **Only consensus binds everyone.**
## VIII. Conclusion
Even if consensus could change without a political fight, **non-monetary data on chain cannot be eliminated entirely.** Payments still need hash addresses, flexible amounts, and auditable supply.
Data that never appears on chain, including Taproot script branches never revealed in a spend, is outside this analysis.
The §III caps belong in a formal spec. The [Bitcoin Commons consensus spec](https://thebitcoincommons.org/spec.html) is the reference. For why a human-readable specification matters as governance infrastructure, see *[Why Bitcoin Needs a Specification](/articles/why-bitcoin-needs-a-specification)*. For the dollar cost of leaving non-monetary data unpriced, see *[Full Cost of Running a Bitcoin Node](/articles/full-cost-of-running-a-bitcoin-node)*. The three-BIP stack that implements §III plus a UTXO-creation floor: *[Permanent Data Channel Closure](/bips/permanent-data-channel-closure)*, *[Static Per-Output Miner Fee](/bips/static-per-output-miner-fee)*, *[Dynamic Escalation of the Per-Output Miner Fee](/bips/dynamic-escalation-per-output-fee)*.
---
# Full Cost of Running a Bitcoin Node
*Methodology and Accounting · Version 2.4 · July 2026*
## Contents
- [I. Overview](#i-overview)
- [II. Representative Node Profiles](#ii-representative-node-profiles)
- [III. Cost Categories](#iii-cost-categories)
- [IV. Total Monthly Cost](#iv-total-monthly-cost)
- [V. Network-Level Aggregation](#v-network-level-aggregation)
- [VI. The Opportunity Cost of Node Density](#vi-the-opportunity-cost-of-node-density)
- [VII. Non-Monetary Data: Cost Distribution](#vii-non-monetary-data-cost-distribution)
- [VIII. Limitations](#viii-limitations)
- [IX. Sources](#ix-sources)
---
## I. Overview
Running a Bitcoin full node has six cost categories: hardware depreciation, bandwidth, power, learning time, ongoing maintenance, and opportunity cost of capital. Hardware alone is only a slice of the total. Operator time (setup plus upkeep) is usually the largest line item, though maintenance hours vary a lot and are shown as low / mid / high ranges.
This document defines each category, how it is estimated, the monthly and annual cost for one representative node, and the aggregate across the network. It also covers what lower node density costs everyone else: weaker security and worse performance when the node count falls.
Version 2.4 shifts the midpoint from a U.S. professional upper bound to a **median worldwide estimate**. Operator time uses a blended global median (~$30-40/hr in 2024-26), not U.S. BLS software-developer wages. The U.S. professional rate (~$75-78/hr) stays only as a high-end static scenario. Maintenance is still 1.0 hour/month at the midpoint for steady-state Profile A operators. After hobbyists, automation, and lower-wage regions, the worldwide median is likely lower still.
**Data.** Historical chain size, block size, and median transaction fees come from blockchain.info public chart APIs (year-end samples). Reachable-peer history comes from the KIT DSN Bitcoin Network Monitor. Hardware and RAM prices use retail series (storagediskprices.com, TrendForce, Stanford DAM, McCallum/jcmit). Electricity uses EIA U.S. residential averages as a hardware-power anchor. Operator hourly rates in the automated series use the worldwide median path; U.S. BLS rates appear only in high-end static scenarios. BTC opportunity uses CoinLore annual price averages.
---
## II. Representative Node Profiles
Aggregation needs clear point estimates. The document uses two profiles: a home operator and a VPS operator. VPS hosting does not remove cost. It rearranges it.
### Profile A: Home Operator (Primary)
A typical worldwide median operator is technically literate (comfortable with software, not a Bitcoin specialist), running a full archival node on a mini-PC with flat-rate or unmetered broadband where available. This sits in the middle: not a hobbyist who values time at zero, and not a high-diligence U.S. professional who manually verifies every release at full BLS wages.
Variance is large. Experienced hobbyists, operators in lower-wage regions, and heavily automated setups often report much lower effective cost than this midpoint. The model aims at a median for aggregation, not a ceiling.
Listening operators add relay capacity and eclipse resistance. Non-listening nodes validate locally but do not serve peers, so their ongoing bandwidth is lower. All per-node figures in the category sections use Profile A unless noted otherwise.
### Profile B: VPS Operator
A full archival node needs roughly 700-750GB storage as of mid-2026, 8GB RAM minimum, and adequate CPU. Entry-level $5-10/month VPS plans are not enough. A realistic archival setup is about 4 vCPU, 8-16GB RAM, and 800GB-1TB storage: roughly $30-50/month on Hetzner (EU), $40-80 on Vultr, $50-100 on DigitalOcean.
Home vs VPS (mid, monthly)
Home (Profile A, 2026)
Operating ~$70/mo automated
Hardware amortized once
~$960 hardware over 5 years
Same learning + maintenance
VPS (Hetzner mid)
~$84/mo ($40 sub + time)
Subscription has no endpoint
~$2,400 sub over 5 years
Same learning + maintenance
VPS saves upfront capital but costs more over five years. Hosting changes how you pay; it does not erase the bill.
---
## III. Cost Categories
### Category 1: Hardware Depreciation
The monthly cost of owning the hardware, spread over useful life.
**Storage.** A pruned node stores roughly 15-20GB after IBD; a full archival node stores ~700-750GB as of mid-2026. Pruning is a post-IBD state: every operator still downloads the full chain on first sync. Post-IBD growth runs ~70-90GB/year. At $200/TB NVMe, a replacement within five years adds roughly $3.33/month. Falling media prices (roughly 15-20%/year for consumer NVMe lately) offset some of the chain growth on this line.
**RAM.** Chainstate is ~7-12GB on disk. Minimum 8GB RAM reserved; 16GB recommended. At $20/GB over 5 years, 8GB reserved is ~$2.67/month.
**Compute.** Midpoint ~$350 for a competent home build, or ~$5.83/month over 5 years.
**Monthly hardware depreciation (full node, NVMe, including replacement):** about $13-18 at mid-2026 prose anchors; **$11.67/month** in the 2026 automated model.
### Category 2: Bandwidth
IBD is the same for pruned and archival operators (~690-740GB one-time). Ongoing listening relay commonly uses 150-400GB/month. For a representative operator on unlimited broadband, marginal cost is ~$5-15/month if the connection already exists, or $15-40 if it would not exist otherwise. Automated 2026 profile: **$10/month**.
### Category 3: Power
Raspberry Pi ~$1/month; mini-PC ~$5/month; desktop ~$12/month at ~$0.15-0.18/kWh EIA residential averages. Automated 2026 profile: **$4.58/month**.
### Category 4: Learning Cost (One-Time, Amortized)
Time to reach reliable first operation for a technically literate non-specialist: roughly 10-20 hours. Packaged products (Start9, Umbrel, RaspiBlitz) ease install work but do not remove networking, verification, or monitoring. They can raise effective cost when "turnkey" expectations meet real failure modes.
| Scenario | Hours | Rate | Amortized/mo |
|---|---|---|---|
| Low (experienced) | 8 | $35/hr | $5 |
| Mid (worldwide) | 15 | $35/hr | $9 |
| High (U.S. diligence) | 25 | $100/hr | $42 |
Automated 2026 profile: **$8.75/month**.
### Category 5: Ongoing Maintenance
Updates, verification, troubleshooting, monitoring. Midpoint **1.0 hour/month** at ~$35/hr worldwide median, or **$35/month**. High static scenario: 2 hours at $75/hr. Many steady-state operators with automation report 30-60 minutes/month or less.
### Category 6: Opportunity Cost of Capital
Capital locked in hardware instead of BTC. Static era bars use a fixed 20%/year on hardware value. The automated yearly series uses actual BTC year-over-year return on that year's hardware capital (floored at zero in down years). **Operating charts exclude opportunity** so bull-year spikes do not warp the operating trend. 2026 automated year-over-year opportunity is $0.
---
## IV. Total Monthly Cost
### Static snapshot (illustrative)
Rounded anchors for a new Profile A operator today. Mid uses worldwide median wages. High uses U.S. professional time rates. Do not compare these rows bit-for-bit to the automated 2026 profile ($69.99/mo operating).
Category
Low
Mid
High
Hardware
$13
$12
$18
Bandwidth
$5
$10
$40
Power
$1
$5
$12
Learning (amortized)
$5
$9
$42
Maintenance
$18
$35
$150
Opportunity (fixed 20%)
$8
$16
$25
Operating subtotal
$42
~$71
$262
All-in
$50
~$87
$287
Static anchors for intuition. Automated 2026 operating cost is $69.99/month.
### Automated 2026 operating composition
One listening node, operating cost (2026 automated)
MaintHWBWLearnPwr
Maintenance
$35.00
Hardware
$11.67
Bandwidth
$10.00
Learning
$8.75
Power
$4.58
Total
$69.99/mo
Operator time (learning + maintenance) is ~$44/month, larger than hardware, bandwidth, and power combined.
### Time-varying series (selected years)
Year
Hardware
Power
Learning
Maint.
Bandwidth
Operating
2012
$8.93
$6.07
$3.07
$11.50
$5.00
$34.57
2016
$11.23
$4.58
$4.17
$18.75
$8.00
$46.73
2020
$8.37
$3.36
$6.07
$24.50
$10.00
$52.29
2023
$7.07
$4.09
$8.25
$33.00
$10.00
$62.40
2026
$11.67
$4.58
$8.75
$35.00
$10.00
$69.99
Operating cost roughly doubled from 2012 to 2026 at worldwide median wages. Combined operator time exceeds hardware every year shown.
Era stacked comparison (fixed 20% opportunity on hardware, so the mix across eras is not warped by year-over-year returns):
| Era | Hardware | Operator time | Other operating | Opportunity (20%) | All-in |
|---|---|---|---|---|---|
| 2012 | $8.93 | $14.57 | $11.07 | $8.93 | $43.50 |
| 2018 | $9.63 | $25.65 | $12.76 | $9.63 | $57.67 |
| 2024 | $7.78 | $42.50 | $14.21 | $7.78 | $72.27 |
| 2026 | $11.67 | $43.75 | $14.58 | $11.67 | $81.66 |
Hardware-only estimates (~$6.80/month storage+RAM at mid-2026 media prices) leave out the dominant time categories. A non-signaling node costs **$64.99/month** operating in the 2026 automated model (lower relay bandwidth).
---
## V. Network-Level Aggregation
**Listening nodes** accept inbound connections and take part in relay. Bitnodes tracked roughly 15,000-20,000 through April 2026 (service offline May 2026). Aggregates use midpoint **17,500**. KIT DSN reachable-peer history uses a different method and is not directly comparable.
**Non-signaling full nodes** sit behind NAT or firewalls. Community estimates put total full nodes at roughly 2-3× the listening count, or ~45,000-80,000, midpoint **~60,000**. They enforce consensus but do not add relay capacity.
Annual operating cost vs Core development spend (2026)
Listening
$14.7M
Full pop.
$47.8M
Core dev
~$9M
Listening: $69.99/mo × 17,500. Full population: blended $66.45/mo × ~60,000. Core spend ~$9M (2025-26 public statements). Ratio is illustrative; a hobbyist-heavy population implies a lower effective aggregate.
Plausible bands: listening ~$8-30M/year; full population ~$25-80M/year. On an operating basis, node operators absorb several times Core development spend, with no formal governance stake and no payback when protocol decisions raise their costs.
---
## VI. The Opportunity Cost of Node Density
Individual operators bear the costs above. Density loss hits every Bitcoin holder.
**IBD propagation.** Fewer listening peers means slower sync for new operators, more abandonment, and further density loss. The feedback is uneven: cutting nodes from a thin network hurts more than adding nodes to a dense one helps.
**Eclipse surface.** Attack cost scales with the ratio of attacker-controlled peers to honest peers. Every listening node that exits because cost no longer makes sense makes eclipse attacks a bit cheaper for everyone left.
**Propagation redundancy.** Thinner networks push relay onto fewer well-connected supernodes. That is centralization at the relay layer even when validation stays formally decentralized.
Putting an exact dollar figure on security loss is out of scope. For scale: a 1% market-cap discount on a ~$2T asset is $20B, against ~$48M/year full-population operating cost in this model.
---
## VII. Non-Monetary Data: Cost Distribution
Every full node stores and downloads historical chain data whether or not the operator cares about non-monetary use. For the design case against treating Bitcoin as general-purpose storage, see *[Bitcoin Is Not a Hard Drive](/articles/bitcoin-not-a-hard-drive)*. For which embedding channels consensus can close, see *[The Achievable Floor](/articles/the-achievable-floor)*. The specified stack: *[Permanent Data Channel Closure](/bips/permanent-data-channel-closure)*, *[Static Per-Output Miner Fee](/bips/static-per-output-miner-fee)*, *[Dynamic Escalation of the Per-Output Miner Fee](/bips/dynamic-escalation-per-output-fee)*.
### UTXO set burden
Mempool Research (May 2025, tip 892385): **29.6%** of UTXOs are inscription-related (51,188,145 of 173,190,861), holding only 415.16 BTC total (mean 811 sats). Roughly 3.3GB of every node's ~11GB chainstate is inscription-related. Inscription UTXOs are spendable, so the share can fall if they are spent, but spent outputs stay in chain history and still load IBD.
UTXO set by count (May 2025)
29.6%70.4%
■ Inscription-related■ Other
### Chain storage burden
Baseline subtraction (pre-Ordinals ~435GB end-2022, organic ~50-60GB/yr vs actual growth to 700-750GB): non-monetary data is about **12-19%** of chain size, or **~85-140GB**. Fees from that activity went to miners. Node operators absorbed permanent storage and bandwidth.
### Ongoing per-node burden (automated)
Ongoing monthly non-monetary burden inside operating cost (storage depreciation + relay × flow-share + UTXO amortization; excludes operator time):
Year
Chain share
Flow share
UTXO share
NM $/mo
% of operating
2023
7.5%
30%
8%
$4.65
7.5%
2024
12.5%
38%
18%
$6.31
9.8%
2025
15.6%
32%
29.6%
$6.05
9.0%
2026
14.6%
28%
29.6%
$5.52
7.9%
2026 snapshot with fixed mid shares: $5.54/mo inside $69.99/mo (~$4.0M/yr across ~60,000 nodes).
One-time / cohort research estimates: $17-28 per node in storage capital for 85-140GB at $200/TB. Across 9,000-12,000 new nodes/year, collective inscription IBD bandwidth is about 765GB-1.68TB annually.
These figures motivate the three-BIP stack: consensus pricing of UTXO creation in *[Static Per-Output Miner Fee](/bips/static-per-output-miner-fee)* and *[Dynamic Escalation of the Per-Output Miner Fee](/bips/dynamic-escalation-per-output-fee)*, and closure of dedicated embedding channels in *[Permanent Data Channel Closure](/bips/permanent-data-channel-closure)*.
---
## VIII. Limitations
- **Medians, not ceilings.** Hobbyists, automation, and lower-wage regions often incur far less.
- **Time cost is high-variance and subjective.** Hours are self-reported; many operators would not treat imputed wages as a cash cost.
- **Infrastructure anchors are partly U.S./EU.** Metered international bandwidth can be higher; free hosting lower.
- **Node counts are uncertain.** Bitnodes went offline May 2026; the non-signaling multiplier is not directly measured.
- **Successful operators only.** Abandoned setups understate population learning cost.
- **Non-monetary value of running a node** (privacy, sovereignty, education) is not subtracted from expense.
- **Aggregates are order-of-magnitude** ($25-80M full-population band).
---
## IX. Sources
- blockchain.info chart APIs (chain size, fees)
- KIT DSN Bitcoin Network Monitor (reachable peers)
- storagediskprices.com / TrendForce / Stanford DAM / McCallum DRAM (media prices)
- EIA residential electricity averages
- CoinLore BTC annual averages
- Jameson Lopp node benchmarks (2023, 2025)
- Mempool Research UTXO Set Report, May 2025, tip 892385
- bitcoin.org full node documentation
- 1A1z report on Core funding (2023); Brink / Mike Schmidt public statements (2025-26 Core spend ~$9M)
- Blockspace Weekly / Galaxy / Mononaut fee-share commentary (2023-25)
- Hetzner / Vultr / DigitalOcean VPS pricing (mid-2026)
---
# Bitcoin Is Not a Hard Drive
## The Technical and Philosophical Case Against Non-Monetary Data Embedding
## Contents
- [I. What Bitcoin Actually Is](#i-what-bitcoin-actually-is)
- [II. The Type Confusion](#ii-the-type-confusion)
- [III. The Three Costs](#iii-the-three-costs)
- [IV. The Externality Structure](#iv-the-externality-structure)
- [V. Forced Participation](#v-forced-participation)
- [VI. The Justifications and Their Failures](#vi-the-justifications-and-their-failures)
- [VII. The Permissionless Counter-Argument](#vii-the-permissionless-counter-argument)
- [VIII. What Can Actually Be Done](#viii-what-can-actually-be-done)
- [Conclusion](#conclusion)
---
## I. What Bitcoin Actually Is
Bitcoin is a distributed consensus state transition ledger. Every node maintains an identical copy **not because storing data is valuable, but because reaching agreement about who owns what is valuable.**
The system was built for **one purpose: settling monetary transactions without a trusted third party.** To do that, every participant must maintain and validate the complete chain of prior state transitions. The integrity of the current state depends on the integrity of every state before it. That requirement is not optional infrastructure around the money. **It is the mechanism itself.**
**What Bitcoin can technically be made to carry** and **what Bitcoin was built to carry** are different things. That gap is the problem this document addresses.
---
## II. The Type Confusion
In software engineering, **type confusion** occurs when a value of one kind is passed to a context designed for something fundamentally different. The bytes are accepted, but the system was not built for them.
Bitcoin's transaction fields exist because payments require them. Hash fields exist for hash-then-reveal privacy, so a recipient can withhold a public key until spend time in case cryptographic assumptions weaken. Amount fields exist for satoshi precision. Sequence numbers and locktimes exist for transaction replacement and timelocked contracts. These fields are **not a general-purpose data bus with a monetary use case bolted on.** They are payment infrastructure that happens to be technically capable of carrying other things.
`OP_RETURN` was introduced as a controlled exit valve for provably unspendable outputs, ones that cannot be mistaken for monetary UTXOs and do not need to be tracked as potential future spends. Peter Todd proposed it on bitcoin-dev on 2013-02-12 as the honest unspendable marker. Jeff Garzik, on 2014-02-24, described the 0.9 change that made a small metadata output standard as damage control against MasterCoin-style unspendable outputs bloating the UTXO set. He rejected the reading that Core developers were endorsing data storage. Eighty bytes because hashes plus a tag. Luke Dashjr, on 2014-11-16, treated relay size as miner policy, not a Core development topic.
Consensus never capped the field. The current default is `MAX_OP_RETURN_RELAY = MAX_STANDARD_TX_WEIGHT / WITNESS_SCALE_FACTOR`, which is 100,000 vbytes, with `DEFAULT_ACCEPT_DATACARRIER` true. The original relay limit was friction that kept the channel aligned with its purpose, marking outputs as definitively unspendable without turning them into subsidized bulk storage.
The **Taproot envelope** is an `OP_FALSE OP_IF` branch that never executes. It was designed as an upgrade hook, not a data container. SegWit's witness discount exists because signature data, while necessary for validation, does not contribute to the UTXO set burden that every node must track indefinitely. Applying that discount to image files treats a targeted engineering accommodation as a general feature.
Using any of these fields to carry arbitrary non-monetary data is type confusion: the bytes are accepted, and the costs land on infrastructure built for something else.
The pattern is not unique to Bitcoin. A relational database is optimized for normalized, queryable data with defined relationships. Storing blob data in it anyway is technically possible, but indexing, querying, replication, and backup all absorb costs the schema was never built to handle. Early VoIP ran over TCP because TCP was available, not because it was appropriate. TCP's retransmission guarantee is a feature for file transfer and a liability for real-time audio, because a retransmitted packet arrives too late to play and the protocol has no way to discard it. Storing millions of small files in a filesystem built for a modest number of large ones causes inode exhaustion, directory traversal collapse, and backup failures. In each case the system accepts the input and the mismatch shows up as hidden costs across everything that depends on the layer below.
That is **impedance mismatch at the abstraction boundary.** Every layer assumes something about what the layer below will carry. Violating the assumption does not erase the mismatch; it spreads cost across every operation that touches that layer. Bitcoin is worse than most of these cases because the others allow migration. You can extract blob data from SQL, refactor trigger logic, move to UDP for media. **Bitcoin's chain history is immutable.** No later engineering decision undoes costs already imposed.
---
## III. The Three Costs
One megabyte of payment data and one megabyte of arbitrary data are not equal in network impact. They differ across three cost categories.
**Initial block download.** When a new participant joins the network, they download and validate the entire chain history from the genesis block forward. Every non-monetary payload ever embedded passes through that node's validation pipeline. **Spam does not become free once it is old.** It becomes a permanent toll on every future participant who wants to verify their own transactions.
Non-monetary data accounts for an estimated **12 to 19 percent** of total chain storage. Blockspace devoted to spam intensified roughly **17-fold** relative to its pre-inscription baseline. A node operator syncing today pays for all of it, permanently. For the full operator-cost model (including the ~$5.50/month non-monetary slice inside ~$70/month operating cost), see *[Full Cost of Running a Bitcoin Node](/articles/full-cost-of-running-a-bitcoin-node)*.
**Pruning does not escape this.** A pruned node still downloads and validates the full chain history during initial sync. What pruning removes is the ongoing storage obligation afterward, at the cost of surrendering the ability to re-verify the full chain from the node's own copy. A pruned node must trust an external node for that function, sacrificing sovereignty.
**Ongoing storage.** A full archival node stores the complete chain indefinitely. The chain currently requires approximately **700 gigabytes** of storage and grows with every block. Arbitrary data embedding inflates that number directly. Every non-monetary byte embedded today is a byte every archival node carries forever, with no recovery mechanism.
**UTXO set bloat.** The UTXO set is the live working set of all unspent transaction outputs. Every validating node holds it in fast storage to check whether incoming transactions are spending real outputs. Its size directly affects validation performance.
Payment UTXOs have economic agents who have reasons to spend them. When a payment output is spent, it leaves the UTXO set.
Inscription-related outputs represent approximately **29.6 percent** of all UTXOs while holding around **415 bitcoin** in total value. The ratio of monetary weight to chain footprint inverts completely compared to payment outputs. Almost no one has economic reason to spend them, so they accumulate in the UTXO set without cycling out, permanently occupying fast storage on every validating node on the network.
For measured blockspace impact and channel-by-channel cost tables, see *[The Achievable Floor, §VI](/articles/the-achievable-floor#vi-the-actual-floor)*.
---
## IV. The Externality Structure
These three cost categories share a common structure. **The person who embedded the data paid a fee once.** Miners were compensated at the moment of inclusion. **Every node operator pays** storage, bandwidth, and UTXO set costs for the entire remaining lifetime of the chain, with no compensation, no recovery path, and no relationship to the person who imposed the costs.
The fee mechanism does what it was designed to do: compensate miners for including transactions in blocks. It was **not designed to compensate node operators** for carrying those transactions indefinitely. That gap reflects the original design assumption that transactions would serve monetary purposes, and that monetary purposes would create economic agents with reasons to eventually resolve the state they created.
Arbitrary data embedding severs that relationship. The minting cost is paid once. The carrying cost is distributed permanently across everyone who validates the network, including everyone who joins later and had no role in the original decision. A transaction that imposes permanent costs on unpaid third parties with no recovery path is not paying its own way. **The fee covers inclusion, not the externality.**
---
## V. Forced Participation
The **"just don't run a node"** response misunderstands what nodes are for.
Bitcoin's security model depends on broad node participation. The properties that distinguish Bitcoin from a database someone else controls (verifying your own transactions, confirming your own balance, rejecting invalid blocks without trusting anyone) all require running a validating node. Custodial services and lite clients inherit their security from the nodes they trust. If the cost of running a node rises beyond what individuals can absorb, the validating population shrinks toward institutions and the network's decentralization degrades.
Policy filters and mempool settings do not resolve this. A transaction with sufficient fee reaches a miner regardless of whether other nodes will relay it. Direct submission APIs, alternative relay networks, and private pool peering all exist and are actively used. Once a transaction is in a valid block, every node must accept it. **Consensus validity is what binds.** A node operator's mempool policy is not a vote on what enters the chain. Participating in Bitcoin's security model means paying all the costs that consensus validity imposes, including those from arbitrary data embedding.
For the structural logic of why social enforcement cannot substitute for consensus closure here, see *[The Social Layer Is the Attack Surface](/articles/bitcoin-social-capture)* and *[Argument Map, Part VI](/articles/bitcoin-governance-argument-map#part-vi-forced-participation)*.
---
## VI. The Justifications and Their Failures
Five defenses recur. Each borrows a real property of Bitcoin and treats the use case as if it inherits that property, without pricing the cost imposed on the infrastructure those properties depend on.
**Immutability and censorship resistance.** The claim is that storing data on Bitcoin makes it permanent and uncensorable. Bitcoin's immutability was built to protect **one specific thing: the finality of monetary transactions.** It guarantees that a confirmed transfer of value cannot be reversed or erased. It was not built as a general archival service. Treating court-record reliability as a reason to store personal correspondence there makes the same mistake. A court is reliable for court records, not for every extra payload someone attaches. The attachment still costs everyone who needs the court for its job.
The same permanence guarantee is available without putting the data on Bitcoin. Arweave was designed for permanent, censorship-resistant storage with a one-time payment that funds retention. IPFS provides content-addressed storage identified by a cryptographic hash of the contents, so tampering is detectable without a central authority. The working pattern is to **store the data on IPFS or Arweave and commit only the content hash on chain**, anchoring provenance and timestamp. The data lives on infrastructure built to carry it. You get Bitcoin-anchored proof of existence without putting the file on Bitcoin.
**Fee payment as legitimacy.** The argument is that paying the fee makes any use legitimate and the market has spoken. Fees compensate miners at inclusion. They do not compensate node operators for the permanent costs above. The fee mechanism was calibrated for monetary transactions whose state has an economic lifecycle. Paying the inclusion fee for a use case that externalizes permanent costs onto unpaid third parties is **not the market pricing a service.** It is offloading costs the market price does not capture onto people who have no way to decline.
**Miner fee revenue and the security budget.** This is the strongest fee-market argument. Inscriptions generated substantial miner fee revenue, and as block rewards decline, fee revenue matters for security. But miner revenue and node operator participation run on **different timescales.** Miner revenue from inscription fees is real and immediate. Erosion of the node operator population from rising participation costs is also real, and it compounds over years. A network with high miner revenue and a shrinking validating population is not more secure. It is more dependent on trusting miners, which is the attack surface node decentralization exists to close. Paying one layer while shifting costs onto another does not improve the security model.
**Innovation and new users.** The argument is that inscriptions attract developers and communities who would otherwise ignore Bitcoin. People attracted by cheap data storage are not the same as people attracted by sound money, and they have no stake in node decentralization. Using Bitcoin as a data store is not innovative. Purpose-built decentralized storage (IPFS, Filecoin, Arweave) has been mature for years. Choosing Bitcoin instead is **a preference for subsidized infrastructure** over paying the real cost of what you want, with the subsidy taken from node operators who never agreed to provide it.
**The block weight limit as containment.** The claim is that Bitcoin's roughly four-million weight-unit block ceiling already proves spam is tolerable: damage has an upper bound, so the network has already contained it. The weight limit keeps **one block** within what a node can validate in finite time. It does not decide which uses of that scarce capacity belong in a monetary security model, and it does not pay node operators for the permanent stock of non-monetary bytes that accumulate under that rate.
A fire code that caps burn rate does not make arson acceptable. **Bounded rate is not the same as acceptable purpose.** The limit is the shared scarce resource payments need. Filling it with arbitrary data means the "upper bound on damage" is also an upper bound on monetary settlement capacity. That is the problem, not the defense.
The witness discount weakens the containment claim further: the same weight units admit more raw envelope payload than equivalent non-witness payment data, so the ceiling is asymmetrically generous to the dedicated spam channel. UTXO set bloat is not cured by a per-block byte ceiling either; outputs that never need to be spent stay in every node's fast storage indefinitely. For rate-versus-stock accounting, BIP141 asymmetry, and measured fullness, see *[The Achievable Floor, §VI](/articles/the-achievable-floor#vi-the-actual-floor)*.
---
## VII. The Permissionless Counter-Argument
The strongest objection is that Bitcoin is permissionless, and any mechanism that excludes a class of transactions is a step toward excluding any transaction. If the network can decide that JPEGs do not belong, it can decide that dissidents do not belong.
That collapses a distinction that matters. **Bitcoin's permissionless property applies to monetary transactions.** It means no authority can prevent you from sending value to another party. It does **not** mean Bitcoin is a neutral substrate for any purpose that can be technically encoded. Those are different claims.
The original `OP_RETURN` limit was not censorship of monetary transactions. It was friction that kept a non-payment channel from becoming a subsidized data bus at the expense of node operators who chose to validate monetary settlement. It was removed under documented pressure from actors with direct financial interest in using Bitcoin's infrastructure as cheap data storage. The governance outcome and the financial interests behind it are both matters of public record. For the full documented account, see *[Who Controls Bitcoin, §V](/articles/bitcoin-governance#v-the-adversarial-layer-when-conflicts-become-visible)*, the *[Argument Map, Parts VI–VII and XXII](/articles/bitcoin-governance-argument-map#part-vi-forced-participation)*, and *[What Bitcoin's Stalled Proposals Tell You](/articles/what-bitcoins-stalled-proposals-tell-you)* (policy monoculture section).
Treating every technical constraint as equivalent to political censorship makes it impossible to distinguish between a limit on arbitrary data embedding and a limit on sending bitcoin to a dissident. The permissionless property is meaningful precisely because it applies to something specific, and extending it to cover every possible use of every transaction field (compounding costs on every node that validates the network) degrades the very thing it claims to defend.
---
## VIII. What Can Actually Be Done
Arbitrary data cannot be reduced to zero. The fields that carry embedded data overlap with fields that payments require, and closing those fields would destroy payment functionality.
Hash fields carrying fake pubkeys or script hashes, amount fields encoding data in low-order bits, and sequence numbers and locktimes within valid ranges all resist consensus closure because the same fields serve legitimate payment functions. Distinguishing a real pubkey hash from a fake one at the consensus layer is not possible without stripping hash-then-reveal privacy from every payment.
What consensus **can** close are the **dedicated high-bandwidth channels:** `OP_RETURN` outputs with large payloads, and the Taproot envelope used as a bulk data container. These channels serve no monetary function, and closing them removes nothing that payments require. That closure is specified in *[Permanent Data Channel Closure](/bips/permanent-data-channel-closure)*.
Closing dedicated channels does not eliminate arbitrary data embedding. It forces embedders into hash and pubkey output fields that carry a dust floor on each output and cost more per embedded byte at every fee rate. The goal is making non-monetary use costly and unwelcome rather than subsidized by infrastructure built for something else. For the full technical breakdown of which channels consensus can close and where the floor actually sits, see *[The Achievable Floor](/articles/the-achievable-floor)*.
**UTXO commitments** address the historical storage burden. A node holding a root hash and verifying spends through inclusion proofs supplied by spenders does not need to carry the full UTXO set locally. The research has been complete since 2014. Every node that syncs today still pays the full cost of chain history that commitments would have capped a decade ago, and that cost grows with every new participant.
A **consensus-enforced per-output miner fee** addresses UTXO set bloat going forward. Two tools are easy to confuse. A minimum output value floor locks bitcoin in each output; that capital comes back when the output is spent, so a spammer can recycle it. A per-output miner fee is different: every newly created output pays a fixed fee to the miner, as ordinary transaction fee, that never comes back. That makes each spam run permanently more expensive, with no recycled capital to fund the next one. Inputs spend outputs created earlier, so if new outputs carry a permanent fee at consensus, stuffing data into later spend fields still requires paying that creation cost up front. Dedicated-channel caps and a per-output fee are complementary, and neither requires closing payment-necessary fields. See *[Static Per-Output Miner Fee](/bips/static-per-output-miner-fee)* and the optional anti-decay companion *[Dynamic Escalation of the Per-Output Miner Fee](/bips/dynamic-escalation-per-output-fee)*. The three pre-proposals are one stack: the fee BIPs price the UTXO slot; the data-channel BIP closes the bus.
---
## Conclusion
Bitcoin's value as a monetary network depends on the cost of running a validating node staying within reach of individuals. The moment that cost is accessible only to institutions, the security model becomes dependent on trusting those institutions, and the property that distinguishes Bitcoin from everything that came before it begins to dissolve.
Arbitrary data embedding raises that cost across three dimensions: **the one-time download every future participant pays at sync**, **the indefinite storage every archival node carries**, and **the permanent UTXO set burden every validating node holds in fast storage.** None of these costs are compensated by the fee that covered inclusion, and all of them fall on people who had no vote on whether the data belonged there.
Monkey JPEGs are beside the point. The question is whether the people running the infrastructure that makes Bitcoin work should subsidize other people's data storage, permanently and without exit, because payment fields can technically be made to carry other things.
**The externalities are not free.** Not every valid byte is equally aligned with the security model. Calling that neutrality is a choice about who pays.
**Bitcoin is not a hard drive.**
---
*Companion to [The Achievable Floor](/articles/the-achievable-floor) (channel taxonomy), [Full Cost of Running a Bitcoin Node](/articles/full-cost-of-running-a-bitcoin-node) (operator cost model), [Why Shitcoins Are Shitcoins](/articles/why-shitcoins-are-shitcoins) (altcoin monetary-asset case), [Who Controls Bitcoin](/articles/bitcoin-governance) (governance evidence), [Bitcoin Governance: Argument Map](/articles/bitcoin-governance-argument-map) (numbered arguments), and the three-BIP stack: [Permanent Data Channel Closure](/bips/permanent-data-channel-closure), [Static Per-Output Miner Fee](/bips/static-per-output-miner-fee), [Dynamic Escalation of the Per-Output Miner Fee](/bips/dynamic-escalation-per-output-fee).*
---
# Why Bitcoin Needs a Specification That Humans Can Read
## Verification methodology is not just a technical question but a governance question that will shape Bitcoin's resilience for decades.
## Contents
- [The Problem Bitcoin Has Been Avoiding](#the-problem-bitcoin-has-been-avoiding)
- [Three Responses to the Same Problem](#three-responses-to-the-same-problem)
- [Verification Is a Governance Problem](#verification-is-a-governance-problem)
- [Defense in Depth, Not a Silver Bullet](#defense-in-depth-not-a-silver-bullet)
- [The Timescale That Actually Matters](#the-timescale-that-actually-matters)
- [The Path We Are Taking](#the-path-we-are-taking)
---
## The Problem Bitcoin Has Been Avoiding
Bitcoin has been extraordinarily successful without a formal specification. But success does not make the absence of one sustainable.
The consensus rules that secure a multi-trillion-dollar network exist only as behavior encoded in Bitcoin Core's C++ codebase. **"The code is the spec" is not a design principle but an admission that no one has written the spec.** Every alternative implementation, every audit, every attempt to verify correctness must reverse-engineer undocumented behavior from a codebase that was never designed to be read as a specification.
Satoshi, after 0.1, said the core design was set in stone for the lifetime of the project. That stone is consensus design, not the application around it. In Bitcoin Core 32.1 the rules are 10,122 code lines and the rest of the implementation is 140,882. *[The Rules Are 7% of the Program](/articles/the-rules-are-7-percent)* is the count. Deploying the quote against P2P or privacy work is a category error on that reading. The case for a specification is the case for keeping the stone and the application apart.
This has worked so far because Bitcoin's growth in economic importance has outpaced the scrutiny that importance attracts. That is changing. When a court needs to understand whether a transaction was valid under the consensus rules at a given block height, there is no document to hand them. When a new implementation team wants to be sure they are building the same rules as Core, there is no specification to target. When an auditor wants to verify that a proposed soft fork does not break existing guarantees, there is no formal description of what those guarantees are.
The absence of a specification is not a minor gap. **It is the foundational vulnerability that every other correctness problem in Bitcoin builds on.**
The missing spec also keeps technical questions in the social layer indefinitely, and the noise degrades the signal from genuine threat detection. For why that noise-floor problem is an argument for a formal spec without asking Bitcoin to soften its adversarial register, see *[The Adversarial Default, §IV](/articles/the-adversarial-default#iv-the-inflation-problem)*.
## Three Responses to the Same Problem
Several serious efforts are underway to address this, and they deserve to be understood on their own terms.
The first is the human-readable mathematical specification approach, which is what Bitcoin Commons has built with the Orange Paper. The spec is written in standard mathematical notation, readable by any mathematician without knowledge of any programming language or proof assistant. The implementation is written separately in Rust and checked against it continuously. Neither artifact depends on the other to be understood. For how formal caps fit into a spec-first blockspace floor, see *[The Achievable Floor](/articles/the-achievable-floor)*.
The second uses Lean 4, a proof assistant, to build machine-checked guarantees. btc-verified, an independent project by Keagan McClelland, takes this approach: verified proof leaves on Bitcoin's byte layer, covering codecs, serialization, merkle, transaction ids, and chain linkage. The proofs verify mathematical properties and stop there. No running node, no generated code. A more ambitious variant would use proofs to generate the implementation itself through a compilation pipeline, though no project ships this at Bitcoin node scale today.
The third is the declarative DSL model taken by Hornet Node, developed by Toby Sharp. Hornet Node is a declarative C++ client written from scratch with no copied Core code, capable of syncing mainnet to tip in a few hours on a single thread. Its companion DSL is designed to eventually generate and validate implementation code, though that capability is still in development.
All three are good-faith responses to a real problem. The question is which foundation is best for Bitcoin over the timescales that actually matter.
## Verification Is a Governance Problem
This is the argument that changes the conclusion, and it is not being made anywhere else in this debate.
Bitcoin Core's governance problem is well understood in this community. Merge authority over the only implementation that the vast majority of economic nodes run is concentrated in a very small group of people. The problem is not that those people are bad engineers. **Concentrating consequential authority over Bitcoin in any small group, regardless of their competence or intentions, creates a single point of capture.** For the no-spec moat and why alternatives stay tethered to Core, see *[Who Controls Bitcoin, §VI](/articles/bitcoin-governance#vi-the-no-spec-moat-and-why-it-matters)*. For common defenses of the implementation monopoly that treat the code as sufficient specification, see *[Bitcoin Core: The Biggest Fallacies](/articles/bitcoin-core-the-biggest-fallacies)* (Fallacy 6).
**The choice of verification methodology is the same problem at a different layer.**
A verification approach that requires rare, specialized knowledge concentrates review authority in whoever holds that knowledge. If Bitcoin's correctness story depends on Lean proofs, its security model depends on a small population of people who can read and audit those proofs well enough to catch a subtle error in a consensus-critical theorem. That population is small, concentrated in academic communities, and not distributed across the independent institutions Bitcoin's long-term security requires. A custom DSL creates the same problem: the reviewer population is bounded by whoever understands the generator.
Standard mathematical notation is different in kind, not just in degree. It is not a tool requiring training in a specific software ecosystem but a communication medium that has been the universal language of precise formal reasoning for five hundred years, predating every programming language, every proof assistant, and every computer. Any mathematician with Bitcoin domain knowledge can read the Orange Paper and evaluate whether the stated rules are correct. That population is orders of magnitude larger, and it is stable across generations in a way that expertise in any specific tool cannot be.
**The choice of verification methodology is not just about which technique catches more bugs today.** It is about which approach maximizes the number of independent people who can meaningfully evaluate Bitcoin's rules over decades. Every verification layer that requires specialized tool knowledge narrows that population and concentrates authority. The Orange Paper widens it permanently.
Bitcoin Commons exists to dissolve implementation concentration. The same principle governs how we think about verification.
## Defense in Depth, Not a Silver Bullet
Framing this as a choice between human readability and formal rigor misses the point. The right answer is a stack.
Bitcoin Commons's verification approach has four layers. The Orange Paper is the normative reference: human-readable, tool-agnostic, auditable by any mathematician, targetable by any implementation team. The BLVM Specification Lock uses `Z3` to check on every merge that the Rust implementation still satisfies the mathematical contracts derived from the spec. Differential testing runs the implementation against Bitcoin Core across the full mainnet history. Those full-chain runs are operator-driven and resource-heavy. That is not a claim every CI job has zero-divergence proof to tip. Machine-checked proof leaves, following btc-verified's methodology, strengthen the byte layer where formal methods are most tractable today and will expand upward as tools mature.
The Specification Lock deserves particular attention because it solves the code generation problem without introducing one of its own.
In a code generation system, the generator is the authoritative artifact. The implementation is derived from it. When something is wrong in the generated code, the fix travels through the generator first. A change to the generator can produce unexpected effects anywhere in its output. Every DSL and proof extraction pipeline has encountered edge cases the generator does not handle. The resolution is always the same: fix the generator, regenerate, verify again. The debugging surface is not the code but the thing that made the code.
The Specification Lock inverts this. **The implementation is the authoritative artifact.** The Specification Lock reads the implementation against the specification rather than producing the implementation from it. When a check fails, the developer fixes whichever side is wrong, directly, without touching a generator. Nothing is regenerated. The Orange Paper can be read without the implementation. The implementation can be audited without the Orange Paper. The Specification Lock is the enforced relationship between them, not the thing that produces either one.
This is how every durable technical standard works. TCP/IP, TLS, POSIX, and the C standard are human-readable specifications implemented independently by teams who never needed to run the specification as code.
## The Timescale That Actually Matters
Bitcoin is infrastructure that must survive institutional and generational turnover. This changes which trade-offs matter.
In the nearer 50 to 100 year window, the question is whether a verification approach can be maintained across the institutional change Bitcoin governance will require. Lean 4 is fifteen years old and actively evolving. Proofs written today require active maintenance as the toolchain develops. A DSL compiler is additional software with its own maintenance burden. Mathematical notation requires no such maintenance. It does not depend on any software remaining operational or any organization remaining funded.
Over longer horizons, the durability gap widens. Legislators, regulators, central banks, and courts will increasingly need to understand what Bitcoin's consensus rules actually are. They will not hire Lean experts. They will hire mathematicians and lawyers who can read a specification written in standard notation. The institutional audiences that will govern Bitcoin's relationship with human society for decades are already reachable through the Orange Paper in a way they are not through any proof assistant.
This is not an argument against formal methods. Machine-checked proofs provide guarantees that empirical testing cannot. The Orange Paper provides the human-legible normative foundation that proofs cannot replace. Differential testing grounds the whole stack in real chain history. Each layer does what the others cannot. The argument is for being deliberate about which layer carries which burden.
## The Path We Are Taking
Bitcoin Commons is not claiming to have solved this problem. The Orange Paper is a first formal specification of Bitcoin consensus, not the last word on it. Specification Lock coverage will expand. Formal proof leaves on the byte layer are being incorporated. The differential testing program will continue to grow. Cryptographic merge authorization is designed and stays off until security review, key management, and community validation.
What we are claiming is that the foundation matters, and that getting it right is the prerequisite for everything else. Implementation diversity on the same chain means multiple independent implementations, built by different teams in different languages, each developed against the same specification, each auditable by the same population of mathematicians, none of them the sole source of the rules. The rules stay legible to the engineers, regulators, and institutions that will need them, without requiring specialist intermediaries.
That is what implementation diversity actually requires. **Not a better single implementation, but a specification that outlives every implementation built against it.** Building that specification is what Bitcoin Commons is doing, and we think it is the most important work in Bitcoin right now.
---
## Sources
- [Orange Paper / Bitcoin Commons consensus spec](https://thebitcoincommons.org/spec.html)
- [Bitcoin Core repository](https://github.com/bitcoin/bitcoin)
*Related: [Who Controls Bitcoin](/articles/bitcoin-governance), [The Vertical Layer Problem](/articles/the-vertical-layer-problem), [Making Core Irrelevant](/articles/making-core-irrelevant), [The Achievable Floor](/articles/the-achievable-floor), [Bitcoin Governance: Argument Map](/articles/bitcoin-governance-argument-map), [Permanent Data Channel Closure](/bips/permanent-data-channel-closure).*
---
# The Coordination Gap
## Bitcoin solved block consensus. Node software is still written by informal agreement.
## Contents
- [Two kinds of consensus](#two-kinds-of-consensus)
- [The wars that informal process could not settle](#the-wars-that-informal-process-could-not-settle)
- [Why the same structure reconstructs](#why-the-same-structure-reconstructs)
- [One public attempt](#one-public-attempt)
- [Sources](#sources)
---
Bitcoin solved agreement among strangers about which chain is valid. A bad block dies at every node that checks it. The people who write the software that performs that check still coordinate in mailing lists, chat, and a GitHub merge queue. That gap is the subject of this article. It is not a claim that Bitcoin's money rules failed, and it is not a pitch to leave Bitcoin for a new coin. Same chain, same 21 million, same proof of work.
In March 2014 Gavin Andresen stood at Princeton and named both layers. Technical consensus was hard, and Satoshi had shipped it. Social consensus, the human work of deciding how the software that enforces those rules gets written, was also hard, and nobody had solved it. Twelve days later he stepped down as lead maintainer. The talk is *[Who Controls Bitcoin](/articles/bitcoin-governance)*'s search frame. The durable outcome of the fight that followed is *[Governance Paralysis Was The Victory](/articles/governance-paralysis-was-the-victory)*. Why informal process reconstructs a hierarchy even when the occupants change is *[The Vertical Layer Problem](/articles/the-vertical-layer-problem)*.
---
## Two kinds of consensus
Protocol consensus is the set of validation rules every node enforces: subsidy, proof of work, script, block structure. No maintainer can change those rules by merging a pull request. The network either takes a new rule or it does not. Shipping a release is not rewriting those rules. The people who write the default still govern what new operators download.
Social coordination is who may merge, who may stall, and how a fight about the software is settled. Consensus-adjacent work sits between those layers. It does not rewrite the money rules, and it still requires coordinated adoption across developers, miners, and economic nodes. A security patch that operators must take is in that middle.
A wallet fight that ships in the default node is in that middle because the money rules and the extras share a binary. Treating that fight as a change to the 21 million cap is the miss.
Core is one implementation. Bitcoin is the protocol. A second client that validates the same rules, talks to the same peers, and accepts the same blocks is still Bitcoin. Age does not decide that. Compatibility does. The longer write-up of why the social layer can be taken over without rewriting consensus is *[The Social Layer Is the Attack Surface](/articles/bitcoin-social-capture)*.
---
## The wars that informal process could not settle
Gavin had already named the 1 MB block limit as a consensus change he knew would be hard. The blocksize war consumed the years after he left. SegWit activated. Bitcoin Cash left, taking a ticker split with it. Mike Hearn quit and called Bitcoin failed. Exchanges halted deposits while the fight was live. The small-block position protected something real: full nodes stay cheap enough to run. The cost was that the war used the window when a second independently specified client was still tractable, and the process for settling the next fight did not get built. That is *[Governance Paralysis Was The Victory](/articles/governance-paralysis-was-the-victory)*.
Taproot did ship. It is the usual reply to the claim that this ecosystem cannot activate anything. Taproot was not the lead maintainer disappearing, and it was not a fight on the scale of the blocksize war. Multiple activation methods, Speedy Trial among them, still had to be socially coordinated under a much larger market cap. That it activated says a smaller disagreement can still clear. It does not say informal merge authority can design a succession process after the people in charge are gone.
The later fight was already on the chain. Ordinals used Taproot's unused envelope plus SegWit's witness discount as a file store. Ready proposals to close dedicated non-money channels stalled. Bitcoin Core v30 removed the default relay limit on `OP_RETURN`. Operators switched to Knots in volume for different policy defaults, and they were still running Core's lineage. Demand showed up. A second independently specified client did not. That record is *[The Adversarial Default](/articles/the-adversarial-default)* and *[Making Core Irrelevant](/articles/making-core-irrelevant)*.
Each of those rounds raised the cost of the next one while the coordination process stayed informal.
---
## Why the same structure reconstructs
About five people hold merge access on [bitcoin/bitcoin](https://github.com/bitcoin/bitcoin). Release trust still runs through identifiable keys. Review is real. Merge authority is not spread the way review is. The numbers are in *[Who Controls Bitcoin](/articles/bitcoin-governance)* and [Bitcoin Governance Research](https://github.com/secsovereign/bitcoin-governance-research).
Formalizing that process from inside the same seats is the thing the seats were not built to do. The current arrangement is fast for the people who already merge. Users treat the default client as the network. There is no published rule for who may merge, and no venue whose decision both sides accept short of a chain-fork threat. Path dependence is not a moral verdict on today's maintainers. It is why swapping the cohort rebuilds the same hierarchy. *[The Vertical Layer Problem](/articles/the-vertical-layer-problem)* is that shape diagnosis.
A single implementation lineage makes the software layer easier to pressure, because there is one menu most economic nodes download. Forking the chain to escape that menu splits the money. Forking governance against a written specification, if one existed, would not. That distinction is the rest of this catalog.
---
## One public attempt
Bitcoin Commons is a from-scratch Rust client aimed at the same chain and the same consensus rules, built from the [Orange Paper](https://thebitcoincommons.org/spec.html), a human-readable mathematical specification, not a new coin and not a ticker split. The case for a specification that humans can read is *[Why Bitcoin Needs a Specification](/articles/why-bitcoin-needs-a-specification)*.
Full-chain differential replay against Bitcoin Core is the scale test. `blvm-bench` targets on the order of 900,000 blocks. Those runs are operator-driven and resource-heavy. That is not a claim every CI job has zero-divergence proof to tip. Methodology lives in the [differential testing guide](https://docs.thebitcoincommons.org/development/differential-testing.html). Cryptographic merge authorization is designed and stays off until security review, key management, and community validation. The Specification Lock checks annotated implementation paths against the spec. It does not replace a written specification, and it is not governance enforcement.
Cheap exit on the same chain is what makes informal merge authority fail as a trap. A client that can be checked against a spec can be forked without reverse-engineering Core. A governance ruleset that can be exported without splitting the ledger is a different operation from Bitcoin Cash. None of that is a claim that the money already runs on those tools.
The diagnosis of the monopoly and the no-spec moat is *[Who Controls Bitcoin](/articles/bitcoin-governance)*. What has to happen, in what order, is *[Making Core Irrelevant](/articles/making-core-irrelevant)*.
---
## Sources
- [Gavin Andresen, "Consensus is Hard," Princeton, March 27, 2014](https://www.youtube.com/watch?v=YH5cFWWtUJE)
- [Bitcoin Governance Research](https://github.com/secsovereign/bitcoin-governance-research)
- [Orange Paper / Bitcoin Commons consensus spec](https://thebitcoincommons.org/spec.html)
- [Differential testing guide](https://docs.thebitcoincommons.org/development/differential-testing.html)
- [bitcoin/bitcoin](https://github.com/bitcoin/bitcoin)
*Related: [The Social Layer Is the Attack Surface](/articles/bitcoin-social-capture), [Who Controls Bitcoin](/articles/bitcoin-governance), [Governance Paralysis Was The Victory](/articles/governance-paralysis-was-the-victory), [Why Bitcoin Needs a Specification](/articles/why-bitcoin-needs-a-specification).*
---
# Don't Trust, Verify
## Coldcard, Credentialed Endorsement, and the Gap Between Source and Audit
## Contents
- [I. Three Errors That Compounded](#i-three-errors-that-compounded)
- [II. How the Stack Built](#ii-how-the-stack-built)
- [III. The Review That Missed](#iii-the-review-that-missed)
- [IV. The Capital Layer](#iv-the-capital-layer)
- [V. What Verification Would Have Required](#v-what-verification-would-have-required)
- [VI. The Same System, Applied to Bitcoin Core](#vi-the-same-system-applied-to-bitcoin-core)
- [VII. What Changes](#vii-what-changes)
---
The Bitcoin community has a handful of commandments. "Not your keys, not your coins." "Run your own node." "Don't trust, verify." Of these, **"don't trust, verify" is the one most directly about process.** It is repeated so often it has become the phrase that signals you are serious about Bitcoin, not just holding it.
Coldcard appropriated that commandment as a brand identity. "Don't Trust. Verify." was printed on the tamper-evident bag the device ships in. It was displayed on the device screen in Coinkite marketing copy. The four pillars on the Coinkite storefront: Bitcoin Only, Verifiable Source Code, Easy-to-use, Ultra-Secure. The tagline beneath the product: "Air-gapped signing options. Verifiable firmware." Reproducible builds. WalletScrutiny badge. **The entire commercial presentation was built around the idea that you don't have to trust Coinkite because you can verify everything yourself.** Verifiability was presented as the product.
Coldcard never commissioned an independent third-party security audit of its seed generation path. Not once across its entire commercial life. From March 2021 onward, Coldcard firmware was silently routing seed generation through a weak software PRNG instead of the hardware TRNG. The code was available. **The verification that Coinkite was marketing as its core proposition was absent from the most important property the device had.**
It has cost their audiences **$88 million** so far, and that number is still growing.
---
## I. Three Errors That Compounded
The first error was **treating source-available as audited.** Coldcard's firmware was publicly readable under a restrictive license, not open source in any meaningful sense. The code could be read but not freely forked, redistributed, or built on commercially. Those are the conditions that generate active external scrutiny. **Source availability without that culture is not a security property.**
The second error was **treating workflow security as seed security.** Coldcard's post-seed security model is genuinely strong: dual secure elements, air-gapped PSBT signing, duress PINs, BIP-85. The promoters who evaluated these things evaluated them accurately. What nobody traced was the path from "user taps generate seed" to **which entropy source actually runs.** In retrospect this seems like the most elementary question you could ask about a device whose only job is to generate a secret. A seed that looks correct but was generated from insufficient entropy is not a secure seed. **Evaluating everything except whether the entropy was sound is like testing a safe by checking the paint.**
The third error was **treating social capital as technical verification.** When Adam Back calls something "super high assurance," the implied claim is that someone with standing to evaluate hardware security has evaluated it. When a Bitcoin Core contributor builds tooling that treats Coldcard as the only supported device, the implied claim is that the device passed whatever scrutiny a Core contributor would apply. When Unchained Capital integrates it and calls Coinkite "big fans," the implied claim is that institutional due diligence was performed. **None of those implied claims were verified about the seed generation path.**
For why reputation and credentialing substitute for verification in Bitcoin's development layer, see *[The Social Layer Is the Attack Surface](/articles/bitcoin-social-capture)*.
---
## II. How the Stack Built
The promotion didn't start with podcasters. **It started with tooling.**
HWI, the official Bitcoin Core-adjacent hardware wallet interface project, provides first-class Coldcard support via a dedicated module maintained by Ava Chow, a Bitcoin Core maintainer. Her own demo at London Bitcoin Devs in 2020: "I am going to be using a Coldcard because that is the easiest thing to do." James O'Beirne, Bitcoin Core contributor and author of OP_VAULT, built coldcore, a wallet tool whose README states Coldcard is "the only wallet supported at the moment because it is opensource, and supports air-gapped use via PSBT." O'Beirne's own framing reflects the community's conflation of source-available with open source. Craig Raw's Sparrow Wallet documentation includes a dedicated "Why Coldcard?" section recommending Coldcard directly.
A user following the most technically serious Bitcoin self-custody path, running their own node, using Bitcoin Core, following the tooling documentation, **arrived at Coldcard without encountering a single advertisement.** The default was structural, not simply marketing.
Then the educators confirmed what the tooling assumed. Then the institutions integrated what the educators confirmed. Then the vendor cited the institutions on the homepage. Coinkite's website stacked WalletScrutiny's "passed all 10 tests" badge next to BTC Sessions calling it "one of the most secure Bitcoin hardware wallets ever built" next to Bitcoin Verdict calling it "the most secure you can buy." **Each layer appears to have treated the layer below as diligence.** None of the layers included a seed-path audit.
From March 2021 onward, Coldcard was generating seeds from a far smaller entropy pool than anyone knew. Every influencer recommendation, every tutorial, every podcast episode, every institutional integration produced after that date was built on top of a device that had already failed the most fundamental test.
By July 2026, "Coldcard" and "most secure Bitcoin hardware wallet" were near-synonymous in serious self-custody discourse. **Disclosed sponsorship did not stop recommendations from functioning as trust signals.** "Don't trust, verify" had become trust the people who say "don't trust, verify."
---
## III. The Review That Missed
The sharpest illustration is PortlandHODL's June 2022 public review.
Bitcoin Core contributor, AnchorWatch engineer. He publicly examined the Mk4's STM32 RNG driver and published his conclusion: "Looking through the source of the COLDCARD MK4 their driver implementation for the STM32 rng is correct."
He was right. The driver was correct. **The bug wasn't in the driver.**
The defect was in the build-time preprocessor guard in a different file, the guard that determined whether the driver was called at all. When `MICROPY_HW_ENABLE_RNG` is defined as zero (which it always was), the `#ifndef` check passes, the error never triggers, and seed generation falls through to MicroPython's Yasmarang software PRNG seeded from the chip's serial number and clock registers. The driver PortlandHODL reviewed was fine. **It just wasn't running.**
A credentialed Bitcoin Core contributor performed visible technical work. The community had reason to trust that work. The work stopped at the wrong file. The community's trust remained, and so did the vulnerability, for four more years.
**This is the third error in practice.** "Don't trust, verify" requires verifying the right thing. It is not satisfied by verifying something adjacent to the right thing and then extending trust to cover the gap.
---
## IV. The Capital Layer
Ten31 led Coinkite's Series A in December 2024. Its managing partners, Matt Odell and Marty Bent, were already two of the most prominent Coldcard promoters in Bitcoin. **By the time they held equity, they had spent years recommending a wallet whose firmware was vulnerable.** The Series A added equity to a sponsorship relationship they had already been disclosing in public.
Rabbit Hole Recap, the weekly podcast co-hosted by Odell and Bent, routinely listed Coinkite in its standard sponsor block ("Shoutout to our sponsors: Coinkite") in published show notes, documented from at least July 2023 through July 2026. Odell's setup guide was listed directly on Coldcard's official documentation page, one of three educators whose guides Coinkite itself endorsed. Citadel Dispatch, Odell's separate audience-funded podcast, carried the Ten31 investment disclosure in the show notes of an episode featuring NVK. **The financial relationship was not hidden.** What was missing was not disclosure but verification: none of that sponsor or investment context included, or substituted for, an independent audit of the seed generation path.
**The "don't trust, verify" standard applies to incentives as much as it applies to code.** Disclosing a sponsorship or equity stake satisfies transparency about conflicts. It does not satisfy the verify step. An audience told to check the firmware could still treat a disclosed sponsor's recommendation as evidence the device had been scrutinized, when the scrutiny that mattered never happened.
One more data point on how thoroughly Coldcard's reputation was constructed: Zach Herbert, CEO of Foundation Devices and maker of Coldcard's closest competitor, published an open letter to NVK calling Coldcard "the most secure Bitcoin hardware wallet with the best security architecture..." A hardware wallet company CEO endorsing a competitor as the best in the market is about as strong a third-party validation as exists.
The irony runs deeper than that. Herbert built Foundation Devices' Passport on a fork of Coldcard's then-GPLv3 firmware, which was legally permitted under that license. GPL requires that anyone who forks and distributes must release their modifications under the same terms. NVK saw a competitor using his code exactly as the license allowed, publicly said he regretted releasing under GPL, and then Coinkite migrated to MIT plus Commons Clause. The Commons Clause addition is specifically designed to prevent commercial use, which is what Foundation Devices had done legally. The new license left the code source-visible but no longer open source by any standard definition. Coinkite began calling it "verifiable" rather than open source. Herbert and others publicly criticized the change.
The large 120-file commit that executed the license migration also rewrote the seed generation path. That rewrite is where the defective preprocessor guard was introduced. **The same period that produced the most credentialed endorsement Coldcard ever received also produced the code change that, five years later, allowed attackers to drain over $88 million from addresses likely tied to innocent Coldcard customers.**
---
## V. What Verification Would Have Required
This is not a story about a sophisticated cryptographic attack or an exotic vulnerability class. **The defect was a configuration error.** Three files, one call chain.
An auditor asking "which entropy source actually runs when a user generates a seed?" would have read `shared/seed.py` to find the `generate_seed()` call, traced `ngu.random.bytes()` to the libngu guard in `external/libngu/ngu/random.c`, and checked the board configuration in `stm32/COLDCARD/mpconfigboard.h` where `MICROPY_HW_ENABLE_RNG` is set to zero. The guard uses `#ifndef`, which passes when the macro is defined to any value including zero. The hardware TRNG path is silently disabled. The fallback runs.
Findable. Not found by anyone in five years. **Found by an attacker, in the same public repository that the community had been citing as a reason to trust the device.**
---
## VI. The Same System, Applied to Bitcoin Core
Here is the uncomfortable part.
Bitcoin Core was first released in January 2009. Its first independent third-party security audit was completed in September 2025, **sixteen years later**, and it was partial. In those sixteen years, the review process that was supposed to substitute for independent audit produced three notable visible failures.
An inflation bug was introduced in Bitcoin Core 0.14.0 in March 2017 as a performance optimization that skipped a block validation check considered redundant. The skipped check was not redundant. The bug allowed a miner to inflate Bitcoin's supply by spending the same inputs twice. It sat in production through multiple reviewed releases for roughly eighteen months before a developer outside Bitcoin Core discovered and disclosed it. It was never exploited on mainnet, but **the inflation bug in the software designed to enforce Bitcoin's 21 million cap passed review repeatedly before anyone found it.**
Bitcoin Core 30.0, shipped in late 2025, contained a wallet migration bug that under specific conditions deleted all wallet files in the user's wallet directory, with no recovery path if backups didn't exist. The dangerous code pattern, using `fs::remove_all()` on user wallet directories, was introduced in 2022 and self-merged by Ava Chow. The PR itself received substantial review, but the specific lines containing the dangerous pattern received essentially none. In 2024, maintainer ryanofsky explicitly identified the exact risk in a code review, writing that the pattern "could wipe out a lot of other data," and recommended a followup PR to fix it. No followup was created. In 2025, an unrelated PR changed backup locations in a way that removed an earlier failure point that had been accidentally preventing the dangerous code from executing. The bug could now run. Users lost wallets. The fix arrived 18 days after the bug report. **A maintainer had named the precise failure mode a year earlier, recommended fixing it, and the warning was not acted on.**
Bitcoin Core 31.0, released April 2026, introduced a `-privatebroadcast` feature whose release notes stated explicitly: "Their IP address (and thus geolocation) is never known to the recipients." When the BIP324 v2 encrypted handshake failed, the software silently fell back to an unencrypted v1 retry that bypassed the Tor proxy entirely, exposing the sender's real IP address to the receiving peer. A malicious peer could deliberately trigger the handshake failure to force the exposure. The bug was disclosed June 6, 2026, six weeks after the feature shipped. It was fixed in 31.1.
Three failures, each defined by the gap between what the feature was supposed to do and what it actually did. A 21 million cap that could be increased. Wallets that got deleted. A private broadcast feature that wasn't private. **All three are the same class of failure as the Coldcard RNG defect:** a code path that ran when it shouldn't have, or didn't run when it should have, visible in the source, not caught by review. For why irreversible stakes and named-but-unfixed failures make a soft culture the wrong prescription, see *[The Adversarial Default, §III](/articles/the-adversarial-default#iii-why-the-stakes-justify-the-register)*.
When the first independent audit finally arrived in September 2025, Quarkslab spent 100 man-days across three engineers over four months. The scope was limited to the P2P layer, mempool, block validation, and chain state. The published scope covered a minority of consensus-critical code paths, and libbitcoinkernel was explicitly excluded. The program those paths sit in is measured in *[The Rules Are 7% of the Program](/articles/the-rules-are-7-percent)*: 10,122 code lines decide validity, 20,366 apply them or choose what to relay, and 120,516 are the rest of the implementation. secp256k1, bundled beside that, is another 76,503.
Many of the people who built Coldcard's reputation are the same people whose judgment you are supposed to trust on Bitcoin Core: **source availability treated as audit, contributor reputation treated as verification, institutional consensus treated as correctness.** Whether that mechanism has failed elsewhere is precisely the question that the "don't trust, verify" standard requires you to ask, and that social capital alone cannot answer. For refutations of judging Core on "technical merits alone" without a formal spec, see *[Bitcoin Core: The Biggest Fallacies](/articles/bitcoin-core-the-biggest-fallacies)* (Fallacy 6). For the funding map, merge concentration, and documented adversarial cases in Core governance, see *[Who Controls Bitcoin](/articles/bitcoin-governance)*.
---
## VII. What Changes
The failures documented here are structural. **They will happen again anywhere reputation replaces verification.** The community preached a standard and didn't apply it to the things it trusted most.
The commandment is real. **The question is whether the community actually lives by it or just says it.**
---
## Sources
- [Galaxy Research on Coldcard losses (via The Block)](https://www.theblock.co/post/410533/coldcard-hack-130-million-galaxy-research) — on-chain loss estimates cited in this article
- [Coinkite, "Technical Deep Dive into the Entropy Issue"](https://blog.coinkite.com/technical-deep-dive-into-the-entropy-issue/) — firmware root cause
- [Quarkslab, "Bitcoin Core Security Audit"](https://blog.quarkslab.com/bitcoin-core-audit.html) — September 2025 P2P/mempool scope
*Related: [The Social Layer Is the Attack Surface](/articles/bitcoin-social-capture), [Who Controls Bitcoin](/articles/bitcoin-governance), [Bitcoin Core: The Biggest Fallacies](/articles/bitcoin-core-the-biggest-fallacies), [The Rules Are 7% of the Program](/articles/the-rules-are-7-percent).*
*This article is analytical commentary based on publicly available information. All factual claims are sourced from public records, public statements, and documented on-chain data. No malice or prior knowledge of the defect is attributed to any individual named. Dollar figures and victim counts reflect published on-chain estimates (e.g. [Galaxy Research](https://www.theblock.co/post/410533/coldcard-hack-130-million-galaxy-research)), not confirmed victim reports.*
---
# Why Shitcoins Are Shitcoins
*A research report on the structural failures of altcoins as monetary assets*
## Contents
- [I. Introduction](#i-introduction)
- [II. Security](#ii-security)
- [III. Rules Without Enforcement Are Gibberish](#iii-rules-without-enforcement-are-gibberish)
- [IV. Decentralization: Potential vs. Reality](#iv-decentralization-potential-vs-reality)
- [V. Monetary Policy Credibility](#v-monetary-policy-credibility)
- [VI. The Founder Problem](#vi-the-founder-problem)
- [VII. Securities Risk](#vii-securities-risk)
- [VIII. The Price Record](#viii-the-price-record)
- [IX. Bitcoin Dominance as the Macro Signal](#ix-bitcoin-dominance-as-the-macro-signal)
- [X. The Lindy Effect and Network Effects](#x-the-lindy-effect-and-network-effects)
- [XI. On Smart Contracts and the Blockchain Problem](#xi-on-smart-contracts-and-the-blockchain-problem)
- [XII. Conclusion](#xii-conclusion)
- [Sources](#sources)
---
## I. Introduction
Thousands of alternative cryptocurrencies have been launched since Bitcoin. Almost none have survived as meaningful stores of value. Seventeen years and multiple market cycles have produced the same outcome often enough that the failure pattern looks structural, not like a collection of one-off post-mortems.
Altcoins fail as monetary assets. Launching a new chain does not replicate Bitcoin's properties. Founder intent and design polish do not change that. Activity on a smart-contract platform or a stablecoin rail is not money. Whether that activity needs its own consensus layer is taken up at the end. The argument throughout is the monetary asset case.
Interesting technology is not the test. The test is whether the rules have held up under real adversarial pressure, not whether they were described as decentralizable on paper.
---
## II. Security
Bitcoin's security rests on its accumulated hashrate, representing billions of dollars of capital investment in specialized SHA-256d hardware deployed over seventeen years. [MIT Digital Currency Initiative](https://www.dci.mit.edu/projects/51-percent-attacks) monitoring and industry estimates put the capital cost of acquiring enough SHA-256 hashrate to attack Bitcoin in the tens of billions of dollars, with only a tiny fraction of that hashrate ever available on rental markets. No credible 51% attack has ever been mounted against the Bitcoin base chain.
A new proof-of-work chain starting from scratch has none of that. The cost to attack it is a fraction of the cost to attack Bitcoin.
Altcoins with thin hashrate get attacked. In January 2019, [Coinbase documented](https://www.coinbase.com/blog/coinbases-perspective-on-the-recent-ethereum-classic-etc-double-spend) fifteen deep reorganizations on Ethereum Classic, twelve of which included double spends totaling 219,500 ETC (~$1.1 million at the time). ETC was hit again in August 2020, when separate attacks [double-spent roughly 807,000 ETC (~$5.6 million) and 238,000 ETC (~$1.7 million)](https://www.coindesk.com/markets/2020/08/07/ethereum-classic-attacker-successfully-double-spends-168m-in-second-attack-report) using hashrate rented from NiceHash. Bitcoin Gold, whose stated purpose was restoring mining decentralization, suffered [~$18 million in double-spend losses](https://www.zdnet.com/article/bitcoin-gold-hit-with-double-spend-attacks-18-million-lost/) across May 2018. Verge suffered [two mining attacks in April and May 2018](https://www.coindesk.com/markets/2018/06/05/verges-blockchain-attacks-are-worth-a-sober-second-look) that exploited timestamp bugs to mint millions of XVG at artificially low difficulty. The second attack alone was estimated at roughly $1.7 million. As of August 2026, XVG trades [more than 99% below its December 2017 all-time high](https://www.coingecko.com/en/coins/verge) and has never meaningfully recovered. For many smaller tokens, the hashrate needed for a 51% attack is available for rent on NiceHash at a cost below the profit from a successful double-spend. The MIT DCI has documented that pattern across dozens of PoW altcoins.
A chain can accumulate hashrate over time, but most never do. The point is not that every new chain gets attacked, but that it remains attackable in a way Bitcoin is not, and that gap degrades the security model whether or not an exploit ever lands.
Proof-of-stake is a different, still weaker, model. Hashrate is sunk hardware. Stake can be withdrawn, slashed, or concentrated by whoever can pay. Ethereum's age and staked ETH do not close that gap. Its social contract has already proved negotiable; the [2016 DAO fork](https://blog.ethereum.org/2016/07/20/hard-fork-completed/) is taken up in §XI.
---
## III. Rules Without Enforcement Are Gibberish
A blockchain's entire value proposition rests on one claim: the rules are enforced without a trusted administrator. Remove that claim and you have an inefficient distributed database.
§II is the mechanism. If a rented majority can rewrite history, the rules are suggestions. That is not trustless. It is anonymous administration without recourse. A permissioned database at least names the administrators.
---
## IV. Decentralization: Potential vs. Reality
A system can be designed to be decentralizable without actually being decentralized, and the gap between those two things is where almost every altcoin spends its entire existence.
Bitcoin's decentralization is not something you read off a diagram. It survived the blocksize war, the SegWit activation fight, multiple nation-state mining bans, and repeated attempts by well-funded actors to redirect its development. Each of those fights hardened the social consensus around Bitcoin's rules. Bitcoin's reference-client governance is concentrated. That is a separate problem from the one addressed here.
A new chain's founding community is typically ideologically homogeneous, assembled around a shared narrative or grievance.
Decentralization metrics often count nodes or validators and miss who actually controls the network. On Ethereum, liquid staking protocols, exchange-operated staking, and foundation treasuries cluster influence in ways headline dashboards hide. [Lido's share of staked ETH fell from roughly 32% in 2023 to near 24% by 2026](https://www.coindesk.com/tech/2025/08/14/figment-outpaces-rivals-in-ether-staking-growth-lido-s-decline-eases-dominance-concerns) after sustained community pressure. The drop took a political campaign, and a quarter of stake is still a cluster. Named foundations holding large token treasuries add another administrative layer. Those entities can vote on rules that directly affect the supply they control. That is a founding coalition that agrees with itself, not a network that had to settle a fight.
---
## V. Monetary Policy Credibility
Bitcoin's 21 million supply cap has never been changed. SegWit and Taproot did not touch it and did not reverse settled history. That is not a code comment. It is a rule a large, economically incentivized network refused to reopen.
Most altcoins announce a similar policy, then issue into it. Low float and large unlocks let insiders distribute into liquidity. Continuous issuance on most L1s, and repeated inflation-schedule changes on chains like Solana, mean holders depend on ongoing demand to absorb new supply. Ethereum's issuance model has changed several times, including the post-merge shift to burn-linked issuance. That is a governance decision. Stated intentions are not sound money.
---
## VI. The Founder Problem
Almost every altcoin was founded by an identifiable person or small group. Ethereum has Vitalik Buterin. Solana has Anatoly Yakovenko. Regulators, institutions, and the community treat that person as the decision-maker. When they exit, pivot, or fight the community, the chain inherits the mess. That has played out dozens of times.
Bitcoin's founder disappeared. No one speaks for Satoshi. The rules are not an ongoing personal preference.
---
## VII. Securities Risk
Almost every altcoin token was issued through an ICO, presale, foundation allocation, or founder reserve. In each case, investors bought an asset expecting profit from someone else's work. That is the core of the [Howey test](https://www.law.cornell.edu/supremecourt/text/328/293): an investment of money in a common enterprise, with a reasonable expectation of profits from the efforts of others. Most altcoins fail it in ways Bitcoin does not. The SEC has pursued [dozens of enforcement actions](https://www.sec.gov/newsroom/press-releases/2025-75) against unregistered token offerings; federal courts have applied Howey transaction-by-transaction rather than treating crypto assets as a single category ([*SEC v. Coinbase*](https://www.sec.gov/litigation/litreleases/lr-25829), 2024).
Bitcoin was never sold in a presale. There was no ICO, no foundation allocation, no founder's reserve. Coins entered circulation only through mining, available to anyone willing to contribute hashrate from day one. In March 2025, the SEC staff [explicitly distinguished](https://www.sec.gov/newsroom/speeches-statements/statement-certain-proof-work-mining-activities-032025) proof-of-work mining from investment-contract offerings, noting that miners earn rewards from computational work rather than passive reliance on a promoter’s managerial efforts.
Regulatory liability does not have to materialize for this to matter. The existence of securities exposure creates uncertainty for exchanges, institutional holders, and downstream applications that Bitcoin does not carry. That uncertainty is priced in even when regulators have not yet acted.
---
## VIII. The Price Record
[CoinGecko's dead-coins study](https://www.coingecko.com/research/publications/how-many-cryptocurrencies-failed) found that 53.2% of all cryptocurrencies listed on GeckoTerminal between July 2021 and December 2025 are no longer actively traded. In 2025 alone, 11.6 million tokens went inactive after recording at least one trade. That accounted for 86.3% of all failures in that five-year window. Minted-but-never-traded projects were excluded. The fourth quarter of 2025 saw 7.7 million failures, concentrated after the [October 10 liquidation cascade](https://www.coindesk.com/markets/2026/01/14/more-than-half-of-all-crypto-tokens-have-failed-and-most-died-in-2025) that wiped out roughly $19 billion in leveraged positions in twenty-four hours. The figure includes many tiny, abandoned, or spam projects, but the direction is clear. The overwhelming majority of crypto projects fail.
Across the more established end of the market, cycle-to-cycle survivorship screens put the share of altcoins that fail to reclaim a prior cycle high above 80%. [MEXC analysis of prior cycle tops](https://blog.mexc.com/crypto-knowledge/the-cycle-highs-and-cycle-lows-creator-redfista/) found roughly 20% of cryptocurrencies hit a new all-time high from one cycle to the next, implying 80% did not. [TradingKey](https://www.tradingkey.com/analysis/cryptocurrencies/more/262073712-crypto-altcoin-eth-bnb-sol-xrp-ada-link-dash-tradingkey) cites similar token-survivorship data across major cycles. As of mid-2026, CryptoQuant analyst Darkfost's "altcoins near ATL" screen tracks tokens trading below 25% of their all-time high. It [put the figure near 40%](https://coinmarketcap.com/academy/article/38percent-of-altcoins-near-all-time-lows-worse-than-ftx-says-cryptoquant), briefly climbing toward 45% when Bitcoin fell below $60,000 in June 2026. These are snapshot figures. Treat them as directionally consistent rather than precise. They hold across multiple data sources and multiple cycles.
A few large-caps printed a later-cycle high in dollar terms. That is not matching Bitcoin's path across cycles. None have. [ETH/BTC peaked near 0.148 in June 2017](https://www.cfbenchmarks.com/blog/the-eth-btc-ratio-through-time), reached roughly 0.087 in November 2021, and traded near 0.027 by mid-2026. Each cycle high in Bitcoin terms was lower than the last, even when ETH printed a later dollar high. Outside that small set, dollar recovery from one cycle high to the next is rare.
---
## IX. Bitcoin Dominance as the Macro Signal
[Bitcoin dominance](https://coinmarketcap.com/charts/bitcoin-dominance/), the share of total crypto market capitalization held by Bitcoin, has ranged from [94% in April 2013](https://www.lambdafin.com/articles/bitcoin-dominance-history) down to [~33% at the peak of ICO mania in January 2018](https://academy.binance.com/en/articles/a-brief-history-of-bitcoin-dominance). It has since recovered to the [56-58% range in 2026](https://www.lambdafin.com/articles/bitcoin-dominance-history). Every altcoin narrative cycle plays out the same way. ICOs, DeFi summer, NFTs, L1 fee wars, AI agents. Dominance falls as capital rotates out, then recovers when the narrative dies.
The institutional stack now being built around crypto concentrates around Bitcoin. U.S. spot Bitcoin ETFs [absorbed a record $18.7 billion in net inflows in Q1 2026 alone](https://blocklr.com/news/bitcoin-etf-performance-q1-2026/). Cumulative net inflows since the January 2024 launch exceeded $65 billion by mid-2026. Ethereum spot ETFs launched in July 2024, but cumulative institutional flows have remained far below Bitcoin's. The wrapper does not erase ICO-era distribution or the monetary-policy problems described above. [CoinShares 13F analysis](https://coinshares.com/insights/research-data/13f-filings-of-bitcoin-etfs-q3-2025-institutional-report/) found registered investment advisors accounting for 57% of institutional Bitcoin ETF holdings. Average reported portfolio allocations were still below 1% of AUM, leaving substantial room for further inflows that have historically favored Bitcoin over altcoin baskets. Sovereign treasuries hold Bitcoin, not altcoin baskets. The [U.S. Strategic Bitcoin Reserve](https://bitcoinreservetracker.org/) holds roughly 328,000 BTC from forfeitures. El Salvador (~7,700 BTC) and Bhutan (~3,100 BTC) are among the few nation-states with verifiable on-chain holdings.
---
## X. The Lindy Effect and Network Effects
Every year Bitcoin survives, the credible commitment that it will continue to survive strengthens. Nassim Taleb called that the Lindy effect: the longer something has survived, the longer it is likely to keep surviving. Derivatives depth, global exchange books, and custody rails sit on that same clock. They were built on the chain that already had liquidity. They do not transfer to a new ticker.
---
## XI. On Smart Contracts and the Blockchain Problem
The standard defense is that these chains serve other purposes: smart contracts, dapps, programmable money, tokenized assets, stablecoin rails. Stablecoin transfer volume on Ethereum, Solana, and Base is dollar volume on someone else's ledger. USDC is the issuer's liability. The chain is transport. You do not need to own ETH or SOL as money to move it, any more than SWIFT messages require you to own the bank software they ride on.
Speed and low fees are database properties. They do not justify a separate consensus layer with its own token. Most of those workloads want named administrators who can fix bugs, reverse errors, and be sued.
The DAO hack is the trade-off in public. When a smart contract vulnerability [drained roughly 3.6 million ETH (~$60 million at the time)](https://www.coindesk.com/markets/2016/06/17/the-dao-attacked-code-issue-leads-to-60-million-ether-theft) from The DAO in June 2016, Ethereum [executed a hard fork at block 1,920,000](https://blog.ethereum.org/2016/07/20/hard-fork-completed/) to reverse the theft. That is what a system with administrators does. The administrators operated through social consensus rather than legal authority.
Trustless computation among mutually distrusting parties is a real problem. Atomic composability and global ordering are cheaper inside one consensus domain today. That is convenience, not a reason to mint money. Zero-knowledge proofs, multi-party computation, validity proofs, and Bitcoin-anchored execution keep separating the computation problem from the consensus problem.
The non-monetary jobs that actually hold up are short: timestamping, proof of publication, existence proofs, settlement finality, credible neutrality in adversarial coordination. They point at anchoring to Bitcoin. [OpenTimestamps](https://opentimestamps.org/) already does this without a second token. For why a chain is a bad hard drive, see *[Bitcoin Is Not a Hard Drive](/articles/bitcoin-not-a-hard-drive)*. For which embedding channels consensus can shut, see *[The Achievable Floor](/articles/the-achievable-floor)*.
---
## XII. Conclusion
The properties that make Bitcoin Bitcoin are not features in a codebase. No alternative chain has them at launch. Most blockchain applications do not need a new monetary layer. They need named administrators, or an anchor to Bitcoin. Money is the one use case that cannot hand that choice to someone else. Bitcoin is the one chain that never did.
*Related: [The Last Uncaptured Asset](/articles/the-last-uncaptured-asset), [Bitcoin Is Not a Hard Drive](/articles/bitcoin-not-a-hard-drive), [The Achievable Floor](/articles/the-achievable-floor), [Who Controls Bitcoin](/articles/bitcoin-governance).*
## Sources
Research compiled August 2026.
**Security and 51% attacks**
- [MIT Digital Currency Initiative — 51% Attacks project](https://www.dci.mit.edu/projects/51-percent-attacks)
- [Coinbase — Ethereum Classic double-spend incidents (January 2019)](https://www.coinbase.com/blog/coinbases-perspective-on-the-recent-ethereum-classic-etc-double-spend)
- [CoinDesk — ETC second 51% attack, August 2020](https://www.coindesk.com/markets/2020/08/07/ethereum-classic-attacker-successfully-double-spends-168m-in-second-attack-report)
- [Bitquery — ETC July 2020 attack analysis](https://bitquery.io/blog/attacker-stole-807k-etc-in-ethereum-classic-51-attack)
- [ZDNet — Bitcoin Gold double-spend attacks, May 2018](https://www.zdnet.com/article/bitcoin-gold-hit-with-double-spend-attacks-18-million-lost/)
- [CoinDesk — Verge blockchain attacks, 2018](https://www.coindesk.com/markets/2018/06/05/verges-blockchain-attacks-are-worth-a-sober-second-look)
- [CoinGecko — Verge (XVG) price and ATH data](https://www.coingecko.com/en/coins/verge)
**Token failure and altcoin performance**
- [CoinGecko — Dead coins: How many cryptocurrencies have failed?](https://www.coingecko.com/research/publications/how-many-cryptocurrencies-failed)
- [CoinDesk — More than half of all crypto tokens have failed (January 2026)](https://www.coindesk.com/markets/2026/01/14/more-than-half-of-all-crypto-tokens-have-failed-and-most-died-in-2025)
- [MEXC — The Cycle Highs And Cycle Lows (Redfist)](https://blog.mexc.com/crypto-knowledge/the-cycle-highs-and-cycle-lows-creator-redfista/)
- [TradingKey — Why 80% of Altcoins Never Reclaim Their Highs](https://www.tradingkey.com/analysis/cryptocurrencies/more/262073712-crypto-altcoin-eth-bnb-sol-xrp-ada-link-dash-tradingkey)
- [CoinMarketCap Academy — CryptoQuant altcoins near ATL screen (Darkfost)](https://coinmarketcap.com/academy/article/38percent-of-altcoins-near-all-time-lows-worse-than-ftx-says-cryptoquant)
- [CF Benchmarks — The ETH/BTC ratio through time](https://www.cfbenchmarks.com/blog/the-eth-btc-ratio-through-time)
**Bitcoin dominance and institutional flows**
- [Lambda Finance — Bitcoin Dominance History (2013–2026)](https://www.lambdafin.com/articles/bitcoin-dominance-history)
- [CoinMarketCap — Bitcoin Dominance chart](https://coinmarketcap.com/charts/bitcoin-dominance/)
- [Binance Academy — A Brief History of Bitcoin Dominance](https://academy.binance.com/en/articles/a-brief-history-of-bitcoin-dominance)
- [BlockLR — Bitcoin ETF Performance Q1 2026](https://blocklr.com/news/bitcoin-etf-performance-q1-2026/)
- [CoinShares — 13F Bitcoin ETF institutional report, Q3 2025](https://coinshares.com/insights/research-data/13f-filings-of-bitcoin-etfs-q3-2025-institutional-report/)
- [Bitcoin Reserve Tracker — sovereign holdings](https://bitcoinreservetracker.org/)
- [WealthManagement.com — RIA crypto ETF exposure](https://www.wealthmanagement.com/crypto/ria-s-show-low-exposure-to-the-latest-crypto-crash)
**Securities regulation**
- [SEC v. W.J. Howey Co., 328 U.S. 293 (1946)](https://www.law.cornell.edu/supremecourt/text/328/293)
- [SEC — Statement on Certain Proof-of-Work Mining Activities (March 2025)](https://www.sec.gov/newsroom/speeches-statements/statement-certain-proof-work-mining-activities-032025)
- [SEC — Unicoin offering fraud charges (2025)](https://www.sec.gov/newsroom/press-releases/2025-75)
**Ethereum governance**
- [CoinDesk — The DAO attacked (June 2016)](https://www.coindesk.com/markets/2016/06/17/the-dao-attacked-code-issue-leads-to-60-million-ether-theft)
- [Ethereum Foundation — Hard Fork Completed (July 2016)](https://blog.ethereum.org/2016/07/20/hard-fork-completed/)
- [CoinDesk — Lido staking share and validator concentration (August 2025)](https://www.coindesk.com/tech/2025/08/14/figment-outpaces-rivals-in-ether-staking-growth-lido-s-decline-eases-dominance-concerns)
**Bitcoin-anchored utilities**
- [OpenTimestamps](https://opentimestamps.org/)
---
# The Adversarial Default
## A Defense of Toxic Maximalism
## Contents
- [I. What Being Collaborative Actually Produced](#i-what-being-collaborative-actually-produced)
- [II. What a Softened Culture Costs on the Outside](#ii-what-a-softened-culture-costs-on-the-outside)
- [III. Why Bitcoin Needs This Tone](#iii-why-bitcoin-needs-this-tone)
- [IV. Two Things Called Toxic](#iv-two-things-called-toxic)
- [V. The Fight Is Not Over](#v-the-fight-is-not-over)
- [Sources](#sources)
---
The complaint arrives on schedule. Bitcoin culture is toxic. The maximalists drive away talent. Be nicer. Extend good faith. Grow up.
This article defends the hostile stance, not every insult and not every pile-on. Some of that is noise. **The hostility is mostly correct.** It matches the threat. People asking Bitcoin to soften have not faced what the hostility is defending against.
---
## I. What Being Collaborative Actually Produced
Constructive optimism was already tried. Years of good-faith work inside the process came before the blocksize war and before the OP_RETURN fight. In both cases, people working inside the process lost without ever losing the argument.
The blocksize war did not start because maximalists woke up one morning and decided to be difficult. It followed years of engagement with a process that was capturable, and that was used that way. Developers who raised concerns about one dominant codebase, who pays the developers, and who gets to approve code changes were not rewarded for honesty. They were pushed to the margins. Their proposed changes were closed. Their concerns were reframed as attacks on the project.
Taproot sailed through on broad agreement. The fight was mostly about how to turn it on, not whether the rules themselves were a good idea. Soft review treated that as a win. Hard review of what the new surfaces could become was thin.
Taproot removed the old 10,000-byte script ceiling. Together with SegWit's existing witness discount, that made large arbitrary data payloads practical, without real accounting for the cost that would land on every validating node. The Taproot envelope (an `OP_FALSE OP_IF` branch that never runs) was meant as an upgrade hook, not a file store. Ordinals and inscriptions used it anyway. JPEGs and token junk went into the chain. Non-money data is now an estimated 12 to 19 percent of total chain storage. Spam blockspace ran roughly 17 times its pre-inscription baseline. About 29.6 percent of UTXOs are inscription-related while holding only around 415 bitcoin. Every validating node pays for that forever.
The OP_RETURN fight in 2025 ran after that abuse was already real. Ready proposals to close dedicated ways of stuffing non-money data into blocks stalled. Core v30 removed the limit on how much `OP_RETURN` data nodes would forward. The stronger technical case did not win. A small set of funded people with power over Bitcoin Core treated doing nothing on those protections as the default, and treated social pressure as a stand-in for technical debate.
That is the record the hostility is responding to.
---
## II. What a Softened Culture Costs on the Outside
Bitcoin maximalists call scams early and loudly, in exactly the tone critics say Bitcoin needs to drop. In most cases they are right. Ordinary investors who heard those warnings had often been trained to discount the people making them.
[MIT Sloan](https://mitsloan.mit.edu/cfi/anatomy-a-run-terra-luna-crash) estimates the Terra ecosystem collapsed in three days in May 2022 and wiped out about $50 billion in value. Reporting at the time put the Terra/Luna wipe near $45 billion overnight. FTX took customer deposits trusted to an exchange whose founder [Fortune had put on its cover](https://fortune.com/2022/08/01/ftx-crypto-sam-bankman-fried-interview/) as a possible "next Warren Buffett," then went bankrupt in November 2022. The [SEC](https://www.sec.gov/news/press-release/2022-219) later charged that customer funds had been diverted to Alameda without disclosure. Celsius, Voyager, and BlockFi followed the same pattern at smaller scales. The [Chicago Fed](https://www.chicagofed.org/publications/chicago-fed-letter/2023/479) documents withdrawal freezes and bankruptcies across those platforms, with hundreds of thousands of customers owed in each filing.
**The hard stance is a warning system.** When it is loud and consistent, it is harder to run a project that borrows Bitcoin's credibility. When it softens, the warning gets weaker, and ordinary investors pay. Destroyed savings and retirement funds are not abstract. After Terra, reporting documented people describing total loss and mental-health crisis, including thoughts of suicide on public forums ([Time](https://time.com/6177567/terra-ust-crash-crypto/); [Al Jazeera](https://www.aljazeera.com/economy/2022/5/20/after-terra-crash-investors-and-regulators-count-cost-of-crypto)). Those costs fall on people who never asked for a friendlier culture.
The same pattern shows up when famous names replace checking the work. That is *[Don't Trust, Verify](/articles/dont-trust-verify)*.
---
## III. Why Bitcoin Needs This Tone
Bitcoin is hard to undo at scale. By the time bugs surface, the damage is often already done.
Bitcoin Core 30.0 and 30.1 had a wallet migration bug that, under specific conditions, could delete all files in the wallet directory when migration of an unnamed legacy `wallet.dat` failed, with no recovery if backups did not exist. Bitcoin Core's own [advisory](https://bitcoincore.org/en/2026/01/05/wallet-migration-bug/) states the risk of fund loss and pulled the affected downloads. The dangerous `fs::remove_all` pattern had been introduced years earlier. In 2024, Core maintainer ryanofsky named the exact risk in code review and recommended a follow-up fix. No follow-up was created. A later change removed an earlier accidental stop that had been blocking the dangerous path. Users lost wallets. The fix landed in [PR #34156](https://github.com/bitcoin/bitcoin/pull/34156) after the bug was reported ([issue #34128](https://github.com/bitcoin/bitcoin/issues/34128)).
CVE-2018-17144 makes the same point for the money rules themselves. An inflation bug that could have created Bitcoin out of thin air sat in the live software for roughly eighteen months before disclosure. Bitcoin Core's [September 20, 2018 notice](https://bitcoincore.org/en/2018/09/20/notice/) documents it. Neither bug was a clever attack. The wallet risk was named a year early and still shipped. The inflation bug sat unused. No mined block used the hole, so a second node program checking the same chain would have agreed with Core. Finding it took someone reading the code, not two clients disagreeing on live blocks. Other clients existed on paper. A fork of Core inherits the bugs it still copies. Genuinely separate clients hold almost no node share, so neither functions as a real check. Almost everyone ran Core.
Being wrong in Bitcoin costs more than being wrong in most other engineering work. Harsh public pressure on proposed changes, including upgrades that look uncontested, is a rational response. The other option is a nicer culture that is also a more dangerous one.
---
## IV. Two Things Called Toxic
Two different things get called toxic maximalism. Only one of them is a problem Bitcoin should try to fix with manners.
Pointing at frauds that trade on Bitcoin's credibility is a permanent job. There is no other defense against a scam whose main asset is proximity to Bitcoin. That part is not going away, and it should not.
The fighting inside Bitcoin is the part that can shrink. A large share of it exists only because the tools that would end an argument do not.
Bitcoin Core has never produced a clear mathematical write-up of the rules every node must enforce. Seventeen years of capable, well-funded developers on software that secures trillions of dollars, and the network still has no adopted specification. There is nothing the network treats as solid to test an implementation against, and nothing adopted to appeal to when people disagree about what the protocol permits. So fights about what Bitcoin is stay in arguments and reputation instead of settling in code.
Everything also ships as one package. There is no clean way to accept part of a release and reject another part without forking the whole program. That is why a disagreement about any single change becomes a fight about the entire project. The wallet is bundled into the node for the same reason a policy dispute becomes a governance crisis. Separating wallet from node has been recognized as an improvement for over a decade and still sits undone.
Write the specification and split the wallet from the node, and what remains is disagreement about tradeoffs and threat models. That is what people should be fighting about. Ask for civility without building either, and you are asking people to stop paying attention.
---
## V. The Fight Is Not Over
People asking Bitcoin to soften are implying the threat has passed: that governance is mature enough now, and that the hostility is leftover from an earlier, riskier period Bitcoin has outgrown.
None of that is true.
Almost everyone still runs one line of software. Economic nodes run Bitcoin Core or a Core-derived fork that stays on Bitcoin. In 2025 Knots showed that operators will switch over what transactions a node forwards. The Core-derived forks that stay are still that switch, not a separately written program that decides the money rules on its own. No separately written Bitcoin software, proven to follow the same money rules, has enough of the network running it to matter.
Who pays for Core development is still concentrated. A small number of grant organizations, with documented ties to companies and funds that care about protocol outcomes, still pay most Bitcoin Core development. Who merges code is still concentrated too. Brink's [Engineering Impact Report 2025](https://brink.dev/blog/2026/03/26/engineering-impact-report-2025/) shows one person at one organization merged 56% of all changes to Bitcoin Core in calendar year 2025. [Bitcoin Governance Research](https://github.com/secsovereign/bitcoin-governance-research) shows the same shape in the 2022+ window of 5,747 PRs: 50.2% of merges from the top account, 82.2% from the top three. The right to merge into Bitcoin Core is still a small fixed set, currently five people on [bitcoin/bitcoin](https://github.com/bitcoin/bitcoin). A subpoena, a regulatory order, or a quiet conversation with that set can still move a protocol change the rest of the network can do little about.
None of the conditions that made the hard culture appropriate have gone away. The trauma that produced it was real. The threat is ongoing. There is still no specification the network has adopted. There is still no separately written second Bitcoin client with meaningful node share. Forks of Core that only change what they forward do not close that gap.
**The hard stance is Bitcoin's immune system.** It matches a threat that has not gone away. Asking for civility without the specification and without splitting the wallet from the node is asking the patient to drop the fever before the infection clears. The fever is doing work. Leave it alone until the structure changes. Then we can talk.
---
*Related: [Who Controls Bitcoin](/articles/bitcoin-governance), [The Social Layer Is the Attack Surface](/articles/bitcoin-social-capture), [Why Bitcoin Needs a Specification](/articles/why-bitcoin-needs-a-specification).*
---
## Sources
- [Liu, Makarov, and Schoar, "Anatomy of a Run: The Terra Luna Crash," MIT Sloan CFI](https://mitsloan.mit.edu/cfi/anatomy-a-run-terra-luna-crash). Terra ecosystem collapse in three days, ~$50B valuation wiped
- [Al Jazeera, "After Terra, Luna crashes, regulators count cost of crypto"](https://www.aljazeera.com/economy/2022/5/20/after-terra-crash-investors-and-regulators-count-cost-of-crypto), May 20, 2022. ~$45B Terra/Luna erase; retail savings wiped
- [Time, "What Terra's Crash Means For Crypto and Beyond"](https://time.com/6177567/terra-ust-crash-crypto/), May 2022. Retail losses; public forum reports of suicidal ideation after the crash
- [Fortune, "30-year-old billionaire Sam Bankman-Fried… next Warren Buffett"](https://fortune.com/2022/08/01/ftx-crypto-sam-bankman-fried-interview/), August 1, 2022. Pre-collapse magazine celebration
- [SEC press release 2022-219](https://www.sec.gov/news/press-release/2022-219), December 13, 2022. Charges that FTX customer funds were diverted to Alameda
- [Chicago Fed Letter No. 479, "A Retrospective on the Crypto Runs of 2022"](https://www.chicagofed.org/publications/chicago-fed-letter/2023/479). Celsius, Voyager, BlockFi, FTX withdrawal pauses, bankruptcies, customer counts
- [Bitcoin Core, "Wallet Migration Failure May Delete Unrelated Wallet Files"](https://bitcoincore.org/en/2026/01/05/wallet-migration-bug/), January 5, 2026. Official advisory for Core 30.0 / 30.1
- [bitcoin/bitcoin#34128](https://github.com/bitcoin/bitcoin/issues/34128). Wallet migration deletion bug report
- [bitcoin/bitcoin#34156](https://github.com/bitcoin/bitcoin/pull/34156). Fix removing `fs::remove_all` cleanup
- [Bitcoin Core notice, CVE-2018-17144](https://bitcoincore.org/en/2018/09/20/notice/), September 20, 2018. Inflation bug disclosure
- [Brink Engineering Impact Report 2025](https://brink.dev/blog/2026/03/26/engineering-impact-report-2025/), March 26, 2026. 56% merge concentration
- [Bitcoin Governance Research](https://github.com/secsovereign/bitcoin-governance-research). Merge concentration, stalled proposals, conflict-resolution findings
---
# Making Core Irrelevant
## What has to happen, and in what order
## Contents
- [I. The Problem Statement](#i-the-problem-statement)
- [II. The Actual Terrain](#ii-the-actual-terrain)
- [III. Why Miner-First Strategies Fail](#iii-why-miner-first-strategies-fail)
- [IV. The Two Tracks and Why Both Are Required](#iv-the-two-tracks-and-why-both-are-required)
- [V. The Scenario Map](#v-the-scenario-map)
- [Key Uncertainties](#key-uncertainties)
- [VI. The Timeline and External Variables](#vi-the-timeline-and-external-variables)
- [VII. What Actually Has to Happen](#vii-what-actually-has-to-happen)
- [VIII. What Failure Looks Like](#viii-what-failure-looks-like)
- [IX. Conclusion](#ix-conclusion)
- [Sources](#sources)
---
Same chain, same 21 million, same proof of work, not a new coin and not a campaign to leave Bitcoin. Bitcoin has an engineering problem. One implementation writes the menu most economic nodes download. That implementation's undocumented behavior is the target every alternative has to chase. That is a single point of failure dressed as decentralization.
Bitcoin Core's review culture, release engineering, and reluctance to rush consensus changes are why the money rules have held. That record is not the dispute. The dispute is informal merge authority on a capturable architecture, concentrated funding, and an exit so costly it does not constrain who merges.
The diagnosis of the implementation monopoly and the no-spec moat is in *[Who Controls Bitcoin](/articles/bitcoin-governance)* and the *[Argument Map](/articles/bitcoin-governance-argument-map)*. The verification work is in *[Why Bitcoin Needs a Specification](/articles/why-bitcoin-needs-a-specification)*. This article is what has to happen, in what order, and what failure looks like.
---
## I. The Problem Statement
The numbers are public. Seventeen years of Bitcoin Core git history show a PR-weighted authorship Gini of about 0.851 historical / 0.834 recent. The top three merger accounts have executed 81.1% of all-time historical merges (50.2% / 82.2% top-1 / top-3 in the 2022+ window of 5,747 PRs). In calendar year 2025, 56% of all merges flowed through one person funded by Brink ([Engineering Impact Report](https://brink.dev/blog/2026/03/26/engineering-impact-report-2025/)). Five people still hold merge access. Core development drew $8.4 million in 2023 against a two trillion dollar market cap. The tables are in [Bitcoin Governance Research](https://github.com/secsovereign/bitcoin-governance-research) and *[Who Controls Bitcoin](/articles/bitcoin-governance)*.
None of this requires a conspiracy. People fund what they understand, hire from networks they trust, and select for demonstrated alignment. The architecture is capturable. Concentration is structural, not a meeting. That makes it harder to argue against and harder to fix. You cannot swap out maintainers and solve the problem. The problem is the monoculture. What keeps the monoculture in place is the absence of a formal consensus specification. That mechanism is [the no-spec moat](/articles/bitcoin-governance#vi-the-no-spec-moat-and-why-it-matters).
Without a spec, any alternative has to reverse-engineer undocumented behavior from Core itself. That ties every alternative to Core by definition. The no-spec moat is not an oversight but the thing that makes the monopoly rebuild itself every time someone tries to compete. The moat dissolves when a credible formal specification exists, and not before.
---
## II. The Actual Terrain
As of mid-2026, four pools controlled over 70% of Bitcoin's roughly 929 EH/s. Foundry held about 31%, AntPool 18%, ViaBTC 13%, and F2Pool 10% (source: [mempool.space](https://mempool.space/graphs/mining/pools), [D-Central H1 2026 Report](https://d-central.tech/reports/state-of-bitcoin-mining-2026-h1/)). Three pools are enough to exceed half of all blocks. Those shares move week to week. The structure does not. A single pool in the high twenties is already large enough that a further swing matters.
The concentration that matters more is who builds the block, not who hashes it. Under Stratum V1, which still carries most of the network, the pool picks the transactions. Hashrate numbers describe who mines blocks. Template control describes who decides what goes in them. Those are different concentrations, and the second one is the censorship risk. Every miner pointing hashrate at Foundry, AntPool, F2Pool, or ViaBTC is handing transaction selection to a US or Chinese entity with its own regulators and its own business.
Stratum V2 with Job Declaration lets a miner build the template while staying in a pool so payouts stay even. The first live Job Declaration block was mined June 25, 2026 (block 955,318, DMND pool, GoMining template). Seven major pools, about 75% of global hashrate, joined the Stratum V2 Working Group in May 2026. Joining the working group is not the same as turning Job Declaration on. As of mid-2026, only DMND and Braiins run V2 natively in production. Ocean got the same result through DATUM before its leadership situation deteriorated. Most of the network is still on V1 with the pool picking the transactions.
The nodes tell the same story. As of May 2026, only about 16% of nodes were running Core v30 with the higher OP_RETURN limits, which is the version Core actually shipped (source: [Clark Moody dashboard](https://bitcoin.clarkmoody.com/dashboard/), May 2026). More nodes were running pre-v30 software or Knots than were running Core's own controversial change. Knots peaked at roughly 25% of public nodes in September 2025 and settled around 20% as of mid-2026, the last pre-split reading (source: [Coin Dance](https://coin.dance/)). That is demand for a policy alternative, not implementation diversity. In 2025 that client was Knots, still Core's lineage on Bitcoin. Luke's Knots later followed a BLAKE2b proof-of-work hard fork and left Bitcoin. Core-derived forks that stayed on Bitcoin are still that lineage, which is why *[Who Controls Bitcoin](/articles/bitcoin-governance)* treats reachable-node splits as demand, not as a break in the monoculture. No dated measurement exists for what share stayed after the split. The missing piece is not demand but a separately written client that an exchange or payment processor can actually run, and a clear answer to who is liable if that client splits the chain.
DCG owns Foundry, the largest pool, and also owns Grayscale, the largest Bitcoin asset manager. Fortitude Mining is trying to go public under that same roof. There is no documented funding tie between DCG and the organizations that pay Core developers. There does not have to be. Hashrate, asset management, and mining infrastructure already sit in one parent company.
---
## III. Why Miner-First Strategies Fail
Miner campaigns without the entities that actually hold value show preference. They do not move the protocol. Protocol changes stick when the economic majority enforces them, because that is when refusing costs money. SegWit succeeded in 2017 not because miners wanted it but because economic nodes made non-compliance dangerous. A hashrate campaign that never gets that pressure fails even when the technical case is sound. People read those failures as hashrate problems. They are economic majority problems.
Hashrate matters. Pool decentralization matters. Neither moves the protocol unless economically significant nodes adopt the change. Push miners first and you get a preference poll, not a rule change.
Implementation diversity is the precondition. Everything else waits on it. Consensus is the small part of a node. Close to 90% is not consensus. Wallet, policy, networking, index, RPC, and mempool sit in that remainder. A Core-derived client can change what it forwards. Knots did. It does not rewrite wallet, networking, and the rest of that surface as a separately designed program. A separately written client can, but only if it can prove it still enforces the same money rules. That proof is what the spec makes possible. That is why the moat dissolves when the spec exists.
---
## IV. The Two Tracks and Why Both Are Required
There are two problems. The order between them is the strategy.
The implementation problem is a specification problem first. Without a formal consensus specification, an alternative cannot prove it enforces the same rules as Core. Every serious alternative in Bitcoin's history has eventually been found to diverge. btcd accumulated documented consensus bugs across 2022-2024 after years as a clean-room Go client. Each bug was a case where the two programs would have accepted or rejected blocks differently. The point of a second implementation is to catch exactly those gaps. btcd kept being the thing that diverged. That record is in *[Governance Paralysis Was The Victory](/articles/governance-paralysis-was-the-victory)*. What a genuine alternative actually requires is in *[Argument Map, Part XV](/articles/bitcoin-governance-argument-map#part-xv-what-alternatives-actually-require)*.
Satoshi warned against a second compatible implementation and called it a menace to the network. Take that warning seriously. The risk he named was a quiet consensus mismatch that splits the chain. Formal verification alone does not close that risk. You need formal verification, fuzzing, differential testing, and property tests. That stack is the engineering answer, not a dismissal of the warning.
Bitcoin Commons is the leading attempt at that path, a from-scratch Rust node written separately from Core, not copied from it.
The Orange Paper is the document that node is built from, Bitcoin's consensus rules written as mathematics a person can read. Signature checks, UTXO accounting, script, and block structure are defined as objects with precise rules instead of as whatever Bitcoin Core happens to do. Any implementation can check itself against that document. That is why the Orange Paper is a public good even if Commons is slow. The no-spec moat dissolves when the spec exists, for the whole ecosystem, not only for Bitcoin Commons.
The BLVM consensus layer is the code that implements those rules, a bounded set of deterministic functions. Wallet, networking, and policy are not mixed into it. That isolation is what makes a proof about the money rules tractable.
The Specification Lock is the check that runs on every merge. It uses Z3, a theorem prover, to ask whether the Rust still satisfies the contracts taken from the Orange Paper. The spec does not write the code. People write the code. If a change would break a consensus property, the merge fails.
Full-chain differential replay against Bitcoin Core is the scale test. `blvm-bench` targets on the order of 900,000 blocks. Those runs are operator-driven and resource-heavy. That is not a claim every CI job has zero-divergence proof to tip. Methodology lives in the [differential testing guide](https://docs.thebitcoincommons.org/development/differential-testing.html). The usual objections about proofs and tests are answered in *[Why Bitcoin Needs a Specification](/articles/why-bitcoin-needs-a-specification)*.
Cryptographic merge authorization is designed and stays off until security review, key management, and community validation. The software carries explicit unreleased warnings. What exists is that foundation. Getting an exchange or payment processor to run it still takes independent security audits, extended mainnet operation, operational hardening, and legal review. That work is ahead, not behind. First institutional adoption is more likely 2028-2029 than late 2027 on an optimistic calendar.
The first question a board will ask is liability. If a formally verified alternative and Core disagree, and the chain splits, who pays? Formal verification lowers the odds of that split. It does not tell counsel who is on the hook if it happens anyway. The first institution to run non-Core software needs that answer in full, not a smaller probability. The likely package is an independent audit, insurance, a staged rollout with a fallback to Core, and a contract that names the split case. None of that exists yet, and all of it takes time.
The mining problem is simpler in one way. The product already worked. Ocean showed that miners will move for TIDES-style honest payouts, non-custodial architecture, and miner template control. What failed was the organization. A pool run by one founding figure, with that person also holding reserve management, transaction policy, and protocol advocacy, is a single point of failure. It failed the way that structure fails.
The successor needs the same product and a different organization. Reserve capital has to sit apart from day-to-day operators. Protocol advocacy has to sit apart from pool operations. The bar is governance that survives the removal or conduct of any one person. Ocean's collapse is the list of what not to repeat.
DMND offers V2-native job declaration in production. Braiins has run V2 with job declaration since before the working group existed. Neither fills Ocean's niche. DMND does not have the transparent pro-rata payout model. Braiins is not non-custodial. As of August 2026, nothing else combines non-custodial payouts, honest accounting, and miner template control.
The two tracks only work together. A verified alternative gives exchanges and payment processors an answer when the board asks why they are not running Core. Without that answer, a more decentralized pool is an ideology that institutions will not touch. With it, economically significant nodes can run non-Core software, and miner campaigns can actually move the protocol. Parallel work is what produces force that neither track produces alone.
---
## V. The Scenario Map
Three scenarios cover the next three to five years.
**Floor.** Bitcoin Commons or a comparable formal-spec implementation is running on at least one economically significant node by 2029. A successor pool holds 3-5% of hashrate before the April 2028 halving. Stratum V2 Job Declaration reaches 10-15% of hashrate by the end of 2027, mostly because new ASIC firmware starts shipping it on. Core still dominates, but the claim that no credible alternative exists is gone. Making Core irrelevant is the destination. The floor is just the first proof that the alternative can be run.
**Mid.** One or two exchanges or payment processors are running a formally verified alternative by 2029. A successor pool holds 8-12% of hashrate. Implementation diversity then has real economic weight, pool share has real weight on what gets built into blocks, and Core's hold on protocol decisions is constrained for the first time.
**Ceiling.** A genuine multi-implementation Bitcoin by 2030-2031. Several exchanges running formally verified alternatives. No single pool near 25% of hashrate. Stratum V2 Job Declaration the default on new ASIC firmware. That is a decade of work, not a three-to-five year one.
---
### Key Uncertainties
Five open questions decide which scenario shows up, and when.
**How fast institutions adopt.** A verified implementation that no exchange runs produces nothing. Selling node software into an exchange or payment processor takes quarters, not weeks. It needs an independent audit, legal review, insurance for a split, and board sign-off. The liability question lives inside that cycle. Formal verification lowers the odds of a split. It does not tell a board who pays if one happens. The software has to be ready before that cycle starts, and the cycle has to start well before the next protocol fight.
**Cash for unlucky streaks.** Most people understate what a successor pool needs in reserve. Ocean's $6.2 million seed covered launch, not running at scale after the halving when margins are thinner. Low-to-mid tens of millions is the realistic reserve for a pool that pays TIDES-style pro-rata and cannot default after a dry run of blocks.
**When firmware actually ships Job Declaration.** That depends on Foundry and AntPool turning the feature on, not on joining a working group. The large pools have a reason to take V2's encryption and efficiency and leave template control where it is. Watch for Foundry turning Job Declaration on. Working group membership is not that signal.
**Whether Core writes a spec of its own.** A credible formal-spec alternative with institutional backing could push Core-funded work to write more of the consensus rules down. If Core or a Core-funded organization publishes a competing spec, the ground changes. The no-spec moat dissolves no matter who dissolves it, which is good for Bitcoin. It also takes away the advantage of having the spec first.
**Where Ocean's hashrate and Tether went.** Tether committed hashrate to Ocean in April 2025 and has said nothing public about where that hashrate went after the August 2026 leadership situation. Do not count that volume for a successor until someone documents it.
---
## VI. The Timeline and External Variables
The April 2028 halving is the largest external date. Block subsidy drops from 3.125 to 1.5625 BTC. Daily issuance falls from roughly 450 to roughly 225 BTC. Post-halving production cost lower bounds are modeled near $93,000 against mid-2026 break-even estimates near $65,000 (source: [D-Central H1 2026](https://d-central.tech/reports/state-of-bitcoin-mining-2026-h1/)). About 20% of miners are already unprofitable at current prices and difficulty. The efficient machines are hydro-cooled S23-class hardware at about 9.5 J/TH. Anything much worse than that is under shutdown pressure.
History is against a new small pool after a halving. Smaller pools have lost share every previous time, because the capital bar went up and only the well-reserved operators survived. That pattern holds unless this time is different, and it is, in one way. FPPS insurance gets more expensive when margins compress and luck hits harder. The gap between a guaranteed daily payout and what the blocks actually produce is not free. The pool eats it. When block rewards are smaller, that gap matters more to a miner on the edge. A TIDES-style model without that insurance overhead pays better expected returns to miners who will take variance. That relative advantage is widest in the 12-18 months after the halving, which means a successor has to be running and trusted before the halving, not after it.
F2Pool has a documented history of filtering. Foundry's compliance posture is institutional by design. Non-custodial template control gets more valuable as US-domiciled pools filter more, because it is the architecture that does not depend on the operator staying brave.
Implementation diversity is not only an engineering problem. Core's maintainers and funders have a tight network and a loud story. An alternative needs its own money, a review culture people trust, and a way not to be framed as an attack on Bitcoin. The capturable-architecture critique is correct, and it is also the story Core's defenders will use against any alternative. The answer is not a louder governance argument but a running alternative with a clean audit trail and no chain splits.
---
## VII. What Actually Has to Happen
Implementation work comes first. Nothing else has force without it.
The formal-spec path needs a release an exchange or payment processor can run. That means an independent security audit, extended mainnet operation without incident, operational hardening, and a prepared answer on liability before the first institutional meeting. The pitch is not a philosophy. A board would need the differential record it can actually read, the Specification Lock that checks the code against the Orange Paper, fuzzing and property-test results, the audit, the insurance, and why this lowers their risk instead of raising it. That packet is not in hand. Finding the people who can have that conversation is a different job from writing the software, and both have to run at once.
Do not start with the largest exchanges. Their legal overhead makes them the slowest. Start with mid-size exchanges and payment processors that have technical leadership, a reason to care about sovereignty, and a reason to stop waiting on Core's release cycle. The first one or two matter because they show that institutions can move.
On mining, the question is who can rebuild what Ocean built, with a better organization. The product is specific. TIDES-style transparent pro-rata payouts, non-custodial architecture, miner template control through DATUM or the equivalent, and a structure that keeps reserve capital, operations, and protocol advocacy in separate hands. The reserve needed to survive unlucky streaks at real scale is low-to-mid tens of millions. Ocean's $6.2 million seed covered launch, not that. A successor needs more capital, and an organization that survives the departure or controversy of any one founder.
---
## VIII. What Failure Looks Like
It can fail in four places.
It fails on implementation if the verification stack exists and no economically significant node adopts the alternative before the next protocol fight. A clean implementation with no exchange running it has no weight. The governance critique can be right, the tests can be clean, and none of it matters if the economic majority never enforced anything.
It fails on mining if the Ocean successor is not standing before the April 2028 halving. After the halving, large institutional pools with deep reserves take share. The window for a non-custodial pool to attract enough miners to matter is widest before the halving raises switching costs.
It fails as an organization if the successor repeats Ocean. The first serious protocol fight the pool takes a side in will test whether reserve governance, operations, and advocacy are actually separate. If they are not, the pool splits at the moment it needs to hold.
It fails on the pitch if the campaign leads with ideology. The people who control economically significant nodes have boards, lawyers, and fiduciary duties. The argument that wins is risk management, with the verification stack and a direct answer on liability. Lead with Bitcoin philosophy and they will treat you as someone whose job they do not have.
---
## IX. Conclusion
The implementation monopoly is a solvable engineering problem. The Orange Paper exists. The Specification Lock checks annotated paths. Full-chain differential replay against Core is the scale test, operator-driven, and not a CI-to-tip certificate. Formal verification, fuzzing, differential testing, and property tests are what make a second client safe enough to run. That foundation has not existed before in Bitcoin. What remains is adoption, the liability answer, the audit, and the time those things take inside institutions.
The mining problem has a product that already worked, a market that already showed up, and a hole where the Ocean successor should be. That hole will not stay open. The halving closes it from one side. Regulatory pressure on US-domiciled pools opens it from the other.
The path is two tracks at once. Implementation diversity gives institutions an answer they can defend. Pools that do not hold keys and let miners build their own templates give miners a reason to move that is about money, not politics. When both exist, miner pressure on protocol questions has economic weight again for the first time since the blocksize war. The work is to get both in place before the next major protocol fight.
---
*Related: [Who Controls Bitcoin](/articles/bitcoin-governance), [The Vertical Layer Problem](/articles/the-vertical-layer-problem), [Why Bitcoin Needs a Specification](/articles/why-bitcoin-needs-a-specification), [Governance Paralysis Was The Victory](/articles/governance-paralysis-was-the-victory).*
---
## Sources
- [Bitcoin Governance Research](https://github.com/secsovereign/bitcoin-governance-research). PR-weighted Gini, merge concentration, stalled-proposal dossiers
- [Brink Engineering Impact Report 2025](https://brink.dev/blog/2026/03/26/engineering-impact-report-2025/), March 26, 2026. 56% merge concentration
- [mempool.space mining pools](https://mempool.space/graphs/mining/pools). Hashrate share
- [D-Central, The State of Bitcoin Mining, H1 2026](https://d-central.tech/reports/state-of-bitcoin-mining-2026-h1/). Network hashrate, post-halving cost bounds
- [Clark Moody Bitcoin dashboard](https://bitcoin.clarkmoody.com/dashboard/). Core v30 node share
- [Coin Dance](https://coin.dance/). Knots node share
- Stratum V2 Working Group announcements, May 2026. Pool membership vs Job Declaration activation
- [ocean.xyz](https://ocean.xyz/). TIDES payouts, DATUM template control
- [TFTC, first Stratum V2 Job Declaration block](https://www.tftc.io/stratum-v2-job-declaration-first-block-dmnd-gomining/), June 25, 2026. Block 955,318
- [Bitcoin Commons documentation](https://docs.thebitcoincommons.org). Orange Paper, Specification Lock, differential testing record
- [Orange Paper / Bitcoin Commons consensus spec](https://thebitcoincommons.org/spec.html)
---
# The Vertical Layer Problem
## The consensus layer is horizontal. The software that implements it is not.
## Contents
- [Benevolent dictatorship is right for ordinary software](#benevolent-dictatorship-is-right-for-ordinary-software)
- [The hierarchy arrives as workplace habit](#the-hierarchy-arrives-as-workplace-habit)
- [Bitcoin produces agreement, not a product](#bitcoin-produces-agreement-not-a-product)
- [Refusing a release only delays the next download](#refusing-a-release-only-delays-the-next-download)
- [Undeclared concentration in the merge log](#undeclared-concentration-in-the-merge-log)
- [Succession needs agreement that does not exist here](#succession-needs-agreement-that-does-not-exist-here)
- [Which thing gets forked](#which-thing-gets-forked)
- [What a horizontal development layer looks like](#what-a-horizontal-development-layer-looks-like)
- [The missing specification is doing the work](#the-missing-specification-is-doing-the-work)
- [Where this design fails](#where-this-design-fails)
- [The two questions that decide it](#the-two-questions-that-decide-it)
- [Sources](#sources)
---
Bitcoin cannot be governed like Linux. A dictator is a good way to ship a kernel, and a bad way to write Bitcoin's node software, even when the people who write it are competent and the code is good.
Bitcoin's consensus layer is horizontal. Every node checks blocks on its own, and no node can force another to take a bad one. The software that implements those rules is written by a hierarchy, and replacing the people who can merge, or making those people more accountable, leaves the hierarchy in place.
Operators download what that hierarchy ships. The money rules sit in the same program as the defaults, so a fight about who writes the client, or about what it ships by default, gets treated as a fight about Bitcoin. The protest people already know is a chain fork. You leave the chain by changing the money rules, which has happened many times, and each time it is a new coin. You stay on it by running a different program that still implements those rules.
A fight about the default client should not mean leaving the chain. A Core-derived fork can leave Core's defaults and stay on Bitcoin, and it is still mostly Core's code. An independently written client, checked against a written specification rather than Core's undocumented behavior, is the missing exit.
Nodes stay equal even though the people who write the code never will, and that still does not entitle those people to a throne.
---
## Benevolent dictatorship is right for ordinary software
Benevolent dictatorship produces good software. Linux runs most of the internet's infrastructure and was governed for decades by one person's judgment about what merged. Python, Django, and Rust all had stretches of single-authority governance, and the work held up.
Concentrated authority makes architectural decisions faster than committees do. It keeps one design across a large codebase, and it ends fights that would otherwise eat years. Linux is a product, and a small group decides what goes in the kernel while everyone else downloads the result. Someone has to pick what ships, and a hierarchy is the right way to run that.
Forking the kernel is allowed. Almost nobody does it. The fork is yesterday's code. The patches people want keep going into the original project. Bitcoin node operators do the same thing. They download Core and wait for the next release. The difference is that Linux is only a product, while a Core release carries the wallet, the relay, and the money rules together, which is why an argument about the first two arrives as an argument about the third.
The pattern is right for ordinary software and wrong for money.
---
## The hierarchy arrives as workplace habit
The hierarchy also shows up because paid engineers bring their workplace with them.
Most of the work is done by people employed to do it. The majority of Linux kernel contribution comes from paid engineers at Intel, Red Hat, Google, IBM, and a handful of others, and that has been true for well over a decade. The same pattern shows up across most infrastructure projects of any size. Volunteer contribution is real, yet paid engineers carry the load.
People who spend forty hours a week inside a company's engineering process bring that process with them. Review turns into an approval chain. Roadmaps get set by a small group. Release management belongs to specific people on a schedule. Disputes go up to whoever is supposed to end them. Nobody votes any of that in. It arrives as professional habit, because it is the only way of coordinating software most working engineers have ever practiced.
Core's contributors are largely employed or funded by a small number of organizations. The governance system that emerged at Core is what happens when people trained in corporate engineering coordinate a project and nobody is asked to design those rules on purpose.
The usual worry about concentrated funding is that donors pressure specific outcomes. That takes intent, coordination, and a visible fight. The quieter path runs all the time. People paid by companies bring their company's way of working with them, with no one telling them to.
Replacing the current contributors accomplishes nothing on its own. A different set of people, from the same professional background and funded the same way, would rebuild the same structure within a few years. The structure comes from where those people were trained, not from who they are. The social-layer version of that argument is *[The Social Layer Is the Attack Surface](/articles/bitcoin-social-capture#ix-structural-capture-does-not-require-bad-actors)*.
If paid engineers really import the hierarchy, a project staffed from different backgrounds and funded differently should not reconcentrate merge authority the same way. If it still does, the workplace-habit story is wrong, and hierarchy is coming from something more basic about coordinating software.
Not all of Core's structure is imported habit. Some of it was chosen on purpose. Merge access tightened after the inflation bug for stated reasons. Review culture hardened after the blocksize war as a considered response to what that conflict cost. Reluctance to touch consensus lightly is a position people hold out loud. Attributing all of it to unexamined corporate reflex would be too clean. Habit set the default, and deliberate choice then reinforced it.
The merge set also decides which changes count as consensus changes, which is how a proposal gets labeled too dangerous to merge. If that label is doing real work, it should show up in what shipped and what sat. That record is *[What Bitcoin's Stalled Proposals Tell You](/articles/what-bitcoins-stalled-proposals-tell-you)*.
---
## Bitcoin produces agreement, not a product
Bitcoin's coordination problem is agreement among peers who do not trust each other. Satoshi solved that for the chain. A bad block dies at every node that checks it. Linux produces a kernel people download. Bitcoin produces agreement about which chain is valid.
That check is only as good as the program doing it. The program is written by a small group. Inside that program the consensus rules are 10,122 code lines, 7% of the implementation, measured on Bitcoin Core 32.1 in *[The Rules Are 7% of the Program](/articles/the-rules-are-7-percent)*. The [Commons white paper](https://thebitcoincommons.org/whitepaper.html) puts the set of people who can do consensus-critical Bitcoin work in the dozens to a few hundred worldwide. Miners and node operators are not in that set. They download a release, confirm it talks to their peers, and run it. They are trusting the maintainers and developers to have done the review they will not do themselves.
"Don't trust, verify" describes what a node does with a block, not what anyone does with a release. Your node checks every block against the rules. Almost nobody checks the software that holds those rules.
The trustless layer sits on a trusted one. The same gap, applied to Bitcoin Core, is *[Don't Trust, Verify](/articles/dont-trust-verify#vi-the-same-system-applied-to-bitcoin-core)*.
The people who write that software are identifiable, and identifiable people can be pressured. If they fold, the software layer folds, whatever the cryptography says. A second client does not answer that by adding more people willing to say no. It answers it by giving operators somewhere to go. Refusing a release is only a refusal when there is other software to run, and without that software it is a delay.
Writing the code will never be as widely spread as checking blocks. Most people who run a node will never read it. That gap is what gives the authors more power than the operators, and it is why "the operators will catch it" is not a check. The gap is real and is not going away.
---
## Refusing a release only delays the next download
A node can refuse a release. Other clients exist. btcd keeps diverging. libbitcoin exists and the ecosystem cannot use it without being rebuilt. A Core-derived fork that stays on Bitcoin is still mostly Core's code, so it is not a destination.
You can pin an old Core version for a while, and you cannot pin it forever. Unmaintained node software rots. Bugs pile up, the network moves, and eventually you take the next download or you fall behind. The people who write the default still govern, because refusal only delays the next download.
After the OP_RETURN relay change merged, Bitcoin Knots went from about 4.7% of reachable nodes at the end of April 2025 to a peak of 25.45% on September 14, 2025, and stayed above 19% through that stretch, according to [Coin Dance](https://coin.dance/). That was a policy protest on the same codebase, still one client. It did not give anyone a place to stay. Luke's Knots later left Bitcoin on a BLAKE2b proof-of-work hard fork. *[Making Core Irrelevant](/articles/making-core-irrelevant)* treats the reachable-node split as demand for a policy alternative, not as a break in the implementation monoculture.
Running different defaults is cheap compared to risking a chain split. Miners can refuse an upgrade, so a consensus change can be blocked. That veto is rarely used. The cost of refusing a default falls on the operator. The benefit of setting it accrues to whoever sets it. Nobody has to capture consensus enforcement to govern this way.
---
## Undeclared concentration in the merge log
The stated model is rough consensus among a broad contributor base. In the merge log, a handful of accounts do most of the merges. Bitcoin Core is not formally a benevolent dictatorship and has never claimed to be, yet how it actually merges looks like a dictatorship with the name taken off, which is worse, because undeclared concentration is harder to see and harder to contest.
Bitcoin Core already posts ACKs on GitHub, which is not the same as the decision forming there. An ACK is a comment on a pull request. Which pull requests are going to merge is decided off GitHub, on IRC, in closed CoreDev sessions, and in Signal groups. Merge is a permission held by about five accounts on bitcoin/bitcoin. Reviewers do not have it, and one of those five ships the code.
Concentration of merge rights on its own still proves nothing. Any mature project restricts commit access, and Linux would look just as lopsided on the same measure. A high concentration of who may merge could just mean they are limiting who can push to a codebase where a bad merge could print coins. That would be a defense if the scarce mergers were also doing the review, and they are not.
Review activity Gini sits near 0.92, while merge-authority Gini is lower because the merger set is tiny, not because power is spread. Review is spread out relative to merges, and merge authority is not. Authorship Gini sits near 0.85. Brink's [2025 Engineering Impact Report](https://brink.dev/blog/2026/03/26/engineering-impact-report-2025/) published that in calendar year 2025 more than half of all merges flowed through a single individual funded by one grant organization. The [Bitcoin Governance Research](https://github.com/secsovereign/bitcoin-governance-research) dataset puts the 2022+ window at 50.2% top-1 and 82.2% top-3. Self-merge among maintainer-authored merges is 25.5%, meaning the same people proposing changes were approving them on a quarter of those landings.
That dataset covers seventeen years of Core history and counts comments, ACKs, and review submissions on GitHub. It does not count hours spent checking consensus-critical code or how deep each review went, so these figures describe who shows up in the record, not who understood the code best in any given week.
The bug usually cited with these numbers is CVE-2018-17144, the inflation bug that sat in Core for eighteen months. People use it to prove Core is incompetent, which it does not prove. It sat in production, was never exploited, and was patched quickly after disclosure. Patching it fast after disclosure is not the same as catching it.
It propagated to Knots, ABC, and Unlimited, because those clients descend from Core's codebase. Listing those clients as independent checks is a mistake when they share a lineage. The case study is *[Governance Paralysis Was The Victory](/articles/governance-paralysis-was-the-victory#cve-2018-17144-the-bug-that-proved-gavin-right)*.
What the CVE does show is that implementations copied from a common codebase inherit that codebase's blind spots, which is the argument for building from a specification instead of observed behavior. An implementation written against a stated standard does not inherit those bugs by copying Core's source. It can still ship its own.
Three things that are fine for ordinary software are a problem in the process that writes Bitcoin's defaults. Decisions about what ships cannot be reversed except by whoever made them. Authority lives in the merge set without a procedure, so when that set leaves you have a crisis, and there is nothing to transfer except the habit of being listened to. Legal, financial, regulatory, or personal leverage only needs that handful.
---
## Succession needs agreement that does not exist here
Every vertical project eventually loses its founder. Python is the usual counterexample. Guido stepped back, the community designed a steering council, and the language came through it intact, with no cryptographic governance, no formal specification, and no distributed signing authority. What carried it through was that people still wanted to work together, and that they had time. There was enough shared purpose to design a governance system after Guido left, and nothing catastrophic happened while they were designing it. Users just kept running the old interpreter and waited.
If Bitcoin's maintainers disappeared tomorrow, existing nodes would keep running. Python users can do the same thing. The difference is what cannot wait. CPython can sit unchanged while people design a council. Bitcoin still needs someone who can patch a bug that prints coins, and someone still picks what new operators download. You cannot put those jobs on hold until a new council exists.
Bitcoin also does not have the shared purpose Python had. The blocksize war was the test of whether it could resolve a fundamental disagreement through social process under pressure, and it could not do so without years of conflict and permanent factional damage. A succession plan that needs the community to agree under pressure has already been tested here, and it failed, which is why Core still cannot process contested work.
Taproot is the usual reply, because that change did ship and activate, yet it is the wrong comparison. Taproot was not the lead maintainer disappearing, and it was not a fight on the scale of the blocksize war. That it shipped says Bitcoin can activate a change when the disagreement is smaller, not that the community can design a governance system after the people in charge are gone.
---
## Which thing gets forked
The blocksize war ended in a fork. Bitcoin Cash left, Bitcoin kept the ticker and the market. Some people say a fork is how this ecosystem keeps developers honest. The blocksize war was that fork. You cannot treat it as both the check working and proof that social process failed.
What matters is which thing gets forked. Bitcoin Cash forked the chain, which meant splitting the ledger, the hashrate, the economic network, and the community, permanently and by design. The cost of that exit was so high that it scares people off without keeping anyone honest. Nobody threatens it credibly, because the threat costs the threatener nearly everything they were trying to protect.
A governance fork is a different operation. Two implementations built against the same specification remain consensus-compatible, which means a disagreement about how a project is run can be resolved by one group building differently without anyone leaving the money. The chain, the ledger, and the economic network do not split. What splits is a development process, and a development process can afford to split. The chain-fork trap is *[The Social Layer Is the Attack Surface, §VII](/articles/bitcoin-social-capture#vii-controlled-opposition-and-the-chain-fork-trap)*.
---
## What a horizontal development layer looks like
Vote weight comes from work recorded in public, and a title does not confer it.
The [Bitcoin Commons white paper](https://thebitcoincommons.org/whitepaper.html) sets the bar for a merge with two questions at once. One is where the change lives, in the consensus specification, the protocol, the node, or an optional module. The other is what kind of change it is, a routine fix, a feature, something that touches consensus validation, an emergency patch, or a change to the governance rules themselves. When both apply, you take the higher signature count and the longer wait. A bug fix in the consensus layer still needs the consensus-layer bar, while a feature in an optional module does not.
Routine maintenance clears on fewer signatures and a short wait. Consensus-adjacent changes need near-unanimity and a delay measured in months. Changes to the governance rules themselves need more than that. A contributor cannot approve their own merge, and even a repository administrator cannot bypass the signature check.
The patch that cannot wait runs through a declared emergency in three classes. Emergency keyholders declare a class, and that declaration changes the merge rules until a clock expires. Network-threatening work gets the fastest path, including no review wait while the declaration is live. Less severe classes keep longer waits and higher bars. Declaring an emergency is a different act from tagging a pull request as emergency work. After the clock, a written post-mortem is required and ordinary rules return. Nobody keeps a low bar because they might need one later.
Optional features load as process-isolated modules outside the money rules. Lightning, mining interfaces, and similar tools can compete without anyone treating them as a consensus change. The base node still validates blocks against the specification, so a feature fight does not become a fight about the money.
A further ladder, vote weight on the crates you have actually shipped, is specified as a complement to that merge policy, and it is not what is enforced today.
Every action is cryptographically signed and publicly auditable once that authorization is switched on. Power is visible because anyone can check the record, not because people are supposed to behave. The software layer cannot make every contributor equal the way every node is equal, and it can make the record checkable, which is what matters for who may change the code.
---
## The missing specification is doing the work
None of that holds without a written specification. Fights still go to whoever has been around longest, because there is nothing independent to measure a judgment against, so authority reconcentrates no matter what a governance document says. Core cannot be repaired by redistributing merge rights, and the missing specification is what keeps the monopoly in place, because that missing document is doing work. The longer write-up is *[Who Controls Bitcoin](/articles/bitcoin-governance#vi-the-no-spec-moat-and-why-it-matters)*.
A written specification gives contributors something to be right about that is not a person's opinion, and writing it is the hard part, because Bitcoin's live rules include serialization quirks, historical bugs the network accepted, and a policy and consensus boundary that is blurrier in practice than on paper. A specification that matches mainnet has to encode all of it, including the parts nobody would design on purpose, which makes it a large contested document that nobody writes in a week.
With a specification, fights become what the document says. Formal verification and machine-checkable proofs shrink the room to argue about what the specification means.
It is also what makes exit cheap enough to be credible. A formally specified implementation can be forked against the specification without reverse-engineering Core. A governance ruleset can be exported as a signed package and replaced without splitting the ledger, which is what makes a fork usable. Cheap exit keeps people honest in ways internal process cannot. The sequencing of that exit is *[Making Core Irrelevant](/articles/making-core-irrelevant)*.
The governance system described is [Bitcoin Commons](https://thebitcoincommons.org), the specification is the [Orange Paper](/articles/why-bitcoin-needs-a-specification), and the implementation is [BLVM](https://docs.thebitcoincommons.org).
---
## Where this design fails
The crate ladder, if it ever ships, can let a shallow contributor outvote the person who wrote the subsystem. A single merged pull request can put someone on questions they cannot evaluate. Someone who has shown they understand the architecture still has to gate who votes. That limit is real. Below it, more votes make worse decisions.
The merge policy specified today has a different failure, because the people who hold the keys can collude. The keys are supposed to sit in different places for that reason, and a governance ruleset has to be forkable without splitting the money.
Distribution is slow when you need a same-day security patch. Ordinary merge rules should stay slow. The specified answer is a declared emergency with a clock, which is the substitute for a person who can merge anything.
If one implementation still defines the rules everyone else must copy, distributed governance is theater. A specification plus full-chain tests is what turns "we match Core" from a claim into a pass/fail check.
Commons has not run this merge policy at scale. Cryptographic merge authorization is designed and stays off until security review, key management, and community validation. Gates and declared emergencies are rules on a public record, and a person constrained only by custom is what they replace. That should break differently under pressure, and it remains a prediction until someone runs it. The specification, the emergency path, and cheap exit have to exist because of those limits.
---
## The two questions that decide it
Bitcoin does not get a pass because some of the people writing the code are skilled or well-intentioned. Failed monetary institutions had skilled, well-intentioned people too. What matters is whether the people with merge authority still decide what Bitcoin nodes run on ordinary work.
It also matters whether an inflation bug can be patched without giving that merge set the power to merge whatever they want. The declared class and the expiring clock are the answer to that second question, which is why the overnight patch does not require a throne.
A governance system that works only while the current merge set holds the chairs was built for Linux, and it does not belong on Bitcoin's node software.
---
## Sources
- [Bitcoin Governance Research](https://github.com/secsovereign/bitcoin-governance-research). Merge/review concentration, Gini, self-merge
- *[The Rules Are 7% of the Program](/articles/the-rules-are-7-percent)*. Line count of Bitcoin Core 32.1: 10,122 rule lines inside 151,004 implementation lines
- [Brink, Engineering Impact Report 2025](https://brink.dev/blog/2026/03/26/engineering-impact-report-2025/). One-person merge share
- [Coin Dance](https://coin.dance/). Knots reachable-node share
- [Bitcoin Commons white paper](https://thebitcoincommons.org/whitepaper.html). Dual bars (where and what), optional modules, three-class emergency (declaration vs PR tag), governance-ruleset exit
- [Orange Paper / Bitcoin Commons consensus spec](https://thebitcoincommons.org/spec.html)
- [Bitcoin Commons documentation](https://docs.thebitcoincommons.org). BLVM Specification Lock; cryptographic merge authorization designed, off
---
# The Rules Are 7% of the Program
## A line count of Bitcoin Core 32.1
*Release **32.1**, branch `32.x`, commit `f0de87f`, 26 October 2026. Current-tree figures are tokei 14 code lines. History figures are git numstat on non-merge commits.*
The consensus rules are **10,122** code lines. The implementation they sit in is **151,004**. The code that applies those rules, stores the result, or chooses what to relay and mine is **20,366**, twice the rules. The other **120,516** lines are the wallet, the GUI, RPC, P2P transport, and the rest of the node.
A wrong rule forks the network. A policy disagreement does not. The two live in the same program, and the rules are the thin slice. That is the measurement behind *[The Vertical Layer Problem](/articles/the-vertical-layer-problem)* and *[Why Bitcoin Needs a Specification That Humans Can Read](/articles/why-bitcoin-needs-a-specification)*.
---
## Contents
- [I. What was counted](#i-what-was-counted)
- [II. The tree](#ii-the-tree)
- [III. The implementation](#iii-the-implementation)
- [IV. The rules](#iv-the-rules)
- [V. What sits beside the rules](#v-what-sits-beside-the-rules)
- [VI. Tests](#vi-tests)
- [VII. Bundled code](#vii-bundled-code)
- [VIII. Who added the lines](#viii-who-added-the-lines)
- [Where the work went](#where-the-work-went)
- [What changes in the same commit](#what-changes-in-the-same-commit)
- [IX. Who last touched what remains](#ix-who-last-touched-what-remains)
- [Who still edits a system](#who-still-edits-a-system)
- [The size of the contract](#the-size-of-the-contract)
- [X. Patch debt](#x-patch-debt)
- [XI. What the count is for](#xi-what-the-count-is-for)
- [XII. Method](#xii-method)
---
## I. What was counted
Tokei parsed **2,698** files and **719,989** code lines. Qt locale files are 103 of those files and **286,741** of those lines. Tokei counts them as TypeScript. They are translations, and the charts below leave them off. Every other parsed file is in exactly one bucket.
The headline is the implementation. Vendored libraries are another 112,703. First-party code, implementation plus tests plus contrib, build, and docs, is **320,545**. Those three figures, 286,741 plus 112,703 plus 320,545, are the 719,989.
---
## II. The tree
Code lines, scaled to the tests
Tests
154,273
Implementation
151,004
Vendored
112,703
Contrib
9,062
Build and CI
6,206
Code, comments, and blanks, scaled to the implementation
CodeComments and blanks
Implementation
151,004 code · 756 files
Tests
154,273 code · 921 files
Vendored
112,703 code · 526 files
Docs
0 code · 189 files
Contrib
9,062 code · 97 files
Build and CI
6,206 code · 106 files
The program carries about as much test code as implementation code. On this release the test pile is the larger of the two. Implementation bodies are 73.8% C++ and 25.6% headers.
---
## III. The implementation
Seven hundred fifty-six files. The median file is 66 code lines. Thirty-three files of 1,000 lines or more hold 38.9% of the implementation. Fifty-four files hold half of it.
Implementation code lines, scaled to the wallet
Wallet
21,687
GUI
19,668
Validation
17,926
P2P
16,880
RPC and HTTP
16,520
Support
15,606
Crypto
10,122
Script
9,734
Mempool
8,363
The crypto bar is that directory. The 10,122 in section IV is a different cut.
The rest of the implementation, scaled to the executables
Executables
3,094
Peer seeds
2,679
Init
2,318
Node interfaces
1,719
Mining templates
1,019
Addresses
816
Logging
812
Interfaces
734
IPC
668
ZMQ
639
`src/node` is not all P2P. Block storage and chainstate in that directory are in the validation bar. P2P is the network files only.
---
## IV. The rules
Consensus here means the code that decides whether a block or a transaction is valid. The bundled signature library is outside this split. It is counted in section VII.
Share of the 151,004 implementation lines
7%13%80%
■ Rules, 10,122■ Adjacent, 20,366■ The rest, 120,516
What the 10,122 rule lines are, scaled to the hash code
SHA-256, RIPEMD
3,803
Script interpreter
2,772
PoW, merkle, deploy
1,312
Keys and integers
1,117
validation.cpp checks
562
Block and tx types
556
SHA-1, SHA-3, and SHA-512 are in the rest. The interpreter itself is 1,584 of the 2,772.
Core's exported `libbitcoinconsensus` is **4,757** of these lines. The kernel target is a different list, and it still compiles policy and mempool.
---
## V. What sits beside the rules
Adjacent means the code that applies the rules, stores the result, or chooses what to relay and mine. An index can be wrong without making a block invalid. A policy limit can change without forking.
The 20,366 adjacent lines, scaled to policy and mempool
Policy, mempool
8,747
Chainstate
8,318
Indexes
2,282
Mining templates
1,019
### validation.cpp is mostly the machine around the checks
The file is 4,247 code lines. CheckBlock, ConnectBlock's checks, the subsidy, and BIP30 stay with the rules. The undo write stays with chainstate. MemPoolAccept stays with policy.
validation.cpp, 4,247 code lines
ChainPoolRules
Chainstate machine
2,645
Mempool acceptance
997
Validity checks
562
Progress and errors
43
---
## VI. Tests
Tests are 154,273 code lines, about as many as the implementation.
Test lines per implementation line, scaled to the rules
Rules
1.47
The rest
1.01
Adjacent
0.88
Test lines by bucket, scaled to everything else
The rest
121,558
Adjacent
17,840
Rules
14,875
Rule and adjacent tests, scaled to mempool and policy
Mempool and policy
8,073
Mining and indexes
6,746
Rule functional tests
5,375
Named rule unit and fuzz
4,517
Script and tx vectors
3,580
Chainstate unit and fuzz
3,021
Hash and block fuzz
1,403
The long bar is wallet, GUI, P2P transport, lint, and CI. A test that calls the interpreter under another name is in that bar.
---
## VII. Bundled code
Vendored trees sum to 112,703 code lines. **89,312** (79%) are maintained as Bitcoin Core projects. **23,391** (21%) are forks of Google libraries. secp256k1 is most of the first group, and it is 7.6 times the first-party rules.
Bundled code lines, scaled to libsecp256k1
secp256k1
76,503
leveldb
21,721
libmultiprocess
5,540
minisketch
4,534
univalue
2,033
crc32c
1,670
ctaes
702
Since the projects split, Google has changed leveldb about ten times as much as this fork has. crc32c has barely moved on either side.
Lines changed since the shared ancestor, scaled to Google's leveldb history
leveldb, Google
+2,335−1,886
leveldb, the fork
+242−194
crc32c, Google
+54−38
crc32c, the fork
+46−24
Qt, Boost, SQLite, ZeroMQ, Cap'n Proto, qrencode, and systemtap are fetched when the node is built. They are not in this checkout, so they have no line count here.
Public-key checks in `src/pubkey.cpp` call into secp256k1. That library is a Core project, used by other software, and it sits outside the node's own source.
---
## VIII. Who added the lines
**1,122,543** lines were added and **614,627** were deleted. **55%** of what was added was later deleted. Net is added minus deleted. It is not the lines still in the tree. That count is section IX. The filter is code files only. Comments and blanks count. Vendored trees, Qt translations, and build scripts do not.
Of the lines added to code files, through 26 October 2026
55% deleted45% net
Added
+1,122,543
Deleted
−614,627
Net
+507,916
Lines added and deleted, by year
AddedDeleted
Thousands of lines, rounded. The largest net is 2020, at 44,625. 2010's net is 3,185.
Code commits by year
The peak is 2,606 commits in 2020.
Distinct people by year
The peak is 144 people in 2018. 2023 falls to 76.
Lines added by person, bulk imports omitted, scaled to Pieter Wuille
Pieter Wuille
132,987
Wladimir
97,885
Marco Falke
72,530
Ava Chow
61,034
Satoshi Nakamoto
50,604
Gavin Andresen
42,191
900 people, after dropping two bulk imports, sirius-m and Vinnie Falco. The top five added 39.5%. The top ten added 52.3%. Satoshi's row is the git string s_nakamoto.
Lines added and deleted by person, scaled to Pieter Wuille
AddedDeleted
Pieter Wuille
+132,987
−59,517
net +73,470 · 1,703 commits · deletes 45%
Wladimir J. van der Laan
+97,885
−47,828
net +50,057 · 1,337 commits · deletes 49%
Marco Falke
+72,530
−61,422
net +11,108 · 2,879 commits · deletes 85%
Ava Chow
+61,034
−41,384
net +19,650 · 1,274 commits · deletes 68%
Satoshi Nakamoto
+50,604
−45,881
net +4,723 · 237 commits · deletes 91%
Gavin Andresen
+42,191
−36,796
net +5,395 · 393 commits · deletes 87%
John Newbery
+24,882
−26,142
net −1,260 · 749 commits · deletes 105%
Suhas Daftuar
+24,723
−8,580
net +16,143 · 438 commits · deletes 35%
Russell Yanofsky
+22,958
−13,286
net +9,672 · 414 commits · deletes 58%
Gloria Zhao
+19,444
−5,951
net +13,493 · 390 commits · deletes 31%
Michael Ford
+19,053
−17,676
net +1,377 · 601 commits · deletes 93%
Ryan Ofsky
+17,697
−6,601
net +11,096 · 272 commits · deletes 37%
Michael Ford's small net skips build scripts. His merge share is a different ranking, in *[Who Controls Bitcoin](/articles/bitcoin-governance)*.
---
## Where the work went
The 55% figure above counts every filtered code file, including tests. Restricted to implementation files, and split with the same system lists as section III, **672,059** lines were added and **431,312** were deleted. **64.2%** of what was added was later deleted. No system has a majority. Wallet is the largest share of lines added, at **14.9%**. Validation is **14.8%**. The top four, wallet, validation, the GUI, and P2P, are **55.3%**.
Implementation lines added and deleted, scaled to the wallet
AddedDeleted
Wallet
+100,177
−71,056
net +29,121 · 4,074 commits · 14.9%
Validation
+99,577
−67,991
net +31,586 · 4,295 commits · 14.8%
GUI
+91,333
−65,302
net +26,031 · 3,070 commits · 13.6%
P2P
+80,675
−51,106
net +29,569 · 3,382 commits · 12.0%
RPC and HTTP
+63,238
−39,140
net +24,098 · 3,142 commits · 9.4%
Support
+59,510
−33,237
net +26,273 · 2,630 commits · 8.9%
Crypto
+36,031
−20,597
net +15,434 · 969 commits · 5.4%
Script
+34,561
−19,247
net +15,314 · 958 commits · 5.1%
Mempool
+24,463
−11,426
net +13,037 · 1,093 commits · 3.6%
A commit that touches two systems is counted in both commit totals. The lines are a partition.
The early years are the GUI. In 2009–2013 the GUI is **28.7%** of implementation lines added. Wallet is the plurality in 2018–2021, at **26.3%**. From 2022 through 26 October, validation leads, at **16.2%**, and the GUI's net is **+261**. Wallet is the largest tree today because older lines survived.
Share of implementation lines added, by era
2009–2013
2014–2017
2018–2021
2022–2026
■ GUI■ Validation■ Wallet■ P2P■ RPC■ Support■ Mempool■ The rest
---
## What changes in the same commit
**61.0%** of wallet commits touch no other implementation system, and **13.7%** of them also touch validation. The tight pair is mempool and validation: **36.7%** of mempool commits also edit validation. RPC is the least separate. It is alone in **45.9%** of its commits, and those commits also touch validation **23.6%** of the time and wallet **23.2%**.
Share of a system's commits that touch no other implementation system
GUI
66.8%3,070 commits · wallet 17.7%
Wallet
61.0%4,074 commits · RPC 17.9%, validation 13.7%
P2P
60.3%3,382 commits · validation 20.8%, RPC 15.9%
Validation
52.5%4,295 commits · RPC 17.3%, P2P 16.4%
Support
49.5%2,630 commits · validation 23.8%, P2P 20.1%
Crypto
49.1%969 commits · support 26.7%, validation 26.6%
In the last three years the GUI fell to 47% alone. Wallet stayed near 68%, and validation near 62%.
---
## IX. Who last touched what remains
`git blame -w` on the 756 implementation files. Each non-blank line goes to the last commit that changed it. `validation.cpp` is split on the same function boundaries as section IV. Comments count, so these totals sit above the tokei code lines: 12,734 non-blank rule lines against 10,122 code lines.
Who last touched the rule lines, scaled to Pieter Wuille
Pieter Wuille
44.2%
Jorge Timón
12.4%
Anthony Towns
5.4%
Marco Falke
3.8%
Cory Fields
3.3%
Wladimir
3.3%
Johnson Lau
3.0%
Largest share of the lines that remain, scaled to the rules
Rules, Pieter Wuille
44.2% · 2017
Adjacent, Pieter Wuille
24.1% · 2023
The rest, Ava Chow
11.4% · 2021
Pieter Wuille last touched 13.9% of all 187,516 non-blank implementation lines, against 44.2% of the rules. Satoshi's author string leads a large share of historical additions and is absent from the lines that remain. Who would make the next change is the next section.
---
## Who still edits a system
Over the three years ending 26 October 2026, validation's 798 commits come from 66 people, and seven of them cover half. Lőrinc is 15%. Marco Falke is 10%. TheCharlatan, including commits signed sedited, is 9%. Mempool is the concentrated system: Pieter Wuille is 36% and Suhas Daftuar is 12%, just under half together, and three people cover half. Wallet takes three people to reach half. Ava Chow, including commits signed Andrew Chow, is 31% of them.
Largest share of a system's commits, last three years, scaled to mempool
Mempool, Pieter Wuille
36%
Wallet, Ava Chow
31%
Script, Ava Chow
29%
Support, Marco Falke
24%
GUI, Marco Falke
20%
P2P, Gloria Zhao
17%
Validation, Lőrinc
15%
People editing each system, last three years, scaled to RPC
RPC
737 to half · top three 33% · 562 commits
Validation
667 to half · top three 34% · 798 commits
Wallet
633 to half · top three 52% · 665 commits
P2P
587 to half · top three 37% · 549 commits
Support
585 to half · top three 43% · 539 commits
Mempool
403 to half · top three 58% · 401 commits
GUI
343 to half · top three 52% · 197 commits
Script
343 to half · top three 52% · 174 commits
Crypto
325 to half · top three 39% · 178 commits
The rule files are their own count. In the same three years, **169** commits touch them, from **31** people, and **five** cover half. Marco Falke is 18%. Anthony Towns and Lőrinc are the next two, and the three together hold 42%. Pieter Wuille's 44.2% is the text that remains, and the median of those lines is 2017. These recent commits are a different list. The 562 check lines inside `validation.cpp` are left out of this count. That file is mostly chainstate and mempool.
People to cover half the commits, last three years, scaled to validation
Validation
766 people · Lőrinc 15%
Rule files
531 people · Marco Falke 18%
Mempool
340 people · Pieter Wuille 36%
Wallet
363 people · Ava Chow 31%
Two git names that share an email are one person. RPC has the most people, 73. The GUI is the quiet tree, 197 commits.
---
## The size of the contract
At this release the tree exposes **171** RPC methods, **36** P2P message types, and **5** named deployment slots. Named slots went 1, 5, 6, then 5. Taproot left the named list. The rule is still in the interpreter.
RPC methods and P2P message types, end of each era
RPC methodsP2P messages
---
## X. Patch debt
The January 2026 debt study scores a file from how often it is edited in small diffs and how long it has gone without a large rewrite. This is the same formula, rerun on **17,072** merged pull requests through 12 October 2026. It is a churn score. It is not a bug count.
Counting every path that history ever touched, including files that are gone, **28.2%** score above 50 and the patch-to-refactor ratio is **3.0**. RPC is 63% of that wider count.
Restricted to files still in this tree, **15.8%** of files score above 50, and those files hold **10.2%** of current code lines. High-scoring files are smaller than average. Many of the old high scores were paths that no longer exist (`main.cpp`, `ui.cpp`). Among living files the ratio is **3.6** patches per refactor. Wallet is **6.9** to 1. The study's own consensus bucket, 26 files, is patched once per refactor, and 42% of those files still score above 50. That bucket is not the 10,122 rule lines.
Living files scoring above 50, scaled to the study's consensus bucket
Consensus files
42.3%
Wallet
25.5%
RPC
23.9%
Script
18.9%
GUI
14.5%
Network
12.7%
---
## XI. What the count is for
The rules that have to be specified, audited, and matched by any other implementation are 10,122 code lines, plus a signature library that is larger than they are. The program operators download is the other 93% of the implementation, the tests, and the bundled trees. Treating a release as "the consensus rules" collapses those piles.
*[Don't Trust, Verify](/articles/dont-trust-verify#vi-the-same-system-applied-to-bitcoin-core)* is about that collapse at the review layer. The first independent audit of Bitcoin Core, Quarkslab in September 2025, scoped P2P, mempool, block validation, and chain state. Those are mostly the adjacent lines in section V, plus some of the checks. The interpreter, the hash implementations, and the type of the transaction are the rest of the 10,122, and secp256k1 is another 76,503.
*[Who Controls Bitcoin](/articles/bitcoin-governance)* measures who merges. This article measures who wrote lines and who last touched the lines that remain. The rankings differ. Merge concentration answers who can land a change. The blame in section IX answers whose text is still in the rule files. Both can be true, and neither is a substitute for the other. The later sections answer three further questions. Wallet commits also touch validation 13.7% of the time. Over the last three years, the rule files' 169 commits come from 31 people, and five cover half. Validation's wider tree comes from 66. A release exposes 171 RPC methods, 36 P2P message types, and 5 deployment slots.
*[Bitcoin Core: The Biggest Fallacies](/articles/bitcoin-core-the-biggest-fallacies)* argues the client is a monolith because the wallet, the network, and the rules ship together. The line count is the size of that claim. Seven percent is the rules. Eighty percent is the rest of the same binary.
*[What Bitcoin's Stalled Proposals Tell You](/articles/what-bitcoins-stalled-proposals-tell-you)* uses the authorship Gini from the governance research. That Gini is on pull-request authorship. The added-line shares in section VIII are a third cut. Top-five line additions at 39.5% and a historical authorship Gini near 0.85 are the same shape at two resolutions. They are not the same number.
The cost of storing the chain this program validates is a separate account, in *[Full Cost of Running a Bitcoin Node](/articles/full-cost-of-running-a-bitcoin-node)*.
---
## XII. Method
**Snapshot.** Bitcoin Core **32.1**, branch `32.x`, commit `f0de87f040621468b956f01f526a43a010310501`, 26 October 2026, "Merge bitcoin/bitcoin#36658: [32.x] Finalise 32.1". The tag matches the branch tip. Not shallow. 50,657 commits, 16,987 of them merges. Line counts are this release. Authorship is history through this commit.
**Code lines.** tokei 14.0.0. A file is in one bucket. Implementation is `src/` excluding vendored prefixes (`secp256k1`, `leveldb`, `crc32c`, `minisketch`, `univalue`, `libmultiprocess`, `ctaes`), Qt locale, tests, fuzz, bench, markdown, and `CMakeLists.txt`. The system split uses explicit file lists for `src/node`, because that directory is not all P2P. `src/node/mining_args.cpp`, `mining_args.h`, and `mining_types.h` are in mining templates.
**Forks.** leveldb in this release is `13da2d67` (11 August 2026). The shared ancestor with Google is `0c40829` (5 November 2019). The Google tip in the comparison is `bb74ef73` (8 October 2026). crc32c is `efb8ea04` (30 August 2024), ancestor `21fc8ef` (8 February 2022), Google tip `2bbb3be` (7 April 2025). The bars are git numstat and include comments and blanks.
**The three-way cut.** Rule files are the SHA-256 and RIPEMD-160 sources, `hash.cpp` and `hash.h`, the script interpreter and script data, `pubkey`, `arith_uint256`, `uint256`, `src/primitives`, `src/consensus`, proof of work, versionbits, deployments, and signet. `validation.cpp` is split by function start, comment-stripped, then scaled from 4,187 raw code-like lines to tokei's 4,247. Adjacent is chainstate and storage, policy and mempool, indexes, and mining templates, including the matching parts of `validation.cpp`. SHA-1, SHA-3, and SHA-512 stay in the rest. The three parts sum to 151,004.
**Tests.** The named rule unit and fuzz files are the earlier filename list (4,517) plus integer, hash, script, and block tests that name a rule type (1,403). Functional rule tests are an explicit basename list: `feature_block`, `feature_taproot`, `feature_segwit`, `feature_cltv`, `feature_csv_activation`, `feature_dersig`, `feature_nulldummy`, `feature_bip68_sequence`, `feature_signet`, `feature_versionbits_warning`, `p2p_segwit`, `p2p_invalid_block`, `p2p_invalid_tx`, `p2p_mutated_blocks`. Adjacent adds an explicit list of mining, assumeutxo, pruning, index, fee, package, and chainstate tests to the mempool and policy filename prefix. A test outside those lists stays in the rest. That undercounts a functional test that exercises the interpreter under another name.
**History.** `git log HEAD --no-merges --numstat`. Renames of the form `{old => new}` are rewritten to the new path. Identity merges every pair of git names that share an email, and one name that used two addresses, plus the published aliases: Wladimir's three spellings, Ava Chow and Andrew Chow, Marco Falke and MarcoFalke, Gloria Zhao and glozow, Michael Ford and fanquake, jtimon and Jorge Timón. The tables use the release-note names. Satoshi Nakamoto's row is the s_nakamoto string. People who share only a first name stay separate. Ryan Ofsky and Russell Yanofsky are different people.
**Systems over time.** The same numstat history, implementation paths only, classified with the section III file lists, including the explicit `src/node` split. A path is classified by the name it had in that commit. Vendored trees and tests are out. The era chart uses that same partition in four spans: through 2013, through 2017, through 2021, and from 2022 through this release. Crypto, script, and the smaller systems are the remainder of each bar. A commit that touches two systems counts in both commit totals. "Only this system" means the commit touched no other classified implementation system. The three-year window is author dates from 26 October 2023 through this release. The people column merges git names that share an email, and the same published aliases as the history.
**Rule-file editors.** The same window and the same person merge. A commit counts once when it touches a file in the section IV rule list: the SHA-256 and RIPEMD-160 sources, `hash.cpp` and `hash.h`, the script interpreter and script data, `pubkey`, `arith_uint256`, `uint256`, `src/primitives`, `src/consensus`, proof of work, versionbits, deployments, and signet. `validation.cpp` is left out. Its 562 check lines share the file with chainstate and mempool.
**The contract.** RPC names are the command table when that table carries the method name (2013 and 2017) and `RPCHelpMan` / `RPCMethod` constructors when it does not (2021 and this release). Hidden methods are included. P2P names in 2013 are the message strings the network dispatcher in `src/main.cpp`, `src/net.cpp`, and `src/alert.cpp` receives or sends. From 2017 on they are the `NetMsgType` strings. Deployment slots are `DEPLOYMENT_*` enumerators other than testdummy, plus the block-version-2 height rule, with height-field aliases of the same fork collapsed to one name. Era tips are the last commit on this history at the end of 2013 (`aec55a07`), 2017 (`c9439e73`), 2021 (`1831d43e`), and this release.
**Blame.** `git blame -w --line-porcelain` on each implementation file. Whitespace-only changes do not move the line. Blank lines are dropped. The same alias list as the history.
**Debt.** `scripts/analysis/code_turnover_analysis.py` in the Bitcoin Governance Research repository, run on `data/github/prs_raw.jsonl` (25,506 pull requests, 17,072 merged with a date, last merge 12 October 2026). The score weights patch frequency, time since a large rewrite, age of files the script labels consensus, and modifications per estimated line. Change type is a size heuristic: a refactor is a change over 30% of the estimated file or over 200 lines. The script's subsystem labels are filename patterns. They are not the three-way cut in section IV. Living-file membership is the 32.1 tree.
---
## Sources
- Bitcoin Core 32.1, commit [`f0de87f040621468b956f01f526a43a010310501`](https://github.com/bitcoin/bitcoin/commit/f0de87f040621468b956f01f526a43a010310501), branch `32.x`, 26 October 2026
- [tokei](https://github.com/XAMPPRocky/tokei) 14.0.0, file-level report on that tree
- [Bitcoin Governance Research, technical debt analysis](https://github.com/secsovereign/bitcoin-governance-research/blob/master/findings/TECHNICAL_DEBT_ANALYSIS.md), formula rerun 30 October 2026 on the pull-request dump through 12 October 2026
- *[Who Controls Bitcoin](/articles/bitcoin-governance)*, *[The Vertical Layer Problem](/articles/the-vertical-layer-problem)*, *[Why Bitcoin Needs a Specification That Humans Can Read](/articles/why-bitcoin-needs-a-specification)*, *[Don't Trust, Verify](/articles/dont-trust-verify)*, *[Bitcoin Core: The Biggest Fallacies](/articles/bitcoin-core-the-biggest-fallacies)*, *[What Bitcoin's Stalled Proposals Tell You](/articles/what-bitcoins-stalled-proposals-tell-you)*, *[Full Cost of Running a Bitcoin Node](/articles/full-cost-of-running-a-bitcoin-node)*
---
# Who Governs Bitcoin's Code, and Why Diligence Doesn't Ask
*Disclosure. The author builds Bitcoin Commons, an alternative Bitcoin implementation discussed near the end of this piece. The quantitative record comes from the author's [Bitcoin Governance Research](https://github.com/secsovereign/bitcoin-governance-research), a public repository with its methodology and datasets, and its definitions and limits are summarized in the methodology section.*
## Key findings
- Bitcoin ETF prospectuses disclose that a "loose community" of "core developers" informally manages the protocol's source code. The public record shows that community is a few dozen sustained contributors, and five people hold the keys that merge code.
- Bitcoin Core's written process sets no review minimum. Maintainers merged their own pull requests in about a quarter of their merges over the project's history, and in one in five during 2025.
- Measured against controls regulated firms already apply, SOX change management, SLSA two-person review, and DORA exit planning, Core meets none as written policy, though its practice has improved sharply since 2016.
- The supply cap has failed once and nearly failed again. A 2010 bug created 184 billion bitcoin, and a 2018 bug would have let a miner inflate supply. A small group of developers fixed both within a day.
- Every bitcoin ETF, custodian, and treasury company depends on the same software lineage, so switching products does not diversify the risk.
- Diligence teams can price this today as a governance modifier on position size, using the seven questions at the end.
## Funds disclose the risk and stop there
US spot bitcoin ETFs held [$111.09 billion in net assets](https://pro.edgex.exchange/en-US/news/article/us-bitcoin-etf-assets-inflows-2026) as of October 8, 2026. Their prospectuses say who maintains the software that defines what they hold. The [iShares Bitcoin Trust prospectus](https://www.sec.gov/Archives/edgar/data/1980994/000143774924025254/bit20240805_424b3.htm) states that "a loose community known as the core developers has evolved to informally manage the source code," that membership evolves "largely based on self-determined participation," and that the core developers "are generally not compensated." The disclosure names a dependency, and the diligence that follows rarely asks who those people are, what controls govern their changes, or what happens when the controls fail.
The wording matters, and it varies by issuer in ways that tell a diligence team something. The iShares prospectus never names Bitcoin Core and writes "core developers" in lowercase, as whoever manages "the source code for the protocol." The [ARK 21Shares prospectus](https://www.sec.gov/Archives/edgar/data/1869699/000121390024045915/ea0205576-02.htm) uses nearly the same sentence, that "a loose community of core developers has evolved to informally manage the source code for the protocol," and elsewhere in the same filing says the network's infrastructure "is collectively maintained by a decentralized user base." The [Grayscale Bitcoin Trust 10-K](https://www.sec.gov/Archives/edgar/data/1588489/000095017025029408/gbtc-20241231.htm) says bitcoin has "no official developer or group of developers that controls the Bitcoin Network," and then that "the Bitcoin Network's development is overseen by a core group of developers." [Fidelity's 10-K](https://www.sec.gov/Archives/edgar/data/1852317/000119312526071484/ck0001852317-20251231.htm) is the only one of the four to name the project. It describes the developers of "a specific distribution of Bitcoin network software" known as "Bitcoin Core," calls it "the de facto standard," and says the core developers are "responsible for quasi-official releases." Read together, the filings treat the maintainers of one implementation as the stewards of the protocol, and the most specific of them says so outright.
## The loose community is small enough to count
BTCDecoded contributor analysis of Bitcoin Core GitHub history, 2010 to 2026, and the 1A1z Funding Bitcoin report (October 2024). Established authors are counted over all time.
The public record lets the "loose community" be counted, and each step down the chart is a narrower definition of who does the work. Nearly 8,000 people have contributed at some point, 42% of them exactly once, and the set that sustains the project numbers in the dozens. Five of them hold the keys.
Core's own [contributing guide](https://github.com/bitcoin/bitcoin/blob/master/CONTRIBUTING.md) disowns the category the prospectus relies on. It says "there is no particular concept of 'Bitcoin Core developers' in the sense of privileged people," and then names the exception, "repository maintainers who are responsible for merging pull requests." The two documents describe the same structure from opposite ends. The issuer discloses a loose community with authority over the protocol's source code, the project says the only people with special authority are its maintainers, and the data says those maintainers number five.
The same funds hold their coins under custody arrangements examined down to the signing policy. Diligence asks who holds the keys to the coins and leaves unasked who holds the keys to the code.
## The asset is the rules, and the rules are code
A bitcoin is a balance that nodes accept as valid under rules written in software. The properties an allocator underwrites, a fixed supply, exclusive control of coins, and confidentiality of the holder's activity, hold only while that software enforces them correctly, so a change to the software is a change to the asset.
Bitcoin Core's record has a defect touching each of those properties. In versions 0.15 through 0.16.2, a removed check meant a miner could have inflated the supply by spending the same output twice. It was reported privately and fixed before anyone exploited it. In January 2026 the project pulled the binaries for versions 30.0 and 30.1 after finding that a failed wallet migration could delete every file in the wallet directory, "potentially resulting in a loss of funds." In version 31.0, the new private broadcast feature sometimes made connections over clearnet instead of the privacy network it was configured to use, which exposed the sender's IP address until version 31.1 fixed it. The consensus rules are a small part of the program, about 7% of Core's implementation, or 10,122 of 151,004 lines in version 32.1. The other 93%, the wallet, networking, interface, and the code that stores and relays what the rules accept, can reach a holder just as directly, and review has to cover all of it.
## What a software failure does to a fund
The cost of a defect reaches a fund through its own operating terms. Take the case the record shows is possible, a consensus bug that splits the chain, as the 2013 version 0.8 release did when upgraded and older nodes followed different chains. For as long as a split lasts, two ledgers each claim to be bitcoin, and a custodian has to decide which one its client balances live on.
The iShares prospectus anticipates this. It lets the trustee suspend redemptions when delivering bitcoin is not reasonably practicable, including after a "significant technical failure, bug, error, disruption or fork of the Bitcoin network," and it commits the trust to "permanently and irrevocably abandon" any rights to assets a fork creates. A shareholder in that position cannot redeem for coins, holds a claim on whichever chain the sponsor and custodian treat as bitcoin, and forfeits the other. With redemptions closed, the arbitrage that keeps an ETF's price near its net asset value stops working, so the share price can drift from the value of the coins behind it.
Wallet and privacy defects reach a fund another way. Custodians and issuers that run node software for validation or broadcasting inherit its defects, so a wallet bug can touch the funds they control and a privacy flaw can expose transaction flow that their clients expect to stay confidential.
The exposure is also correlated in a way allocators rarely see. Every US spot bitcoin ETF, every custodian, and every corporate treasury holding bitcoin depends on the same chain, and almost all of them validate it with software from one lineage. A failure in that software reaches every product at once, so moving between issuers or custodians diversifies counterparty risk and leaves this one untouched.
The supply cap has already failed once. In August 2010 a bug let a single transaction create more than 184 billion bitcoin. A patched client shipped within five hours, and the corrected chain overtook the bad one the next day. The 2018 bug came close to a repeat and was caught only because a developer of a competing implementation reported it privately. Both times, a supply that cannot inflate, the asset's defining property, was restored by a small group of developers acting fast, which is the arrangement this piece asks diligence to examine.
The 2018 response also shows who decides what holders learn. The project's own notice says the team chose "to immediately patch and disclose the less serious Denial of Service vulnerability" and held back the inflation flaw for three days "to give times for systems to upgrade." That was a defensible security call. It was also a decision about material information, made by a handful of people under no written procedure, with no one in the room for holders.
## Core fails the controls a firm applies to every other critical system
A regulated firm already holds its critical software to three tests. Bitcoin Core meets none of them as written policy, though its current practice meets parts of them.
| Control the firm already applies | What it requires | Bitcoin Core |
| --- | --- | --- |
| Change management under SOX IT general controls | No single person can develop, approve, and deploy a change | Maintainers merged their own pull requests in 2,501 of 9,793 maintainer merges, and no written rule bars it |
| SLSA source integrity, Level 3 | Every change approved by two trusted persons before submission | No written review minimum, though zero-review self-merges fell from 83.9% of self-merges in 2016 to 4.0% in 2026 |
| ICT third-party risk under EU DORA | An assessment of concentration risk and a documented exit strategy | Core or code derived from it runs on most nodes, with no independent specification to exit against |
The third test shows the deepest gap. DORA's Article 28 says that "for ICT services supporting critical or important functions, financial entities shall put in place exit strategies," and third-party risk programs enforce that through contracts, with audit rights, service levels, and termination clauses. Bitcoin Core has no CEO or foundation, no contract, and no counterparty, so the most critical dependency in a bitcoin position sits outside the program built to catch it.
Bank capital rules already treat the network as something to assess. Under the Basel Committee's cryptoasset standard, SCO60, an asset qualifies for the lightest treatment only if its network is "designed and operated to sufficiently mitigate and manage any material risks." Bitcoin falls into the harsher Group 2 on other grounds, since it has no stabilization mechanism, so the network question never gets asked of it. The standard names the question, and no bank has to answer it for bitcoin.
## Five people hold the merge gate, and their duties to holders are unsettled
Five trusted-key holders can merge code into Core's main branch, and the existing maintainers decide who joins them. Over the full record, 23 GitHub logins have used merge keys, and three of them performed three-quarters of all merges. Node operators install releases without auditing them and rely on the maintainers' review, which makes that review the last control before code reaches the network.
BTCDecoded cross-repository comparison, merged_by field on 16,845 merged Bitcoin Core pull requests, 2010 to 2026.
The all-time share understates the gate as it works today, because the top three changed over the years. In every year since 2013, the three most active mergers performed between 88% and 97% of that year's merges, including 90.3% in 2025 and 91.2% so far in 2026. Since 2022 a single maintainer has merged half of all pull requests. In any given year, about nine in ten changes that reach Bitcoin Core pass through three people's hands, and the same holds at the last step before installation, where [three people signed 90.1% of the releases whose signers are recorded](/articles/bitcoin-governance).
No written procedure governs who joins the group. When a contributor proposed documenting the maintainer list and selection process in 2023, a long-time contributor described the process as "someone puts their name forward, it is discussed at a IRC meeting, they open a pull request," and objected to shoehorning the project "into a formal company structure" ([#26868](https://github.com/bitcoin/bitcoin/pull/26868)).
Counsel will recognize the shape as key-person dependence with no employment agreement, no succession plan, and no settled duty running to holders. In 2023 the English Court of Appeal held in [Tulip Trading v van der Laan](https://caselaw.nationalarchives.gov.uk/ewca/civ/2023/83) that whether Bitcoin developers owe fiduciary duties to coin owners was a serious issue to be tried. The claimant [discontinued the case](https://www.lexisnexis.com/en-gb/legal/news/bitcoin-inventor-drops-case-against-software-developers) in 2024, so the question remains open, and a holder has no established legal claim on the people who change the rules of the asset.
Legal scholarship reached this point years ago. Angela Walch argued that "the core developers and significant miners of public blockchains function as fiduciaries" ([In Code(rs) We Trust](https://commons.stmarytx.edu/facarticles/613), 2019), and that the word "decentralized" can work as "a liability shield for those operating the systems (developers and miners)" ([Deconstructing 'Decentralization'](https://papers.ssrn.com/abstract=3326244), 2019). She also warned that misreading where power sits produces inaccurate risk assessments of the assets built on these systems, which is the error this piece asks diligence teams to correct.
The law is moving toward fewer obligations for developers. The CLARITY Act, which passed the House in July 2025, carries the Blockchain Regulatory Certainty Act in its Senate text and would shield non-custodial developers from money-transmitter and Bank Secrecy Act obligations. The bill failed a Senate cloture vote 49 to 50 on September 15, 2026, and no new vote is scheduled. The provision concerns licensing, not fiduciary duty, and its direction is still clear. Policy treats developers as publishers of software, so any control over how they change it will have to come from the project or from the institutions that rely on it.
## How rule changes get decided
Merge statistics show who approves code. Changes to the rules show how contested decisions get made, and they follow no written procedure either. Taproot, the most recent consensus upgrade, locked in in June 2021 under a "Speedy Trial" mechanism that required 90% of blocks in a signaling period to support it, after months of public argument over how activation should work. The method was chosen for that upgrade and binds none that come after it.
Policy changes, which alter what a node relays without changing consensus, need less. Version 30, released in October 2025, removed the default 80-byte limit on OP_RETURN data. Critics, among them developer Luke Dashjr and Nick Szabo, warned that it invited spam and permanent storage of illicit data, and one lawyer argued that a change this contested should not ship bundled with security fixes. The maintainers shipped it. Over roughly four months, Bitcoin Knots, a Core derivative that kept the limit, rose from about 4% to about 21% of the nodes counted by coin.dance. The episode shows the decision process as it actually runs. The maintainers judge rough consensus, and an operator who disagrees can switch to a different build of the same code.
The next contested change is already in the filings. BlackRock's July 2025 iShares prospectus warns that quantum-resistant changes "could require the achievement of broad consensus within the Bitcoin network community and a fork (or multiple forks), and there can be no assurance that such consensus would be achieved or the changes implemented successfully." A migration of that size will run through the same unwritten process that took Taproot years, and the largest issuer has already told its investors the result may be a split chain.
## Who pays for the work
The prospectus line that developers are "generally not compensated" understates how the work is funded. A 2024 report by the research group 1A1z, Funding Bitcoin, counted $8.4 million spent on Core developers in 2023, spread across 13 sponsoring organizations, and found 41 developers with at least five commits in 2024. Two grant-makers, OpenSats and Spiral, provided 62% of grant funding, and Chaincode Labs accounted for 46% of employment spending. Eight sponsors depend entirely on donations, and the top three of those receive 62.25% of their funding from a single source.
Diligence asks about funding concentration because it is how influence enters an organization without a vote. The people who control the merge gate depend on a small number of discretionary grants, many renewed annually, with no disclosure owed to holders. A 2023 budget of $8.4 million maintains software that now secures $111 billion in US ETF assets alone.
## Review practice has improved, and it rests on custom
BTCDecoded Bitcoin Core governance research, TEMPORAL_ANALYSIS_REPORT, 2016 to 2026 to date (2026 is a partial year). GitHub review records exist from 2016.
Since GitHub review records begin in 2016, average review depth on maintainer-merged pull requests has risen from 1.0 to 7.8, and zero-review self-merges have fallen from 83.9% of self-merges to 4.0%. Active reviewers grew from 22 to 94 by 2021, and pull requests per reviewer fell from 71 to 21. A 2025 [Quarkslab audit](https://blog.quarkslab.com/bitcoin-core-audit.html) called Core the most mature and well tested codebase its engineers had assessed and found no high-impact issues in its peer-to-peer scope.
Incident handling has matured too. Since 2024 the project has published [security advisories](https://bitcoincore.org/en/security-advisories/) under a written disclosure policy that ranks bugs from low to critical and sets disclosure timelines for each grade. The list now holds 28 entries, one of them critical, the 2018 inflation bug. The policy also says critical bugs fall outside its standard timelines and would need an ad hoc procedure, so the most serious class of defect still has no written process.
Diligence should credit all of it, and should also notice what holds it in place. Core's contributing guide sets no numeric review minimum and leaves merge decisions to the maintainers' judgment of contributor consensus. Review stays concentrated, with a Gini coefficient of about 0.93 and the top ten reviewers producing 39% of reviews since 2021. A control that exists as the habit of a small group lasts as long as that group does, and nothing in the written process obliges the next group to keep it. Set beside sixteen other Bitcoin repositories on a shared health index, Core's rank moves with how size is handled, so the finding concerns missing written rules and not measured underperformance.
The gap between the rule as described and the rule as written shows up in the project's own funders. Brink, one of the largest funders of Core developers, told supporters in its 2025 engineering report that "every change to Bitcoin Core must be carefully reviewed by multiple qualified developers before it can be merged." That describes a two-person rule. The contributing guide contains no such requirement, and in 2025 one in five maintainer merges was the maintainer's own pull request.
The developers describe the shortage in their own words. Pieter Wuille wrote in 2024 that "review is the biggest bottleneck for our project" ([#29473](https://github.com/bitcoin/bitcoin/pull/29473)). Anthony Towns warned in 2021 that the shortage creates "an incentive to get in the habit of merging code that's not thoroughly reviewed in order to avoid delaying things because we've run out of review resources" ([#20721](https://github.com/bitcoin/bitcoin/pull/20721)). When maintainers debated self-merging in 2022, Marco Falke estimated that "about half of my changes are merged by myself" and wrote that "in the absence of several active maintainers per file/module, I fail to see how self merges could be rare" ([#25524](https://github.com/bitcoin/bitcoin/pull/25524)). The self-merge rate is what review scarcity looks like from the merge button.
The project has also considered writing the rule down. A 2022 pull request to document maintainer responsibilities ([#25560](https://github.com/bitcoin/bitcoin/pull/25560)) met pushback from contributors and maintainers who wanted it cut back to minor fixes, in part, as one contributor summarized, to avoid "a restriction that a maintainer can't merge their own PR no matter how much review it has."
Core's release process shows the project can write a multi-party rule when it chooses to. Release binaries go out only after "6 or more people have guix-built and their results match" ([release process](https://github.com/bitcoin/bitcoin/blob/master/doc/release-process.md)), so no single person can ship a binary that differs from the source. Pieter Wuille has been clear about what that control leaves out. A build attestation "isn't and shouldn't be interpreted as the builder/attester vouching for the code they are building," he wrote, because "we have the review process for that" ([#21462](https://github.com/bitcoin/bitcoin/pull/21462)). The project writes a numeric rule for the step that checks binaries against source and leaves the step that checks the source itself to custom.
## Other critical projects write the rule down
A written review rule is ordinary for security-critical open source. OpenSSL, the cryptography library that drew global scrutiny after the 2014 Heartbleed flaw, states in its [committer policy](https://openssl-library.org/policies/general/committer-policy) that "all submissions must be reviewed and approved by at least two committers" and that "neither of the reviewers can be the author of the submission." That is the SLSA two-person rule in policy form, adopted by an open-source project under the same review pressure Core faces. Core's practice now often exceeds that bar, and its written process still does not state it.
## Bitcoin's code is a commons, and a commons without rules runs down
Core's codebase is a commons that many depend on and no one owns. Its upkeep draws on two scarce inputs, reviewer expertise and the consistent application of the design principles that keep the software safe. Elinor Ostrom's study of commons that last found that durable ones share a set of design principles, and a review of 91 later studies found strong support for them. Two bear directly on Core. The people affected by the rules take part in changing them, and the people who monitor use are accountable to the users. Core has a self-selecting maintainer group and no written review rule, and the holders who bear the losses, institutions now among them, have no part in setting either.
When principles live in reviewers' heads, they get applied unevenly. The 2013 split came from a database limit that old nodes enforced and new nodes did not, and the 2018 bug from a check a later optimization judged redundant. In both cases no build step enforced a rule the network depended on.
The concentration is documented in the academic literature. Azouvi, Maller, and Meiklejohn found in 2018 that "there is usually a handful of people that accounts for most of the discussion" in Bitcoin's development. De Filippi and Loveluck concluded that "the governance of the Bitcoin project relies almost exclusively on its leaders," and Yeung and Galindo argued in 2019 that public blockchains without formal internal governance are unlikely to be taken up at scale.
The strongest scholarly counterview comes from Nabilou, who argues that Bitcoin "achieves decentralized governance by putting users at the center," because node operators can refuse to run code they reject. That veto is real for intended rule changes that users can see and debate. It does not reach a defect nobody has found, and exercising it requires an alternative implementation, which brings the argument back to the cost of exit.
## The exit option costs more than it appears
The standard answer is that operators can refuse an upgrade or switch software. Exercising that option is expensive, because the alternatives share Core's code. Bitcoin Knots, the largest, is a patch set maintained on top of Core, so the operators who left Core over version 30 still run Core's code. The 2018 bug hit Core and Knots as well as Bitcoin ABC, Litecoin, and Dash, because a flaw travels with the lineage that carries it. Core has never published a formal specification of its consensus rules, so an independent implementation has to reproduce Core's behavior from Core itself, and reimplementations have diverged in edge cases, including script validation in btcd. In the Quarkslab audit, cross-implementation fuzzing found most of its issues in the alternatives. In third-party risk terms, that is a concentration with no tested exit.
## The objections, answered
The first objection is that the system has worked for seventeen years. The record is real, and it belongs to particular people. The improvement since 2016 came from the habits of one group, and nothing written obliges its successors to keep them. Diligence treats a track record with no control behind it as reliance on management and prices it as key-person risk.
The second is that the network is decentralized. Validation is, since thousands of independent operators each check the chain. Code approval is not. Five key holders control what goes into the software most of those operators install, and the operators upgrade without auditing the diff.
The third is that anyone can review open source. Anyone can, and few do. Review has a Gini coefficient of about 0.93, and ten people produce 39% of it. The right to review is open, and the work is concentrated.
The fourth is that consensus changes need miners and users to agree. That holds for intended changes to the rules, which miners and economic nodes do gate, and it does nothing about bugs. The 2018 inflation flaw, the version 30 wallet bug, and the 31.0 privacy flaw all shipped in ordinary releases with no activation vote, because nobody intended them.
The fifth is that regulating developers would be worse than the problem. Nothing here asks a regulator to act. The questions are for allocators and counsel deciding how much exposure to take, and for issuers deciding what to disclose. A project can adopt written controls on its own, as OpenSSL did.
The sixth is that no fund diligences Linux or the internet's protocols either. A defect in an operating system can stop a firm's systems, and the firm controls that exposure through its own patching and change management. A defect in Bitcoin's consensus code changes what the firm owns, and no internal control can patch a ledger that has split.
The seventh, and the one Bitcoin developers press hardest, is that the informality is deliberate. A foundation, a board, or a charter gives courts and governments someone to sue or pressure, and diffuse authority protects the people who maintain the code. The concern is real, and investors should price the trade-off it describes, though informality has not stopped suits either, since the Tulip Trading claim named individual developers. It does not explain the missing review rule, though. A written review rule binds a process, creates no legal entity, and hands no one a new target, which is why OpenSSL can publish one.
The project's own history shows the pattern behind that defense. Bitcoin launched with an alert system whose messages, Satoshi wrote in 2010, were "signed with a private key that only I have" ([2010 post](https://satoshi.nakamotoinstitute.org/posts/bitcointalk/409/)). When it was removed in 2016, Wladimir van der Laan argued that it was "seen as a centralized point of control" and that a network-wide alert system "would also need a network-wide bureaucracy for managing it" ([#7692](https://github.com/bitcoin/bitcoin/pull/7692)). Removing it was a reasonable call. It also shows the project's settled preference, which is to remove a lever rather than write rules for it, and the merge gate is a lever no project can remove.
## A governance-aware design can be built
Bitcoin Commons, the author's project, is a design for building and governing a Bitcoin implementation under written controls. Its status is stated row by row.
| Test | Bitcoin Core today | Bitcoin Commons design | Status |
| --- | --- | --- | --- |
| Who can merge | Five trusted-key holders who choose their successors | Signature thresholds by layer, from 2-of-3 to 6-of-7, checked by a merge gate that administrators cannot bypass | Designed, enforcement off |
| How much review | No written minimum | Review periods from 14 days at the extension layer to 180 days at constitutional layers, and 365 days for consensus-rule changes | Configured, enforcement off |
| What counts as correct | Core's own behavior | An independent specification of 159 consensus rules, with 251 production functions checked against it by the Z3 solver | Built |
| Proof of compatibility | None | Differential testing against Core across chain history, targeted at about 900,000 blocks | Program exists, completion record not published |
| Cost of exit | High, with no specification | Lower, because compatibility can be tested against a specification | Depends on the row above |
The verification half is further along, and a node built from a written specification goes at the exit problem directly. The governance half is configured with enforcement switched off. Two public proofs would turn it from design into evidence, a completed full-history differential run and a fail-closed merge check on a real repository. What the design shows already is that written controls for a Bitcoin implementation can be specified.
Peter Todd raised the standard objection to specifications during the 2013 chain split. "Specifications aren't magic; they're just words on paper," he wrote, and writing one "doesn't magically make code actually follow the spec" ([2013 thread](https://bitcointalk.org/index.php?topic=153170.msg1633620#msg1633620)). For a document that sits beside the code, he was right. The Commons design binds the two mechanically. A tool called spec-lock parses the formulas in the specification and the annotated Rust functions that implement them, ties each function to its rule, and uses the Z3 solver to check that they still agree, so drift between rule and code fails verification instead of waiting for a reviewer to notice. The binding covers the 251 locked functions, not the whole node, and a rule written wrong in the specification would be locked in wrong, which is what differential testing against Core is for.
## What allocators and counsel can do now
1. Put the node software on the dependency register. Ask issuers and custodians which implementation and version they run, who approves upgrades, and whether that upgrade process falls inside their SOC 2 scope.
2. Ask who can merge changes to the software and who decides who can. For Core, five trusted-key holders who choose their successors.
3. Ask for the written review rule. For Core, none exists, and practice has improved since 2016.
4. Count independent implementations by code lineage, not by client name, and ask whether correctness is defined by a specification independent of the incumbent. For Core, most nodes run Core or its derivatives, and no formal specification has been published.
5. Ask who funds the people with merge authority and on what terms. For Core, a small number of annual grants, concentrated around one donor at the time of the 2024 report.
6. Ask how a fork would be handled. Read the issuer's redemption-suspension and forked-asset terms, and ask the custodian how it decides which chain is bitcoin.
7. Ask issuers to disclose the controls in their risk factors, beyond the existence of the developers.
S&P's corporate methodology applies governance as a modifier that moves a rating by notches, and Fisher's 15 points treat management integrity as a veto. The answers can be scored the same way, as a modifier on position size by default and as a gate when nothing independent can verify the software. They also need re-running on a schedule, because they depend on a small group of people.
## The risk is disclosed, measurable, and unpriced
Every major issuer already tells investors that a small, informal group maintains the software their product depends on. The public record shows how small that group is, how it reviews and merges code, and where its written rules stop. The controls needed to price the exposure, change management, two-person review, exit planning, and governance modifiers, are ones a regulated firm already applies to every other critical system. Applying them to bitcoin needs no new framework, and the questionnaire below puts them in the form diligence teams already use.
## Appendix. Questionnaire items
The seven questions, written for an operational due diligence questionnaire sent to an issuer, custodian, or treasury company.
| Topic | Question | What a strong answer shows |
| --- | --- | --- |
| Software dependency | Which node implementation and version do you run to validate client holdings, and who approves upgrades? | A named implementation and version, a written upgrade policy with a named approver, and the upgrade process inside SOC 2 or equivalent audit scope |
| Merge authority | Who can merge changes to that software, and how are they chosen and removed? | Named people or roles and a documented admission and removal process |
| Review rule | What written rule sets the minimum review before a change merges? | A published two-person or stricter rule that excludes the author as a reviewer |
| Implementation diversity | How many independent implementations validate the chain you hold, counted by code lineage? | At least one implementation not derived from the incumbent's code, and a plan to test against it |
| Specification | Is correctness defined by a specification independent of the incumbent implementation? | A published specification and a record of compatibility testing against it |
| Funding | Who funds the people with merge authority, and on what terms? | Named funders, multi-year terms, and no single source above a stated share |
| Fork handling | If the chain splits, how do you decide which chain is bitcoin, and what happens to redemptions? | A written fork policy naming the decision-maker, the criteria, and the timeline for telling clients |
The last item maps to the redemption-suspension and forked-asset terms in each issuer's prospectus, so counsel can test the answer against the filing.
## Methodology
The quantitative record comes from Bitcoin Governance Research, an analysis of Bitcoin Core's public history covering 25,122 pull requests and 339 releases from 2010 to 2026, with 8,890 issues, 51,062 mailing-list emails, 430,613 IRC messages, and forum archives used for context. The repository holds the scripts, datasets, and reports behind every figure here, starting from [findings/EXECUTIVE_SUMMARY.md](https://github.com/secsovereign/bitcoin-governance-research/blob/master/findings/EXECUTIVE_SUMMARY.md).
A self-merge is a merged pull request whose author and merger are the same person, and a pull request with no recorded merger is not counted as one. Maintainer figures use a roster of maintainer logins, under which 2,501 of 9,793 roster-authored merges are self-merges. A pull request counts as zero-review when it has no GitHub review object with a state of approved, changes requested, or commented. Core publishes no maintainers file, so the 23 merge-key holders are inferred from observed merge activity.
GitHub had no review functionality before 2016, so review figures start there, and the all-time zero-review share of self-merges, 45.1%, overstates the gap in early years for that reason. Review objects also miss review done in comments, on IRC, or offline, so the counts are a floor. Sustained active contributors are those with at least five pull requests and a minimum average quality score in the contributor timeline analysis. The 17-repository peer comparison uses a shared health index without review data, and its intervals cover zero. Figures for 2026 cover a partial year. The analysis found no measurable link between self-merging and later reverts, so the argument here rests on missing controls and not on measured harm.
## Sources
Exposure and disclosure. [US spot bitcoin ETF assets, October 2026 (edgeX)](https://pro.edgex.exchange/en-US/news/article/us-bitcoin-etf-assets-inflows-2026), [iShares Bitcoin Trust prospectus, August 2024 (SEC)](https://www.sec.gov/Archives/edgar/data/1980994/000143774924025254/bit20240805_424b3.htm), [iShares Bitcoin Trust prospectus, July 2025 (SEC)](https://www.sec.gov/Archives/edgar/data/1980994/000143774925024228/bit20250731_424b3.htm), [ARK 21Shares Bitcoin ETF prospectus (SEC)](https://www.sec.gov/Archives/edgar/data/1869699/000121390024045915/ea0205576-02.htm), [Grayscale Bitcoin Trust 10-K, FY2024 (SEC)](https://www.sec.gov/Archives/edgar/data/1588489/000095017025029408/gbtc-20241231.htm), [Fidelity Wise Origin Bitcoin Fund 10-K, FY2025 (SEC)](https://www.sec.gov/Archives/edgar/data/1852317/000119312526071484/ck0001852317-20251231.htm)
Control frameworks. [Program change controls (ITGC)](https://cpaexamsmastery-com.pages.dev/isc/it-general-controls/program-changes/), [SLSA source requirements v1.1](https://slsa.dev/spec/v1.1/source-requirements), [DORA Article 28 text](https://www.springlex.eu/en/packages/dora/dora-regulation/article-28/), [Basel Committee SCO60 cryptoasset standard](https://www.bis.org/committees/bcbs/basel-framework/81562/chapter-no-footnotes.pdf), [OpenSSL committer policy](https://openssl-library.org/policies/general/committer-policy), [S&P corporate methodology](https://www.maalot.co.il/Publications/MT20240214173705.PDF), [Fisher's 15 points](https://fairvaluelabs.pages.dev/value-investing-academy/books/common-stocks-uncommon-profits/)
Legal duties. [Tulip Trading v van der Laan, EWCA Civ 83 (2023)](https://caselaw.nationalarchives.gov.uk/ewca/civ/2023/83), [Claim discontinued](https://www.lexisnexis.com/en-gb/legal/news/bitcoin-inventor-drops-case-against-software-developers), [CLARITY Act status](https://tech-insider.org/clarity-act-2026-status/), [Senate Banking fact sheet on developer protections](https://www.banking.senate.gov/imo/media/doc/fact_sheet_the_clarity_act_protects_software_developers_while_promoting_responsible_defi_innovation.pdf)
Research. [Walch, In Code(rs) We Trust (2019)](https://commons.stmarytx.edu/facarticles/613), [Walch, Deconstructing 'Decentralization' (2019)](https://papers.ssrn.com/abstract=3326244), [Azouvi, Maller, and Meiklejohn, FC 2018](https://discovery.ucl.ac.uk/id/eprint/10073112/), [De Filippi and Loveluck, Internet Policy Review 2016](https://policyreview.info/articles/analysis/invisible-politics-bitcoin-governance-crisis-decentralised-infrastructure), [Yeung and Galindo, European Journal of Risk Regulation 2019](https://www.cambridge.org/core/journals/european-journal-of-risk-regulation/article/why-do-public-blockchains-need-formal-and-effective-internal-governance-mechanisms/B323CC2D41B2498C092C53E8C4A39CE2), [Nabilou, Stanford Journal of Blockchain Law and Policy 2020](https://blogs.law.ox.ac.uk/business-law-blog/blog/2020/04/bitcoin-governance-decentralized-financial-market-infrastructure)
Rule changes and funding. [Taproot lock-in](https://hotfix.coindesk.com/tech/2021/06/12/locked-in-bitcoins-taproot-upgrade-gets-its-90-mandate), [Bitcoin Core v30 and OP_RETURN](https://unchainedcrypto.com/bitcoin-core-v30-releases-with-expanded-op_return-capacity/), [1A1z Funding Bitcoin report](https://nobsbitcoin.com/bitcoin-core-development-funded-with-8-4m-in-2023-report), [Brink engineering report 2025](https://brink.dev/assets/files/brink-engineering-report-2025.pdf)
Bitcoin Core. [Value overflow incident, CVE-2010-5139](https://en.bitcoin.it/wiki/CVE-2010-5139), [CVE-2018-17144 disclosure](https://bitcoincore.org/en/2018/09/20/notice/), [Wallet migration bug notice, January 2026](https://bitcoincore.org/en/2026/01/05/wallet-migration-bug/), [Bitcoin Core 31.1 release notes](https://bitcoincore.org/en/releases/31.1/), [Security advisories](https://bitcoincore.org/en/security-advisories/), [CVE-2018-17144 affected versions](https://www.notcve.org/cve/CVE-2018-17144), [Bitcoin ABC incident report](https://www.bitcoinabc.org/2018-09-26-incident-report/), [Consensus libraries](https://bitcoincore.academy/consensus-libraries.html), [Quarkslab audit](https://blog.quarkslab.com/bitcoin-core-audit.html), [Bitcoin Programming Textbook](https://github.com/karask/bitcoin-textbook), [Governance model](https://www.spark.money/research/bitcoin-core-governance-development-model), [CONTRIBUTING.md](https://github.com/bitcoin/bitcoin/blob/master/CONTRIBUTING.md)
Developer record. [Wuille on review as the bottleneck, #29473](https://github.com/bitcoin/bitcoin/pull/29473), [Towns on the review shortage, #20721](https://github.com/bitcoin/bitcoin/pull/20721), [Self-merge debate, #25524](https://github.com/bitcoin/bitcoin/pull/25524), [Maintainer responsibilities proposal, #25560](https://github.com/bitcoin/bitcoin/pull/25560), [Maintainer selection discussion, #26868](https://github.com/bitcoin/bitcoin/pull/26868), [Release signer concentration](/articles/bitcoin-governance)
Historical record. [Todd on specifications, 2013](https://bitcointalk.org/index.php?topic=153170.msg1633620#msg1633620), [Satoshi on the alert system, 2010](https://satoshi.nakamotoinstitute.org/posts/bitcointalk/409/), [Alert system removal, #7692](https://github.com/bitcoin/bitcoin/pull/7692), [Release process (Guix attestations)](https://github.com/bitcoin/bitcoin/blob/master/doc/release-process.md), [Wuille on attestations and review, #21462](https://github.com/bitcoin/bitcoin/pull/21462)
Code composition. [The Rules Are 7% of the Program](/articles/the-rules-are-7-percent), Bitcoin Core 32.1 line counts
Bitcoin Commons. [Whitepaper](https://thebitcoincommons.org/whitepaper.html), [Consensus specification](https://thebitcoincommons.org/spec.html), [Differential testing guide](https://docs.thebitcoincommons.org/development/differential-testing.html)
Quantitative record. [Bitcoin Governance Research](https://github.com/secsovereign/bitcoin-governance-research), covering the executive summary, research methodology, temporal analysis, merge pattern breakdown, cross-repository and size-adjusted comparisons, and contributor analysis.
---
# Bitcoin Has Governance, and It Is an Informal Oligarchy
## The claim
People often say that nobody governs Bitcoin. It has no chief executive, no board and no foundation that sets its rules, so the usual conclusion is that it has no governance at all.
That conclusion is wrong. Bitcoin's software is maintained in a public repository, and a change reaches the network only if someone merges it. Today five people hold the keys that allow merging, and one of them has merged about half of all pull requests since 2022. They are added and removed by pull request after discussion at a developer meeting, and the written merge rule sets no minimum number of reviews. The people holding that power are identifiable, and their decisions shape what the software does. What is missing is a written rule for how they are chosen, checked or replaced.
This article treats Bitcoin as two layers of governance. The repository layer, where code is written and merged, is an informal oligarchy. The deployment layer, where node operators, miners and businesses decide which software to run, is an unwritten system in which several groups hold vetoes. The argument concentrates on the repository layer, because it is the one with feasible alternatives. Among the forms of governance that could apply there, informal oligarchy falls short of a foundation and a formal oligarchy only on legibility and credible commitment.
Three terms recur. Bitcoin Core is the reference software, and nearly every node runs either Core or an alternative built from its code. A pull request is a proposed code change, and a merge key is the cryptographic key that lets its holder merge changes into Core's main branch. A node is a computer that checks every block and transaction against the rules.
## Polybius and the modern instruments
Polybius was a second-century BCE Greek historian who set out to explain how Rome rose to power. In Book VI of his Histories he names three pure forms of government, kingship, aristocracy and democracy, and a corrupt twin for each, tyranny, oligarchy and mob rule. Each pure form decays into its twin in a cycle that begins with monarchy and ends in mob rule. Rome slowed the cycle, he argued, by mixing all three. Consuls, the senate and the people each checked the other two.
In his scheme oligarchy is one corruption among three, and the form he praises is the mixture. The question he asks is how power is checked, and this article asks it of Bitcoin.
Two thousand years of political science have added instruments for answering it.
- Robert Michels argued in 1911 that organizations drift toward oligarchy as they grow. The evidence is mixed. A study of 683 wikis supports him, a 1971 test on a state party found little, and Giovanni Sartori called it a bronze law rather than an iron one.
- Jo Freeman showed in 1970 that dropping formal structure leaves informal structure in place, and that the informal kind hides power from anyone who does not know the rules.
- George Tsebelis showed that the more veto players a system has, and the further apart they are, the more stable its policy is and the harder it is to change.
- Albert Hirschman gave exit and voice as the two ways participants discipline an institution.
- Elinor Ostrom found that long-lived shared resources follow common design principles, including clear boundaries, monitoring, graduated sanctions and cheap dispute resolution. Her cases were small and local, so applying her principles to global commons needs adaptation.
## How Bitcoin is governed
Bitcoin's rules are enforced by thousands of independent nodes, but the software those nodes run comes from somewhere. That gives two layers that need separate treatment.
The repository layer maintains the software. Core 32.1, released in October 2026, has 151,004 lines of implementation code and 154,273 lines of tests. The rules that decide whether a block or transaction is valid are 10,122 of those lines, 7% of the implementation. Anyone can submit changes, but only the five merge-key holders can merge them, and their gate covers the other 93% of the code as well as the rules. Nearly every alternative node program is built from Core's code, so decisions made here reach almost every node.
The deployment layer decides which release actually runs. Node operators choose what software to run, miners choose which upgrades to signal for, and businesses such as exchanges and wallet providers decide what to support. Each group can refuse a release.
Five merge keys decide what is offered, and nodes, miners and businesses decide what runs. Neither layer is a pure form of governance.
The chart estimates how strongly each layer leans on seven forms, from 0 to 5. Forms overlap, so the scores do not sum to a whole. Technocracy means authority earned through technical track record, rough consensus means open review and signaling, and market and exit means forks and competing software.
The repository layer leans on informal oligarchy and technocracy. The deployment layer leans on exit, hashrate and rough consensus. The rest of the article concentrates on the repository layer.
## What the record shows
Nine episodes since 2013 show identifiable people and groups making binding decisions, with no written rule for how.
| Date | What happened | Why it matters |
| --- | --- | --- |
| Sept 2026 | Luke Dashjr, maintainer of an alternative node program built from Core's code, launched a breakaway fork that changed Bitcoin's mining algorithm to BLAKE2b. Miner signaling peaked at 2.53% against a 55% threshold, and no major exchange listed the new coin | Changing the consensus rules means leaving the network everyone else is on. The proposal drew almost no support, so the outcome shows rejection more than the price of leaving |
| Feb 2026 | Maintainer Gloria Zhao removed her merge key and stepped down. No reason was given | Key holders are added and removed by an ordinary pull request, and five remained |
| Jan 2026 | A developer known as sedited was nominated at the regular developer meeting and added as the sixth key holder | Selection runs through a meeting and a pull request, not a published procedure |
| Sept to Oct 2025 | Core version 30 raised the default limit on OP_RETURN, the field that lets a transaction carry arbitrary data. Opponents objected, and the share of reachable nodes running an alternative built from Core's code rose to 25.45% on September 14 | The maintainers settled a contested decision. Switching software over a policy difference was cheap, and about a quarter of reachable nodes did it, but the alternatives enforce the same consensus rules as Core and are built from its code |
| 2021 | Activation of the Taproot upgrade stalled over a technical dispute until a developer proposed a compromise, called Speedy Trial, in a chat room | One developer's proposal broke the deadlock |
| Sept 2018 | A bug in Core, present since version 0.14 in March 2017, was reported on September 17 and proved to let a miner inflate the coin supply. A fix shipped on September 18 after a handful of developers coordinated privately, and it was first described as a denial-of-service fix | The fix was fast, and the disclosure choices were made by a few people. Core's written security policy leaves critical bugs to an ad hoc procedure, and the bug sat in the only reference implementation for about a year and a half |
| Nov 2017 | Segwit2x, a plan backed by miners, exchanges and wallet providers to raise the block size limit, was cancelled after it failed to gain enough support | A coalition of miners and businesses could not force a change through |
| Apr to Aug 2017 | BIP148 proposed a user-activated soft fork to force activation of the SegWit upgrade. Core developers did not merge it because they saw no consensus for it | Users coordinated outside the repository |
| 2013 | A software upgrade accidentally split the network into two chains, and developers and miners coordinated a rollback | A crisis decision was made by coordination, with no formal authority |
The author's analysis of about 17,000 merged Bitcoin Core pull requests through October 2026 adds numbers. It uses GitHub's public record of each merged pull request, with its author, the person who merged it and every recorded review. A self-merge is a maintainer merging their own pull request, and a review is a recorded approval, comment or change request on GitHub.
- Merging is more concentrated than the key count suggests. Since 2022 one current key holder has merged 50.2% of pull requests and three have merged 82.2%. Merge share is not decision share, since many merges are routine, but it shows where the gate is narrowest.
- The proposal layer is far more open than the code layer. The repository that records Bitcoin Improvement Proposals has 443 distinct mergers and a top-three share of 10.6%, against 23 mergers and 76.4% for Core over its history.
- Maintainers self-merged 25.5% of their merged pull requests, and 45.1% of those self-merges had no recorded review. No written rule sets a minimum number of reviews.
- Practice has improved. Self-merges with no recorded review fell from 83.9% in 2016 to 4.0% so far in 2026.
- Outsiders face a hard start. A contributor's first pull request was merged about 29% of the time over the project's history and about 16% since 2022. Established outsiders with five or more earlier merges are merged about two thirds of the time.
- No written rule says who receives merge keys. The contribution guidelines describe how a key holder judges consensus and say nothing about how keys are granted.
- The files that define the rules drew 169 commits from 31 people over the last three years, and five of them accounted for half. Writing the code is spread more widely than the power to merge it.
Review practice has tightened since 2016, while the self-merge rate stayed high until 2021. The self-merge rate is the share of merged pull requests merged by their own author.
Funding is concentrated as well. A 1A1z report found that $8.4 million was spent on Bitcoin developers in 2023. Among the eight sponsors that rely only on donations, the top three receive 62.25% of their funding from a single source, Jack Dorsey.
## Measuring a form of governance
Six measures, each with a test someone else can run, score every form from 1 (worst) to 5 (best).
| Measure | What it asks | How to test it |
| --- | --- | --- |
| Capture resistance | How few actors can change the rules | The smallest number of actors whose assent changes the rules, and how concentrated merges are. The Nakamoto coefficient, proposed by Balaji Srinivasan in 2017, applies this idea and is taken as the minimum across subsystems |
| Exit cost | How cheaply participants can leave | The share of economic weight that followed a fork or split, following Hirschman's exit and voice |
| Legibility | Whether participants can see who decided what, under which rule | Two parts, following Freeman. Whether each decision has a named decider, and whether a written rule says who decides and how. Neither part scores 1, one part scores 2 or 3, and both score 4 or 5 |
| Error correction | How fast and cheaply a bad decision is reversed | Time from error to rollback, and who had to agree |
| Credible commitment | How hard it is for rulers to change the rules against participants | The number of veto players and the distance between them, following Tsebelis |
| Decision cost | How much time and effort a decision takes | Time from proposal to decision, and deadlocks, following Buchanan and Tullock's cost trade-off |
Prosperity and freedom are left out. They depend on separating cause from selection effects across countries, and Bitcoin is one case, so the scores cover process quality only.
## Forms that could govern the repository
Seven of nine forms of governance can apply to the repository layer. Real systems combine forms, so each form below is judged as a candidate for that layer alone.
| Form | Can it apply | Reason |
| --- | --- | --- |
| Direct democracy, one person one vote | No | Participants are pseudonymous and identities are free to create, so votes cannot be counted |
| Token-weighted voting | No | Bitcoin has no governance token, and studies of DAOs that vote this way find power concentrated, with half of those studied controllable by three or fewer delegates |
| Single maintainer | Yes, at a legitimacy cost | The software allows it, but Satoshi Nakamoto's exit was central to the story that Bitcoin has no ruler |
| Foundation or corporate steward | Yes, with legal exposure | A legal entity is a single target for lawsuits, regulators and lobbying. Individual Core developers were sued in the Tulip Trading case, and an entity would concentrate that exposure |
| Informal oligarchy | Yes, and it is the current form | Five key holders, chosen by pull request and meeting |
| Formal oligarchy | Yes | A committee with published rules for selection, review and removal |
| Elected council | Yes, with limits | Python elected a five-member steering council in 2019, but Bitcoin has no agreed electorate |
| Mixed constitution with written vetoes | Yes | Separate powers for proposers, reviewers and deployers, with written thresholds. Bitcoin Commons, an alternative Bitcoin implementation, uses a five-tier version with signature thresholds |
| Commons governed by Ostrom's principles | Yes, conditional | Needs bounded membership and monitoring, and her cases were small and local |
The two excluded forms need a counted electorate. Every form that survives needs only an accountable group and a written rule, which the repository layer largely lacks.
## Scores
Against a foundation and a formal oligarchy, exit cost, error correction, capture resistance and decision cost do not account for the gap. The whole shortfall is legibility and credible commitment.
Higher is better, and for exit cost and decision cost higher means cheaper. The scores are judgments, and each panel notes how much evidence stands behind it.
The chart isolates the comparison that matters, informal oligarchy against formal oligarchy.
- Exit cost is 3 for every repository form. Switching software over a policy difference is cheap, as the move to alternatives during the version 30 dispute showed. Leaving the consensus rules means leaving the network, and that costs the same whoever maintains the repository. The failed BLAKE2b fork and Segwit2x show weak demand for those changes more than a high price for leaving. The one repository-level lever is a written, independent specification of the rules, which is a design choice separate from the form of governance.
- Informal oligarchy scores 2 on legibility. Each merge is recorded with a name, but no written rule sets a minimum number of reviews or says how merge keys are granted, selection runs through a pull request and a meeting, Core's written security policy leaves critical bugs to an ad hoc procedure, and 45.1% of maintainers' self-merges had no recorded review. Who judged consensus, who objected and who coordinated in private is not recorded. A single maintainer scores 3, because every decision has one obvious author even with no written rule.
- It scores 2 on capture resistance because five keys gate the repository, one key holder has merged half of all pull requests since 2022, and funding is concentrated.
- It scores 3 on error correction because the 2013 rollback worked and a planned deprecation of the option that lets node operators cap OP_RETURN size was reversed on September 30, 2025, after protest. It does not score higher because the 2018 inflation bug sat in the code for about a year and a half and was first described as a denial-of-service fix, and because people affected by a decision have no formal route to challenge it.
- Decision cost also scores 3. The median merged pull request took 3.9 days for maintainers and 6.4 days for everyone else. Speed is the advantage informality usually claims, and here it only ties a formal oligarchy.
**How far to trust the scores.** Every score is a judgment. Only informal oligarchy and the elected council have evidence behind them from Bitcoin or a comparable project. The two highest totals belong to forms untested at Bitcoin's scale, so the order at the top means little, and nothing in the conclusion depends on it. Legibility and credible commitment reward written rules by definition, so any written form beats an unwritten one on those two measures, and the score gap partly restates that. The case that the missing rules matter rests on the record. Keys are granted with no written procedure, merges need no minimum review, and critical bugs go to an ad hoc process. A reader who treats legal exposure as a capture risk would mark the foundation worse on capture resistance. That does not close the gap, which is legibility and credible commitment.
## Objections
Four objections test the thesis, and it survives in a narrower form.
| Objection | Strongest form | What survives |
| --- | --- | --- |
| Maintainers only propose | Users and miners decide what runs. In the block size war of 2015 to 2017, companies, miners and prominent developers could not override node operators | The agenda setter still controls the menu. Operators can refuse a release, as about a quarter of reachable nodes did over version 30, but the alternatives they moved to are built from Core's code, so the claim stays scoped to the repository layer |
| Informality shields against legal capture | A legal entity can be sued or compelled. In Tulip Trading the English Court of Appeal ruled in 2023 that it was arguable Bitcoin developers owe fiduciary duties to coin owners, a position Angela Walch had argued in 2019 | Individual developers were sued anyway. This argues for written rules that need no legal entity, such as published signing thresholds, and a foundation would gather that exposure in one place |
| Michels' iron law is contested | The evidence that oligarchy is inevitable is mixed | The thesis rests on Bitcoin's own record and does not need inevitability |
| Review practice has improved | Self-merges with no recorded review fell to 4.0% so far in 2026 | The improvement is a norm and no rule requires it. The self-merge rate was 30.3% in 2021 and 10.9% so far in 2026, so it has moved once and can move back |
The surviving claim is narrower than the worst form of governance. At the repository layer, informal oligarchy has the lowest legibility of any form and no written commitment device. That is enough to show that Bitcoin has governance and that its form hides it.
## Conclusion
Bitcoin has governance, and the repository layer is run by an informal oligarchy of five key holders. Its weakness is that the rules are unwritten, which makes power hard to see and hard to hold to account. Capture resistance and exit cost are not where it loses ground. In Polybius's terms the five key holders are an aristocracy with nothing written to keep it from becoming his oligarchy, and the deployment layer is a popular check that can only say no. Rome slowed the cycle by making each power answer to the others, and the repository has no such check written down.
Three written rules would close most of the gap. They are a published procedure for adding and removing key holders, a minimum review requirement for merges, and an independent specification of the consensus rules that other implementations can be checked against. The first two close the gap with a formal oligarchy. None of the three needs a legal entity, a vote or a change of form, and all three fit the current maintainers as they are.
The deployment layer has no formal alternative to compare. Its one tool is refusal. Switching software is cheap, but every alternative it can switch to is built from Core's code, and that calls for separate design work.
## Sources
Sources by topic.
Theory and comparators
- Polybius and the mixed constitution, [The Collector](https://www.thecollector.com/polybius-ancient-historian-rome/) and [Thornton](https://montesquieu.unibo.it/article/view/5144)
- [Michels and oligarchy](https://www.encyclopedia.com/topic/iron_law_of_oligarchy.aspx), [Shaw and Hill on 683 wikis](https://arxiv.org/pdf/1407.0323), [Pahl 1971](https://digitalcommons.morris.umn.edu/jmas/vol37/iss2/18) and [Sartori](https://pressbooks.pub/cisi/?p=62)
- [Freeman, The Tyranny of Structurelessness notes](https://ferd.ca/notes/paper-the-tyranny-of-structurelessness.html)
- [Veto players, Tsebelis overview](https://core-prod.cambridgecore.org/core/books/formal-models-of-domestic-politics/veto-players/FAD5549C08C6188A9CE6B71E6DB5D60D)
- [Exit and voice in open source, Viseur and Charleux](https://esploro.umontpellier.fr/esploro/outputs/conferenceProceeding/Open-Source-Communities-and-Forks-A/99148160209311)
- [Ostrom, design principles overview](https://www.ecologyandsociety.org/vol15/iss4/art38/) and [Rozas et al. on global commons](https://www.frontiersin.org/article/10.3389/fbloc.2021.577680)
- [Nakamoto coefficient, Spark glossary](https://www.spark.money/glossary/decentralization)
- [DAO voting concentration, empirical study](https://arxiv.org/pdf/2302.12125)
- Developers as fiduciaries, [Walch](https://commons.stmarytx.edu/facarticles/613), [Tulip Trading v van der Laan, EWCA Civ 83 (2023)](https://caselaw.nationalarchives.gov.uk/ewca/civ/2023/83) and [Tulip Trading analysis](https://thebarristergroup.co.uk/blog/the-tulip-trading-case-and-the-future-of-liability-in-web3-and-blockchain-networks)
- [Python steering council, LWN](https://lwn.net/Articles/777997/rss)
Bitcoin episodes
- [Zhao leaves, crypto.news](https://crypto.news/bitcoin-core-maintainers-face-shake-up-as-gloria-zhao-revokes-pgp-key/). [sedited added, btcpp insider](https://insider.btcpp.dev/p/bitcoin-core-adds-new-maintainer)
- [BLAKE2b fork, BeInCrypto](https://beincrypto.com/bitcoin-hard-fork-failed-adam-back/) and [CryptoRank](https://cryptorank.io/news/feed/75b12-bitcoin-hard-fork-dashjr-fake-bitcoins)
- [Core v30, Cointelegraph](https://cointelegraph.com/magazine/bitcoin-upgrade-core-developers). [OP_RETURN deprecation reversed, pull request 33453](https://github.com/bitcoin/bitcoin/pull/33453) and [Protos](https://protos.com/bitcoin-core-drops-op_return-deprecation-hours-before-v30-release). [Alternative node share, Bitcoin.com](https://news.bitcoin.com/nl/bitcoin-knots-versterkt-greep-vangt-meer-dan-een-kwart-van-netwerk-nodes/)
- [Taproot activation, Speedy Trial glossary](https://www.learnbitcoin.com/glossary/speedy-trial)
- [Segwit2x, Fortune](https://fortune.com/crypto/2017/11/12/bitcoin-upheavel-segwit2x-fork). [BIP148, BIP text](https://github.com/bitcoin/bips/blob/master/bip-0148.mediawiki)
- [2013 fork and governance overview, Oxford Business Law Blog](https://blogs.law.ox.ac.uk/business-law-blog/blog/2021/12/coming-battle-over-bitcoin-governance)
- [Funding, 1A1z, Funding Bitcoin](http://1a1z.com/fund.html) and [No Bullshit Bitcoin coverage](https://nobsbitcoin.com/bitcoin-core-development-funded-with-8-4m-in-2023-report)
- [Mining pool concentration, GN Crypto, June 2026 snapshot](https://www.gncrypto.news/news/four-pools-control-over-70-percent-bitcoin-hashrate/)
- Line counts for Core 32.1, [The Rules Are 7% of the Program](/articles/the-rules-are-7-percent)
Dataset. The merge, review and outsider figures come from the author's [Bitcoin Governance Research](https://github.com/secsovereign/bitcoin-governance-research) analysis of Core's pull request history, built from GitHub's public record of 16,811 merged pull requests. A self-merge is a merge by the pull request's author, and a review is any recorded approval, comment or change request. The Bitcoin Commons design comes from its governance documents.
---
# BIP Pre-Proposals
# Static Per-Output Miner Fee
## Contents
- [Abstract](#abstract)
- [Motivation](#motivation)
- [Specification](#specification)
- [Rationale](#rationale)
- [Backwards Compatibility](#backwards-compatibility)
- [Reference Implementation](#reference-implementation)
- [Calibration Checklist](#calibration-checklist)
- [Security Considerations](#security-considerations)
- [Revision history](#revision-history)
- [References](#references)
- [Copyright](#copyright)
---
## Abstract
This BIP proposes a consensus-enforced per-output miner fee: a fixed satoshi floor that every non-coinbase transaction must leave as part of its ordinary transaction fee for each output it creates.
Bitcoin has no consensus-enforced fee floor today. Policy-based dust limits and mempool filters are unenforceable, because any transaction that pays enough miner fees can still be included by a participant who chooses not to enforce those filters. This proposal prices the permanent cost of UTXO creation at consensus, and it binds every participant.
The fee is a single fixed constant. There is no dynamic component, no sampling window, no moving average, and no rate adjustment. Every non-coinbase output pays the same fee regardless of script type, value, or fee environment. The amount is paid as ordinary miner fee (`sum(inputs) - sum(outputs)`), not minted into the coinbase. It is not recoverable by the sender. Old nodes see a valid high-fee transaction. New nodes reject transactions that miss the floor. That is a soft fork.
The design is deliberately small. A [companion BIP](/bips/dynamic-escalation-per-output-fee) adds a dynamic escalation layer on top of this static fee once the network has operational experience with the base rule. Dedicated embedding channels are a different surface; they are closed by [Permanent Data Channel Closure](/bips/permanent-data-channel-closure). The three pre-proposals are one stack. This BIP prices the UTXO slot.
---
## Motivation
### The Problem: No Consensus Fee Floor Exists
Bitcoin has no consensus rule requiring any minimum fee for transaction inclusion. Policy filters, dust limits, and minimum relay fees can all be bypassed by routing through a miner who does not enforce them. That is why UTXO spam debates have cycled for years without resolution. Policy binds willing participants. Consensus binds everyone.
This BIP introduces a consensus fee floor scoped to UTXO creation: the surface where unpriced externalities are measurable, permanent, and harmful to network health.
### The Two Spam Vectors
UTXO set spam runs on two vectors.
Two UTXO spam vectors, one permanent fee
Value vector
Near-zero / dust outputs
Uneconomical to spend
Permanent UTXO accumulation
Dominant historical pattern
Count vector
High outputs per transaction
Each may carry real value
Bloat via volume, not dust
Attractive once value vector dies
A per-output fee closes both: every output costs the fee regardless of value, and cost scales linearly with count.
The **value vector** is the main historical pattern: outputs created at or near zero value that are uneconomical to spend and sit permanently in the UTXO set. They cost almost nothing to create because their value is tiny and miner fees can be spread across many outputs.
The **count vector** is the secondary pattern: many outputs per transaction, each carrying real value, bloating the UTXO set through volume rather than dust. This vector becomes more attractive once the value vector is closed.
A permanent per-output fee closes both at once. Any output costs the fee to create, whatever its value. The fee scales linearly with output count. There is no capital recovery path: the fee goes to miners and does not come back.
### The Externalized Cost This Proposal Prices
The per-output fee is not a new tax on Bitcoin use. It prices a cost that already falls on node operators instead of the actors who create it.
*[Full Cost of Running a Bitcoin Node](/articles/full-cost-of-running-a-bitcoin-node)* (v2.4, July 2026) estimates that burden:
UTXO set composition (May 2025, tip 892385)
29.6%70.4%
■ Inscription-related■ Other UTXOs
Inscription UTXOs
51,188,145
Mean value
811 sats
Network burden
~$4M / year
Mempool Research UTXO Set Report. Inscription outputs impose permanent storage on every node, whether or not the operator cares about that activity.
Externality
Estimate
Who pays
Non-monetary chain share
12-19% (~85-140 GB of 700-750 GB)
Every new node at IBD
Annual IBD from inscriptions
765 GB - 1.68 TB across ~9-12k new nodes
New participants
Per-node ongoing cost
$5.52-$5.54 / month (2026)
~60,000 full nodes
Aggregate network burden
~$4M / year
Node operators
Core development spend
~$9M / year
(comparison only)
Node operators absorb a non-monetary burden approaching half of total protocol development spend, with no recovery path.
That also names a political constituency: about 60,000 node operators absorbing roughly $4 million per year in non-monetary burden. They have a direct interest in this rule. They are not the BIP-8/9 signaling threshold.
### Why Determined Spammers Require a Permanent Fee
The 2023 to 2026 inscription and ordinals waves showed that determined spammers are more price-insensitive than simple models predict. Those actors paid sustained high miner fees because presence on Bitcoin itself was part of the product. Blocks ran 91 to 97% full for long stretches, and the activity continued.
A capital lockup does not change that math. An attacker facing only a minimum output value can mint outputs, lock capital, spend them back, and repeat. The per-output fee removes that path. Every spam run is permanently more expensive, with no revolving capital to fund the next one.
Minimum output value vs per-output miner fee
Min output value (lockup)
Capital locked in each output
Recovered when output is spent
Revolving cost to attacker
Spam runs can recycle forever
Per-output miner fee
Sats paid to confirming miner
Not recoverable by sender
Permanent cost per output
Every spam run is more expensive
Permanence is the point. Lockup is a revolving door; the miner fee is not.
### Provisional Static Fee Anchor
The static fee needs a principled starting point for calibration, not an arbitrary constant. The node-cost work above helps, but the derivation has to ask the right question.
The $4 million per year aggregate and the $5.52 to $5.54 per node per month figures are the ongoing cost of non-monetary data already in the chain: storage, bandwidth, and RAM that existing inscription UTXOs impose every month. That is a stock cost, not a per-new-output flow cost. You cannot divide it by new UTXO creation rates and call the result a fee.
The right question is: what lifetime cost does one newly created non-monetary UTXO impose on the network from creation forward? That cost has three parts:
1. **Permanent storage cost:** about 85 to 140GB of non-monetary chain data at $0.11/GB NVMe pricing is $9 to $15 per node in sunk storage. Spread across about 51 million inscription UTXOs, that is roughly 0.1 to 0.3 sat per UTXO in storage cost per node.
2. **Ongoing monthly storage and RAM burden:** $5.52 per month per node in non-monetary ongoing cost. At 60,000 nodes and 51 million inscription UTXOs, that is about 78 sats per UTXO per year across the network, or roughly 6 to 7 sats per UTXO per node-year.
3. **IBD cost** on every future node that syncs the chain: 85 to 140GB of inscription data downloaded once per new node, at about 9,000 to 12,000 new nodes per year.
Summing those pieces and discounting over a reasonable UTXO lifetime at current BTC price yields a per-UTXO externalized lifetime cost around **16 to 20 sats per output**. That is a cost-derived provisional anchor for the **UTXO-slot** externality, not a conclusion, and not an inscription-killer. The 2023 to 2026 inscription waves already paid far more than 20 sats per output in weight fees. Those waves would have continued at this floor on fee grounds alone. Closing dedicated data channels is the job of *[Permanent Data Channel Closure](/bips/permanent-data-channel-closure)*. This BIP prices output count.
The 16 to 20 sat band must still be checked against two tests: what floor deters high-count UTXO spam at realistic attacker budgets, and what floor stays negligible relative to legitimate output values across historical fee regimes. If calibration shows 16 to 20 sats is too low to deter determined count-vector spam, the static fee will be raised and the change documented before the proposal moves forward. If the floor is not negligible for Lightning channel opens, CoinJoin outputs, and exchange batch withdrawals, the static fee will be lowered and the change documented the same way.
---
## Specification
### Fee Rule
This is a transaction-fee floor, not extra mint. Coinbase accounting is unchanged from existing consensus (`coinbase_value <= block_subsidy + sum(tx_fees)`). A block of transactions that each meet the per-output floor can still have a miscounted coinbase, so that existing check remains required in addition to the per-transaction floor. The floor is a consensus validity rule, not relay policy. Miner preference cannot override it. Adding the per-output amount to the coinbase above subsidy-plus-fees would be a hard fork and is not this BIP.
For every non-coinbase transaction in a block at or above `activation_height`:
```text
tx_fee = sum(input_values) - sum(output_values)
n_outputs = count(outputs in this transaction)
tx_fee >= active_fee × n_outputs
```
```text
active_fee = static_fee
```
`tx_fee` is the existing consensus fee: a non-negative integer satoshi amount. Transactions with `sum(input_values) < sum(output_values)` remain invalid under existing rules. `static_fee` is a consensus constant fixed at activation. It changes only by a future soft fork.
Overpayment is valid. The floor is per transaction from that transaction's own inputs and outputs. Package fee rate and CPFP do not count: a parent that misses the floor is invalid even if a child pays more.
All arithmetic is integer satoshis. Multiplication uses at least 64-bit unsigned range. A transaction that overflows that range is invalid.
### Exempt Outputs
The coinbase transaction is the only exemption. Charging coinbase outputs would be circular: the coinbase is how the miner collects `tx_fee`. All other transactions pay the floor, including those whose outputs are `OP_RETURN` or otherwise unspendable.
### Validation
1. Skip the coinbase transaction.
2. For each remaining transaction, compute `tx_fee` and `n_outputs` as above. The product `static_fee × 0` is 0, so an empty output list would meet the floor. It does not matter: existing consensus rejects a transaction with no outputs (`bad-txns-vout-empty` in Bitcoin Core `CheckTransaction`). This BIP does not make that transaction valid.
3. If `tx_fee < static_fee × n_outputs`, the transaction is invalid and the block is invalid.
4. Existing coinbase rules are unchanged. Miners receive the per-output amount because it is part of `sum(tx_fees)`.
This is a soft fork. Old nodes accept any non-negative fee. New nodes reject transactions that miss the floor. A miner who includes a non-compliant transaction produces a block that enforcing nodes reject.
### Activation Height
The fee rule applies to every block at or above `activation_height`. Blocks below `activation_height` are unaffected. `activation_height` is set by the BIP-8 or BIP-9 signaling process and is known in advance, so wallets and services have time to update fee estimation. No separate grace window is specified: the minimum one-year signaling window is enough protection for in-flight transactions, and an extra grace window adds complexity without much added safety.
### Consensus State
The only consensus state this BIP requires is:
- `static_fee` (fixed at activation)
- `activation_height` (set by the signaling process)
Both are deterministic from the soft fork activation parameters and need no ongoing computation.
### Parameters
Parameter
Description
Provisional value
static_fee
Fixed per-output fee in sats
16-20 sats (pending calibration)
At the provisional band, count-vector cost scales linearly:
Outputs created
@ 16 sats
@ 20 sats
100
1,600 sats
2,000 sats
1,000
16,000 sats
20,000 sats
10,000
160,000 sats
200,000 sats
100,000
1,600,000 sats
2,000,000 sats
Permanent, non-recoverable cost per spam run. Calibration must confirm deterrence at realistic attacker budgets and negligibility for legitimate high-output use.
One regtest measurement, Bitcoin Core v28.1, is not a consensus constant. A 100-input, 100-output P2WPKH transaction, signed with low-R ECDSA, had vsize 9,886 on two runs. Weight was 39,541, then 39,542; one witness byte did not change `ceil(weight / 4)`. Core accepted fees of 1,599, 1,600, and 2,000 sats. The 9,886 row is that vsize times 1 sat/vB. It was not a separate Core run.
| Fee (sats) | What it is | Floor at 16 | Floor at 20 |
|---|---|---|---|
| 1,599 | Below both products | Reject | Reject |
| 1,600 | `16 × 100` | Accept | Reject |
| 2,000 | `20 × 100` | Accept | Accept |
| 9,886 | 1 sat/vB on this vsize | Accept | Accept |
### Activation
This BIP is meant to deploy via a soft fork using BIP-8 or BIP-9 style signaling, with a minimum activation window of one year and no mandatory lock-in fallback. Miners who do not signal are not penalized. If signaling does not reach the threshold within the window, the proposal does not activate and the process restarts with revised parameters or renewed community discussion.
BIP-8/9 without lock-in-on-timeout is miner signaling. Node operators absorbing non-monetary burden are a political constituency for this rule; they are not the signaling threshold. If miners do not signal, this BIP does not activate under the specified mechanism. User-activated soft fork deployment is a separate choice and is not specified here.
---
## Rationale
### Why a Fee Floor, Not Extra Mint
The per-output amount must be part of `tx_fee`. Minting it on top of subsidy-plus-fees would raise `coinbase_value` above what pre-activation nodes allow, which is a hard fork. A floor on `tx_fee` is a soft fork: old nodes accept the transaction; new nodes reject a miss. Miners still receive the sats. The amount is still permanent and not recoverable by the sender.
### Why a Permanent Fee Rather Than a Capital Lockup
A minimum output value floor forces attackers to lock capital in each output. That capital returns when the output is spent, so the floor is a revolving cost. The per-output miner fee removes that path: those sats go to miners and do not return. Every spam run is permanently more expensive.
### Why This Differs from Prior Minimum Fee Proposals
Prior minimum fee proposals were either relay policy, which miners can bypass, or minimum output value floors, which return locked capital when outputs are spent. This proposal is neither. The per-transaction consensus validity rule means a non-compliant transaction cannot appear in any valid block, regardless of miner preference or side arrangements. The fee is paid at confirmation and is not recoverable by the sender.
### Why a Single Global Rate With No Script-Type Differentiation
A single constant per output is the simplest rule. Script-type differentiation would force the fee to track script classification across every output form, create edge cases at upgrade boundaries, and make the rule harder to specify cleanly. The externalized cost this fee prices is per UTXO slot, not per script type, so a uniform fee matches the cost model.
### Why OP_RETURN Pays the Fee
All non-coinbase outputs pay the fee, including `OP_RETURN` and provably unspendable outputs. Legitimate `OP_RETURN` users will object: timestamping services, colored coin protocols, and apps that embed small amounts of data for non-spam purposes.
The tradeoff is accepted for two reasons. First, the motivation is the cost imposed on node operators by all non-coinbase output creation, including outputs that never enter the UTXO set. `OP_RETURN` outputs consume block space and impose bandwidth and storage costs on every node whether or not they are spendable. Exempting them while citing node operator burden would contradict the premise. Second, at a correctly calibrated static fee of 16 to 20 sats, the cost per `OP_RETURN` output is negligible for legitimate low-volume use and material only for high-volume data embedding, which is the intended effect.
### Why a Static-Only Rule First
A combined static-plus-dynamic rule has more review surface, more implementation complexity, and more political attack surface than a static-only rule. The property that matters most is that a permanent, non-recoverable cost exists on every new output. That property lives entirely in the static component. The dynamic escalation layer is a long-term anti-decay mechanism that is useful but not urgent. Staging the two rules raises the odds that the core mechanism actually reaches consensus.
### Miner Incentives
Miners receive per-output fees as part of ordinary `tx_fee` in the coinbase. They have a financial interest in including transactions that create outputs. That is not new: miners already want fee-paying transactions. The per-output fee raises the price floor on all output creation. Spammers pay miners more per output than before. The per-output cost to attackers rises whether or not aggregate spam volume falls.
Large miners who earn significant revenue from inscription-style activity may oppose this. That opposition is short-term: a fee market where monetary transactions compete on equal terms with correctly priced non-monetary use produces more durable revenue than one distorted by externalized costs.
### Interaction with Permanent Data Channel Closure
The [Permanent Data Channel Closure](/bips/permanent-data-channel-closure) pre-proposal targets dedicated high-bandwidth data channels: `OP_RETURN`, Taproot envelopes, witness fragmentation, and related embedding surfaces. This BIP targets UTXO creation economics and charges all outputs, including `OP_RETURN`. The two proposals address different surfaces and reinforce each other when activated together. Coordinated activation of all three pre-proposals closes dedicated embedding channels and prices UTXO creation. Hash, amount, `nSequence`, and ordering fields remain open because payments require them; see *[The Achievable Floor](/articles/the-achievable-floor)* and *[Bitcoin Is Not a Hard Drive](/articles/bitcoin-not-a-hard-drive)*.
### Activation Game Theory
Prior soft fork proposals that use mandatory lock-in fallbacks treat non-signaling miners as attackers rather than participants with legitimate concerns. This BIP uses voluntary signaling with no mandatory lock-in. If inscription-dependent miners block signaling, that outcome documents the network's governance dynamics and strengthens the case for implementation diversity and alternative node software. It does not activate the rule. Node-operator interest is not a substitute for the specified signaling threshold.
The most credible activation path is to deploy on signet and testnet, run the rule in production across Bitcoin Commons and Bitcoin Knots, publish calibrated parameters with full chain scan results, and treat miner signaling as a multi-year process.
---
## Backwards Compatibility
Existing UTXOs remain valid and spendable. Old nodes will see new blocks as valid under the soft fork. From the user's point of view there is one fee: wallets add the weight-based transaction fee and the per-output component internally and show a single total. Wallets that do not update will underestimate fees and produce transactions that enforcing nodes reject at and after the activation height. The one-year minimum signaling window gives the wallet ecosystem time to update. Updates should be complete before activation: unlike soft forks that affect only unusual transaction types, the per-output fee affects fee estimation for nearly every transaction that creates outputs. A wallet that is not updated by activation will start producing invalid transactions the moment the rule applies, with no warning to the user.
Lightning channel opens, CoinJoin transactions, and exchange batch payouts will pay the per-output fee for each output created. Calibration must confirm the fee is negligible relative to typical output values across historical fee regimes. Exchanges should be engaged before signaling begins.
The floor is per transaction. A child that spends a P2A or anchor output does not count toward the parent's `tx_fee`. Regtest Core v28.1 accepted both parents below, and a high-fee child of the first. The floor rejects both parents. The child is not a row: its fee is not added.
| Parent | Own `tx_fee` | Outputs | Required at 16 | Required at 20 | Floor |
|---|---|---|---|---|---|
| Two outputs | 20 | 2 | 32 | 40 | Reject |
| Three outputs, one P2A `51024e73` | 0 | 3 | 48 | 60 | Reject |
BOLT 3 `zero_fee_commitments` and `option_anchors` CPFP, as specified today, put the mining fee on the child. After activation those commitment transactions are valid only if the commitment's own `tx_fee` is at least `static_fee × n_outputs`. The child still pays any extra weight fee. Wallets that leave the commitment at fee 0 will produce transactions enforcing nodes reject.
---
## Reference Implementation
High-level pseudocode:
```python
STATIC_FEE =
ACTIVATION_HEIGHT =
def tx_fee(tx):
return sum(inp.value for inp in tx.inputs) - sum(out.value for out in tx.outputs)
def is_valid_transaction(tx, block_height):
# Transaction validation, before block assembly.
# Per-transaction floor: no tx can free-ride on another tx's fees in the same block.
if block_height < ACTIVATION_HEIGHT or tx.is_coinbase:
return True
return tx_fee(tx) >= STATIC_FEE * len(tx.outputs)
def is_valid_block(block):
# First guard: every transaction must already meet the per-output floor.
if not all(is_valid_transaction(tx, block.height) for tx in block.transactions):
return False
# Second independent guard: existing coinbase accounting.
fees = sum(tx_fee(tx) for tx in block.transactions if not tx.is_coinbase)
return coinbase_value(block) <= block_subsidy(block.height) + fees
```
The per-transaction function does not check coinbase value. `is_valid_block` applies existing subsidy-plus-fee rules as a second independent guard.
Detailed test vectors, integer arithmetic precision requirements, and treatment of edge cases (zero-output transactions, reorgs at activation height, IBD validation) will be provided in a future numbered BIP submission.
---
## Calibration Checklist
Calibration is a hard gate. The static fee value is provisional until this checklist is satisfied.
### A. Static Fee Determination (Hard Gate)
- Validate the provisional 16-20 sat anchor as a UTXO-slot price: stress-test against high-count attack economics at realistic attacker budgets (1,000 / 10,000 / 100,000 outputs). Raise the static fee if the provisional number does not deter count-vector spam at scale. Do not treat "would inscriptions have stopped at 20 sats" as a pass condition; that is the data-channel BIP.
- Confirm the static fee is negligible relative to Lightning channel open values, CoinJoin outputs, and exchange batch withdrawal amounts at the 99th percentile fee rate.
- Confirm the static fee does not make ordinary small payment outputs uneconomical under any historical fee regime.
- Lock in the static fee value, or document the required adjustment with full reasoning.
### B. Collateral Damage (Must Pass)
- Lightning channel opens: per-output fee as a percentage of typical funding output value; pass if negligible across historical fee regimes.
- Exchange batch withdrawals: total per-output fee burden as a percentage of transaction value; pass if negligible.
- CoinJoin / JoinMarket / Wasabi-class transactions: same analysis.
- `OP_RETURN`-bearing transactions: confirm the per-output fee does not break legitimate low-volume `OP_RETURN` use.
- Ordinary payments: per-output fee near zero relative to output value.
### C. Spam Efficacy
- Verify the static fee makes the documented value-vector spam pattern permanently uneconomical.
- Confirm no capital recovery path exists under the per-output fee mechanism.
- Model inscription-wave attacker economics **together with** the data-channel BIP: the static fee alone does not claim to have stopped 2023-2026 dedicated embedding.
### D. Consensus Edge Cases
- Confirm reorg behavior at activation height: blocks below `activation_height` are never subject to the fee rule, regardless of reorg depth.
- Confirm IBD and assumeutxo: activation height and static fee are reconstructable from soft fork parameters alone.
- Confirm integer arithmetic: satoshi amounts, 64-bit multiply of `static_fee × n_outputs`.
- Confirm coinbase exemption: the floor applies to non-coinbase transactions only; coinbase value uses existing subsidy-plus-fee rules.
- Confirm the floor is per-transaction `tx_fee`, not package or CPFP attribution.
### E. Wallet and Exchange Validation
- Share calibration results with at least one exchange wallet engineer and one Lightning implementation developer before proceeding.
- Confirm wallet fee estimation correctly sums weight-based fee and per-output fee into a single user-facing total.
- Confirm fee estimation APIs can be updated without breaking existing interfaces.
### F. Exit Criteria
- Static fee value confirmed and gate A passes, including the high-count stress test.
- Collateral checklist B passes at the recommended static fee.
- Spam efficacy checklist C confirms permanent cost on both vectors.
- Consensus edge cases in checklist D resolved and written into Specification.
---
## Security Considerations
**No dynamic manipulation surface.** The static fee is a constant. It has no sampling window, no moving average, and no parameter an attacker can influence through fee activity. That is the main security advantage of the static-only design.
**Soft fork boundary.** The floor restricts currently valid (low-fee) transactions. It does not mint coins. Blocks that meet the floor are valid to old nodes.
**Insufficient tx fee.** A transaction with `tx_fee < static_fee × n_outputs` is invalid. A block that includes it is invalid. Self-enforcing among enforcing nodes. CPFP cannot rescue the parent.
**Clean activation boundary.** The rule takes effect at `activation_height` with no grace window. The one-year minimum signaling window is enough for wallets and services to update before the rule applies. Transactions broadcast before `activation_height` that remain unconfirmed at that height must meet the floor to confirm. Wallets should watch approaching activation and rebroadcast or bump fees as needed.
**Residual incentive surfaces.** A transaction that misses the per-output floor is consensus-invalid. Including it does not produce an orphan; it produces a block that cannot exist. No side payment can make that transaction valid.
A miner can still accept the full fee and rebate part of it to the spammer after confirmation. That requires a sustained operational arrangement. The miner absorbs the rebate as a direct cost to coinbase revenue. Publicly broadcast transactions can be mined by anyone, so the spammer's effective throughput is limited by that miner's hashrate share.
A vertically integrated spammer-miner faces the same hashrate-share cap on self-inclusion and pays full fees when submitting publicly.
These are known residual vectors. The [dynamic escalation BIP](/bips/dynamic-escalation-per-output-fee) and [Permanent Data Channel Closure](/bips/permanent-data-channel-closure) address surfaces this proposal does not close. The three pre-proposals are complementary, not redundant.
**Static fee decay over time.** A fixed satoshi amount becomes economically trivial as BTC price and fee levels rise over decades. That is the known limit of the static-only design and the reason for the companion [dynamic escalation BIP](/bips/dynamic-escalation-per-output-fee). The static fee is not meant as a permanent final answer; it is the first layer the dynamic BIP builds on.
---
## Revision history
- 2026-10-27. An empty output list meets `static_fee × 0` and is still invalid. Bitcoin Core `CheckTransaction` rejects it (`bad-txns-vout-empty`).
- 2026-10-27. A child cannot fill a parent shortfall. The parent's own `tx_fee` must be at least `static_fee × n_outputs`.
- 2026-10-27. The 100-output row is 1,600 sats at 16 and 2,000 sats at 20. The vsize note under Parameters is a measurement of one transaction shape, not a new constant.
---
## References
- *[BIP Pre-Proposal: Dynamic Escalation of the Per-Output Miner Fee](/bips/dynamic-escalation-per-output-fee)* (Josh / Secure Sovereign, July 2026). Optional companion.
- *[BIP Pre-Proposal: Permanent Data Channel Closure](/bips/permanent-data-channel-closure)* (Josh / Secure Sovereign, August 2026).
- Bitcoin Core dust limit implementation (`GetDustThreshold` / `-dustrelayfee`; Core PRs #2577, #10817, #22863)
- *[Full Cost of Running a Bitcoin Node](/articles/full-cost-of-running-a-bitcoin-node)*, v2.4 (Josh / Secure Sovereign, July 2026). Source of per-node non-monetary burden ($5.52-$5.54/month) and network aggregate ($4M/year) figures.
- Mempool Research UTXO Set Report, May 2025, tip 892385 ([research.mempool.space/utxo-set-report](https://research.mempool.space/utxo-set-report)). Source of 29.6% inscription UTXO share and 51,188,145 inscription UTXO count.
- *[The Achievable Floor](/articles/the-achievable-floor)* (Josh / Secure Sovereign, 2026).
- *[Bitcoin Is Not a Hard Drive](/articles/bitcoin-not-a-hard-drive)* (Josh / Secure Sovereign, 2026).
- Lopp, Jameson. "Goldiblocks: A Dynamic Block Size Limit." OP_NEXT 2025.
- Various Delving Bitcoin and bitcoin-dev threads on UTXO bloat and spam mitigation (2023-2026)
---
## Copyright
This document is licensed under the BSD 2-Clause License.
---
# Dynamic Escalation of the Per-Output Miner Fee
## Contents
- [Abstract](#abstract)
- [Motivation](#motivation)
- [Specification](#specification)
- [Rationale](#rationale)
- [Backwards Compatibility](#backwards-compatibility)
- [Reference Implementation](#reference-implementation)
- [Calibration Checklist](#calibration-checklist)
- [Security Considerations](#security-considerations)
- [Revision history](#revision-history)
- [References](#references)
- [Copyright](#copyright)
---
## Abstract
This BIP adds a dynamic escalation layer on top of the static per-output miner fee from its predecessor. It has a hard consensus dependency on *[Static Per-Output Miner Fee](/bips/static-per-output-miner-fee)*: the dynamic rules are inert for any block at or below the static fee BIP's activation height, regardless of this BIP's own signaling or lock-in status. Until that height, this BIP adds no fee floor.
The problem is long-run decay. A static satoshi amount fixed under today's conditions becomes trivial as Bitcoin's price and fee levels rise over decades. Without automatic adjustment, the static fee stops working as a real disincentive, and the only fix is another soft fork to raise the constant. Repeated soft forks to update a fixed number create a permanent dependency on governance processes that can be captured, delayed, or blocked.
This BIP specifies a dynamic fee component derived from the 25th percentile fee rate sampled over 288-block windows, smoothed by an exponential moving average, confirmed by multi-window persistence, and bounded by an upward-only rate-of-change cap. The active per-output fee is the maximum of the static fee and the dynamic fee. When the scaled EMA is above `static_fee`, the dynamic fee governs, subject to the rate cap. When it is not, including the low corner of the provisional `k` range, `active_fee` stays on `static_fee`.
This BIP is an optional long-term upgrade to the static fee. The static fee BIP works fully without it. Dedicated embedding channels are closed by [Permanent Data Channel Closure](/bips/permanent-data-channel-closure), which does not depend on this BIP.
---
## Motivation
### The Known Limitation of the Static Fee
The static per-output miner fee closes both the value vector and the count vector of UTXO spam with a permanent, non-recoverable cost per output. It is the main piece of the fee layer. It has one known limit, already noted in its security considerations: a fixed satoshi amount decays in real terms as Bitcoin's price and fee levels rise.
At 20 sats per output and current BTC prices, creating 100,000 outputs costs 2 million sats. That is a material cost today. At 10x BTC price it is one-tenth the real cost. At 100x BTC price it approaches noise:
BTC price multiple
Cost of 100k outputs @ 20 sats
Real deterrent?
1× (today)
2,000,000 sats
Material
10×
2,000,000 sats (1/10 real cost)
Weakening
100×
2,000,000 sats (1/100 real cost)
Noise
Nominal sats stay fixed; real economic cost decays as BTC appreciates. Without automatic adjustment, another soft fork is eventually required.
The static fee does not need a fix today, but without automatic adjustment it will eventually need a soft fork. That soft fork will face the same political and review surface as any other consensus change, with the extra difficulty of being an explicit fee increase rather than a new capability.
The dynamic escalation layer removes that future dependency. It is calibrated to track multi-decade fee drift, not short-term fee spikes, so it adjusts slowly and predictably rather than reacting to noise.
### Why This Is a Separate BIP
The static fee is simple, small, and high-leverage. Putting the dynamic machinery in the same proposal raises implementation complexity, expands review surface, and raises the chance that neither piece activates. Splitting the proposals means the most important property, a permanent per-output cost, can land in consensus first. This BIP is the optional upgrade that keeps that cost from decaying over time.
Separation also lets the network gain operational experience with the static fee before adding the dynamic layer. If the static fee is enough in practice, the dynamic BIP may not need to activate on the same timeline. If the static fee decays faster than expected because of BTC price appreciation, the dynamic BIP has a clearer and more urgent case.
### Anti-Decay Is the Only Job of the Dynamic Layer
The dynamic component has one job: keep the static fee from becoming economically trivial over decades. It is not meant to respond to short-term spam waves, react to individual fee spikes, or replace the static fee as the primary deterrent. During short-term fee anomalies the dynamic fee should stay stable. During genuine multi-year fee drift it should move up. The design choices below (slow EMA, multi-window persistence, upward-only rate cap) all follow from that single role.
Division of labor in the fee layer
Static fee BIP
Primary deterrent
Fixed satoshi constant
No sampling / no manipulation surface
Fully functional alone
Dynamic escalation BIP
Anti-decay only
Tracks multi-decade fee drift
Can raise above static, never below
Optional long-term upgrade
Split so the permanent cost can activate first. Dynamic machinery is useful but not urgent.
---
## Specification
### Dependency
This BIP is only valid when *[Static Per-Output Miner Fee](/bips/static-per-output-miner-fee)* is active. If the static fee BIP has not activated, this BIP has no effect. Implementations must check for static fee BIP activation before applying dynamic escalation logic.
### Active Fee
The active per-output fee for any given 288-block period is:
```text
active_fee = max(static_fee, dynamic_fee)
```
Where `static_fee` is the constant from the static fee BIP and `dynamic_fee` is computed as specified below. The static fee BIP's validation rule is unchanged except that `static_fee` is replaced by `active_fee`:
```text
tx_fee >= active_fee × n_outputs
```
Coinbase accounting is unchanged from existing consensus. The dynamic amount is paid as ordinary `tx_fee`, not minted.
During any period in which the dynamic fee falls below or equals the static fee, the active fee equals the static fee and validation matches the static fee BIP.
### Period Alignment
A period is the half-open height interval `[n × 288, (n + 1) × 288)` for integer `n >= 0`, aligned to genesis (`height // 288`). The dynamic fee computed from the transactions in period `n − 1` applies to non-coinbase transactions in period `n`.
This BIP performs no dynamic computation until the first full 288-block period that begins at or after this BIP's `activation_height`. Until that boundary, `active_fee = static_fee`. If the static fee BIP is not yet active, this BIP is inert and adds no floor.
Initial state at the first computation boundary:
- `p25_ema_previous = 0`
- `dynamic_fee_previous = 0`
- `active_fee_previous = static_fee`
- `active_fee_current = static_fee`
Persistence requires two consecutive windows above threshold, so the first computed period cannot raise `dynamic_fee`. The second consecutive window can.
### Dynamic Fee Computation
The dynamic fee is computed at each 288-block boundary and cached for the following period. Computation happens only at boundaries, never per block.
| Condition | Result |
|---|---|
| Fewer than `min_tx_count` fee-paying transactions | Hold the previous EMA and dynamic fee. Step 3 does not run |
| Both the current and previous EMA are above `persistence_threshold` | `candidate_dynamic = raw`, then the rate cap of at most one quarter |
| Otherwise, and the sample is thick | `candidate_dynamic = min(dynamic_fee_previous, raw)`. This cannot raise the fee. It can lower it |
Then `active_fee = max(static_fee, dynamic_fee_new)`. The active fee cannot go below the static fee.
#### Step 1: Sample the fee rate
This step is the sole definition of fee sampling in the fee-layer BIPs. The static fee BIP needs no fee sampling; all fee rate computation starts here.
Collect the fee rate for every fee-paying transaction in the previous 288-block period. Fee rate is in milli-sat/vB as a non-negative integer:
```text
vsize = ceil(weight / 4) # vbytes, weight in WU
rate = floor(tx_fee * 1000 / vsize) # milli-sat per vB
```
`tx_fee` is `sum(input_values) - sum(output_values)` as in the static fee BIP. Exclude coinbase transactions. Exclude transactions with `tx_fee = 0`. Rate uses that transaction's own fee and weight only: no package or CPFP attribution.
Compute the 25th percentile of the resulting integer set. Sort ascending. For `N` samples, the 25th percentile is the element at index `floor((N − 1) × 25 / 100)` (0-based). No interpolation on even `N`. If the set has fewer than `min_tx_count` fee-paying transactions, **do not update** `p25_ema_previous` or `dynamic_fee_previous` (hold). Do not set them to zero. A thin sample must not collapse or freeze-from-zero the dynamic component. The period still advances: set `active_fee_previous = active_fee_current` so the grace window tracks the held fee. `active_fee_current` stays unchanged.
#### Step 2: Apply the exponential moving average
All EMA math is integer, toward zero:
```text
ALPHA_DEN = 1000
alpha_n =
p25_ema = (alpha_n × p25_current + (ALPHA_DEN − alpha_n) × p25_ema_previous) / ALPHA_DEN
```
A slow `alpha_n` toward 100 tracks multi-year fee drift while ignoring short-term spikes. Because the dynamic layer's only job is anti-decay over decades rather than short-term spam response, `alpha_n` must be tuned slow. A faster value toward 300 is appropriate only if sensitivity analysis shows a real benefit from faster response without instability.
#### Step 3: Apply multi-window persistence
```text
raw = (k × p25_ema_current) / 1000
if p25_ema_current > persistence_threshold
and p25_ema_previous > persistence_threshold:
candidate_dynamic = raw
else:
candidate_dynamic = min(dynamic_fee_previous, raw)
```
`persistence_threshold` is in milli-sat/vB, the same units as `p25_ema`. Truncation is toward zero. `k` is an integer scale, not the serialized size of an output. One elevated window cannot raise the dynamic fee. The else-branch cannot raise it either: `min` keeps the previous value when `raw` is larger. A thick sample below the threshold can lower it. `active_fee` still cannot go below `static_fee`. A sample shorter than `min_tx_count` holds the previous EMA and dynamic fee and does not take this branch.
#### Step 4: Apply the rate-of-change cap
```text
R_NUM = 1
R_DEN = 4 # R = 0.25 unless calibration sets otherwise
cap_base = max(dynamic_fee_previous, static_fee)
max_increase = cap_base + (cap_base × R_NUM) / R_DEN
dynamic_fee_new = min(candidate_dynamic, max_increase)
dynamic_fee_new = max(0, dynamic_fee_new)
```
All integer, toward zero. `cap_base` is never 0 while the static fee BIP is active, so a zero `dynamic_fee_previous` cannot trap the cap at 0. The first upward move is bounded by `static_fee × (1 + R)`, not by an uncapped jump to `candidate_dynamic`.
The dynamic fee may not increase faster than that bound per 288-block period. Decreases are uncapped: the dynamic fee falls freely back toward zero when fee conditions normalize, at which point the static fee governs.
#### Step 5: Apply the static fee floor
```text
active_fee = max(static_fee, dynamic_fee_new)
```
### Transaction Fee Floor During the Grace Window
The static fee BIP has no grace window at activation. This BIP changes `active_fee` every 288 blocks, so in-flight transactions need a short hold at period boundaries.
During the first `G` blocks of a new 288-block period, the required floor is the previous period's `active_fee`. After `G` blocks, the new period's `active_fee` applies. Coinbase rules are unchanged.
```text
if block_height < period_start + G:
required_fee = active_fee_previous_period
else:
required_fee = active_fee_current_period
tx_fee >= required_fee × n_outputs
```
### Consensus State
Each node must carry the following state across 288-block period boundaries, in addition to the static fee BIP's activation state:
- `dynamic_fee_previous` (the dynamic fee from the prior period)
- `p25_ema_previous` (the EMA value from the prior period)
- `active_fee_previous` (for grace window floor)
- `active_fee_current` (the active fee for the current period)
All values are deterministic from block history and need no external input. Implementations must also retain EMA state snapshots at every period boundary for the most recent 2,016 blocks of boundaries to support reorg recovery, as specified in Security Considerations.
### Parameters
All parameters are consensus parameters adjustable by a future soft fork. Initial values are provisional pending calibration.
Parameter
Description
Provisional value
k
Integer vbyte scale from p25 EMA (milli-sat/vB) to sat per output
2-4
alpha_n
EMA numerator over 1000 (100 = α 0.1)
100-300 (tune slow)
persistence_threshold
Minimum p25 EMA (milli-sat/vB) for a window to count toward persistence
TBD via calibration
R_NUM / R_DEN
Maximum upward rate of change per period
1/4
G
Grace window in blocks at period boundaries
6-12
min_tx_count
Minimum fee-paying transactions for a valid sample
1,000
Prefer slow alpha_n unless sensitivity tables show a real benefit from faster response without instability. k is a scale, not output vsize.
### Activation
This BIP is meant to deploy via a soft fork using BIP-8 or BIP-9 style signaling, with a minimum activation window of one year and no mandatory lock-in fallback. Miners who do not signal are not penalized.
This BIP has an explicit consensus dependency: it is inert for any block whose height is less than or equal to the static fee BIP's `activation_height`, regardless of this BIP's own signaling or lock-in status. Until the static fee BIP is active, `active_fee` is not applied by this BIP (the static BIP's floor is also absent). After the static fee BIP is active and this BIP has completed its first full 288-block period, `active_fee = max(static_fee, dynamic_fee)` as specified. Signaling order is not enough; implementations must enforce the height dependency at the consensus layer.
BIP-8/9 without lock-in-on-timeout is miner signaling. Node-operator interest is not the threshold. User-activated soft fork deployment is a separate choice and is not specified here.
---
## Rationale
### Why 288 Blocks as the Sample Window
The dynamic fee's job is tracking multi-decade fee drift, not reacting to short-term spam waves. A 288-block (~2 day) window provides enough transactions for a statistically meaningful 25th percentile during active periods, while staying short enough to detect genuine sustained changes without unreasonable lag. Combined with the EMA, the effective response time to sustained fee changes is much longer than 288 blocks regardless of window size.
### Why the 25th Percentile
The 25th percentile represents cheaper legitimate transactions and is less sensitive to outliers than the median. A small number of high-fee transactions cannot push it far upward, which keeps the dynamic fee from pricing out legitimate use during fee spikes driven by monetary activity rather than spam.
### Why EMA Rather Than Hard Window Reset
A hard window reset creates cliff-edge transitions and makes the fee reactive to single-window anomalies. The EMA smooths toward prevailing conditions over many periods, which is the right behavior for a mechanism tracking multi-decade drift rather than reacting to individual events.
### Why Multi-Window Persistence
A single elevated 288-block window is achievable by a moderately funded actor for whom fee spend is an acceptable operating cost. Requiring two consecutive windows doubles the sustained cost and duration of any manipulation attempt. The persistence check adds no per-block computation and is the main defense against short-term fee flooding aimed at ratcheting the dynamic fee upward.
### Why an Upward-Only Rate-of-Change Cap
Even with EMA smoothing and persistence, a sustained campaign could ratchet the dynamic fee upward over many periods. The rate cap bounds how fast that can happen regardless of fee pressure: even a perfectly sustained campaign can raise the dynamic fee by only `R` percent per period, so rapid ratcheting is slow, expensive, and publicly visible on chain. The cap is asymmetric on purpose: the dynamic fee falls freely when pressure stops, so a manipulation attempt does not leave a permanently elevated floor once the attacker withdraws.
### Why k Is a Scale, Not Output Size
The p25 EMA is in milli-sat/vB. Multiplying by an integer `k` and dividing by 1000 produces sats per output. Dimensionally `k` has units of vbytes, but it is **not** set to the serialized size of a P2WPKH or P2TR output (31–43 vB). Using literal output vsize would make `dynamic_fee` track weight fees one-for-one and would overprice Lightning and CoinJoin during congestion. Calibration sets `k` so that at a reference p25 of about 5 to 10 sat/vB, `dynamic_fee` is the same order as `static_fee` (provisional `k` in 2–4). The products at the corners of that rectangle, before the rate cap and before `max(static_fee, ·)`, are:
| `k` | p25 | Scaled sats per output | Against static 16 and 20 |
|---|---|---|---|
| 2 | 5 sat/vB | 10 | Below both. The static fee governs |
| 4 | 5 sat/vB | 20 | Equals the high endpoint |
| 2 | 10 sat/vB | 20 | Equals the high endpoint |
| 4 | 10 sat/vB | 40 | Above both. Step 4 caps the first rise |
A single `k` matches the static fee's uniform-per-output model: the externalized cost being priced is per UTXO slot, not per script type.
### Interaction with Permanent Data Channel Closure
The [Permanent Data Channel Closure](/bips/permanent-data-channel-closure) pre-proposal targets dedicated high-bandwidth data channels. This BIP targets UTXO creation economics. They operate on different surfaces. Dynamic escalation does not change that split. See *[The Achievable Floor](/articles/the-achievable-floor)* and *[Bitcoin Is Not a Hard Drive](/articles/bitcoin-not-a-hard-drive)*.
---
## Backwards Compatibility
The active fee replaces the static fee in the per-transaction floor. During any period in which the dynamic fee is below the static fee, validation matches the static fee BIP. The dynamic layer is additive: it can only raise the active fee above the static fee floor, never below it.
Wallets and fee estimators that already account for the static per-output fee must also track the current period's active fee, which may differ from the static fee during elevated fee conditions. From the user's point of view there is still one fee; wallets present a single total that uses whichever of the two rates is currently required, including the grace-window hold at period boundaries.
---
## Reference Implementation
High-level pseudocode, assuming the static fee BIP is active:
```python
STATIC_FEE =
ALPHA_N = 100
ALPHA_DEN = 1000
K = <2-4 pending calibration>
R_NUM, R_DEN = 1, 4
MIN_TX_COUNT = 1000
G = <6-12>
RATE_SCALE = 1000 # milli-sat/vB
def tx_vsize(tx):
return (tx.weight + 3) // 4
def tx_fee(tx):
return sum(inp.value for inp in tx.inputs) - sum(out.value for out in tx.outputs)
def sample_rates(period_blocks):
rates = []
for block in period_blocks:
for tx in block.transactions:
if tx.is_coinbase or tx_fee(tx) == 0:
continue
rates.append((tx_fee(tx) * RATE_SCALE) // tx_vsize(tx))
rates.sort()
return rates
def percentile_25(rates):
n = len(rates)
return rates[(n - 1) * 25 // 100]
def compute_period_active_fee(last_288_blocks, state):
rates = sample_rates(last_288_blocks)
if len(rates) < MIN_TX_COUNT:
state.active_fee_previous = state.active_fee_current
return state.active_fee_current # hold ema and dynamic_fee; rotate grace window
p25_current = percentile_25(rates)
p25_ema = (ALPHA_N * p25_current + (ALPHA_DEN - ALPHA_N) * state.p25_ema_previous) // ALPHA_DEN
raw = (K * p25_ema) // RATE_SCALE
if (p25_ema > PERSISTENCE_THRESHOLD and
state.p25_ema_previous > PERSISTENCE_THRESHOLD):
candidate = raw
else:
candidate = min(state.dynamic_fee_previous, raw)
cap_base = max(state.dynamic_fee_previous, STATIC_FEE)
max_increase = cap_base + (cap_base * R_NUM) // R_DEN
dynamic_fee = min(candidate, max_increase)
dynamic_fee = max(0, dynamic_fee)
active_fee = max(STATIC_FEE, dynamic_fee)
state.p25_ema_previous = p25_ema
state.dynamic_fee_previous = dynamic_fee
state.active_fee_previous = state.active_fee_current
state.active_fee_current = active_fee
return active_fee
def required_fee(block_height, period_start, state):
if block_height < period_start + G:
return state.active_fee_previous
return state.active_fee_current
def is_valid_transaction(tx, block_height, period_start, state):
if tx.is_coinbase:
return True
return tx_fee(tx) >= required_fee(block_height, period_start, state) * len(tx.outputs)
```
Detailed test vectors, integer arithmetic precision requirements, and edge-case handling will be provided in a future numbered BIP submission.
---
## Calibration Checklist
This checklist is separate from and follows the static fee BIP's calibration. The static fee BIP's calibration must pass before this checklist begins.
### A. Dynamic Parameter Sensitivity
- Sweep `alpha_n` in {50, 100, 200, 300} × `R` in {1/10, 1/4, 1/2} × `k` in {2, 3, 4} against full chain history.
- For each combination report: number of periods where dynamic fee exceeds static fee; maximum dynamic fee reached; EMA lag to a sustained 10x fee increase; periods required to ratchet 2x under simulated sustained fee pressure.
- Recommend a default parameter tuple only after sensitivity tables exist. Prefer slow `alpha_n` unless tables show a real benefit from faster response.
- Calibrate `persistence_threshold` above the noise floor of quiet periods and below the movement threshold for genuine sustained congestion.
- At the recommended parameters, report the periods where the scaled EMA is above `static_fee` and the periods where it is not. The low corner of the provisional range (`k = 2`, 5 sat/vB) is 10 sats, below both static endpoints, so `active_fee` stays on `static_fee` there. Do not treat "always above static" as a passing condition.
### B. Anti-Manipulation Stress Test
- Simulate a moderately funded attacker sustaining elevated p25 fee rates for 2, 4, 8, and 16 consecutive 288-block windows. Report dynamic fee trajectory and cost to the attacker at each duration.
- Confirm the rate-of-change cap prevents rapid ratcheting even under sustained pressure.
- Confirm the dynamic fee falls freely back to the static fee floor once pressure is removed, with no persistent elevation.
### C. Collateral Damage at Dynamic Rates
- Lightning channel opens: confirm the active fee remains negligible at the 95th and 99th percentile of simulated dynamic fee values under historical and projected fee conditions.
- Exchange batch payouts: same analysis.
- Confirm the dynamic fee does not price out legitimate high-output transactions during fee spikes driven by monetary activity rather than spam.
### D. Consensus Edge Cases
- Specify behavior on reorgs crossing 288-block period boundaries: which period's EMA state and active fee apply to disconnected blocks.
- Specify IBD and assumeutxo interaction: EMA state must be fully reconstructable from block history alone without mempool history.
- Specify integer arithmetic precisely (milli-sat/vB rates, EMA division toward zero, `k × ema / 1000`, rate cap via `cap_base = max(previous, static_fee)`) so all implementations agree bit-for-bit.
- Define the identical percentile algorithm specified in Step 1 (sort ascending, index `floor((N − 1) × 25 / 100)`, no interpolation).
- Confirm grace window `G` is sufficient at period boundaries given historical mempool boundary-crossing data.
- Confirm periods are genesis-aligned `[n×288, (n+1)×288)` and the first full period after activation is the first computation window.
### E. Exit Criteria
- Recommended (`k`, `alpha_n`, `R_NUM/R_DEN`, `persistence_threshold`, `G`, `min_tx_count`) published with full sensitivity tables.
- Anti-manipulation stress test B passes at recommended parameters.
- Collateral damage checklist C passes at recommended parameters.
- Consensus edge cases in checklist D resolved and written into Specification.
---
## Security Considerations
**Fee rate manipulation.** Moving the 25th percentile meaningfully requires sustaining elevated transaction volume across a full 288-block window. The three-layer dynamic architecture (EMA, persistence, rate cap) makes rapid ratcheting slow, expensive, and publicly visible on chain. A state-level actor treating fee spend as an operating cost can still move the dynamic fee upward over many periods; the cap bounds how fast, and the fee falls freely once pressure is removed.
**Static fee as irreducible floor.** The dynamic fee can never push the active fee below the static fee. The static fee BIP's security properties are fully preserved regardless of what the dynamic layer does.
**Low-activity window.** If the 288-block sample contains fewer than `min_tx_count` fee-paying transactions, EMA and `dynamic_fee` are held, not zeroed. Zeroing would re-introduce a from-zero rate-cap trap. The static fee still floors `active_fee`. A sample that meets `min_tx_count` but sits below `persistence_threshold` is not this case. Step 3 lowers `dynamic_fee` to `min(dynamic_fee_previous, raw)`. Holding the old value would freeze an elevated fee after the pressure stops.
**Period boundary floor.** The grace window keeps the required per-transaction floor unambiguous at every period boundary. The previous period's `active_fee` governs during the grace window; the new rate governs after. Coinbase value is not part of this BIP.
**Rate cap from zero.** `cap_base = max(dynamic_fee_previous, static_fee)` so a zero previous dynamic fee cannot pin `max_increase` at 0.
**Reorg safety.** On a reorg crossing a 288-block period boundary, the EMA state must revert to the correct state for the reorganized chain tip. Implementations must cache EMA state snapshots at every period boundary. The consensus rule is: retain snapshots for the most recent 2,016 blocks (one difficulty adjustment period, about two weeks) of period boundaries. That bounds the cache to at most seven snapshots at any time and covers any reorg that Bitcoin's proof-of-work economics makes plausible, without relying on heuristic depth estimates. A reorg deeper than 2,016 blocks is treated as a chain split requiring operator intervention, consistent with existing Bitcoin consensus assumptions. Implementations that do not retain the required snapshots cannot correctly validate blocks after a deep reorg and must re-sync from a known-good checkpoint.
---
## Revision history
- 2026-10-27. If persistence fails, `candidate_dynamic` is `min(dynamic_fee_previous, raw)`. A thick sample below the threshold can lower the dynamic fee. A raise still needs two consecutive windows. A sample shorter than `min_tx_count` still holds. Worked fixture, not a consensus constant: `static_fee = 20`, `k = 4`, threshold 5,000 milli-sat/vB, previous dynamic fee 80, then two windows of rates at 1,000 milli-sat/vB. The candidate falls to 4, and `active_fee` returns to the static fee.
- 2026-10-27. At `k = 2` and 5 sat/vB the scaled value is 10 sats, below both provisional static endpoints, so `active_fee` stays on `static_fee`.
---
## References
- *[BIP Pre-Proposal: Static Per-Output Miner Fee](/bips/static-per-output-miner-fee)*. This BIP depends on it.
- *[BIP Pre-Proposal: Permanent Data Channel Closure](/bips/permanent-data-channel-closure)* (Josh / Secure Sovereign, August 2026).
- *[Full Cost of Running a Bitcoin Node](/articles/full-cost-of-running-a-bitcoin-node)*, v2.4 (Josh / Secure Sovereign, July 2026).
- Mempool Research UTXO Set Report, May 2025, tip 892385 ([research.mempool.space/utxo-set-report](https://research.mempool.space/utxo-set-report)).
- *[The Achievable Floor](/articles/the-achievable-floor)* (Josh / Secure Sovereign, 2026).
- *[Bitcoin Is Not a Hard Drive](/articles/bitcoin-not-a-hard-drive)* (Josh / Secure Sovereign, 2026).
- Lopp, Jameson. "Goldiblocks: A Dynamic Block Size Limit." OP_NEXT 2025.
- Various Delving Bitcoin and bitcoin-dev threads on UTXO bloat and spam mitigation (2023-2026)
---
## Copyright
This document is licensed under the BSD 2-Clause License.
---
# Permanent Data Channel Closure
## Contents
- [Abstract](#abstract)
- [Motivation](#motivation)
- [Specification](#specification)
- [Unreferenced push analysis](#unreferenced-push-analysis)
- [Witness item classification](#witness-item-classification)
- [Rationale](#rationale)
- [Backwards Compatibility](#backwards-compatibility)
- [Reference Implementation](#reference-implementation)
- [Calibration Checklist](#calibration-checklist)
- [Appendix A. `stack_items_read`](#appendix-a-stack_items_read)
- [Security Considerations](#security-considerations)
- [Revision history](#revision-history)
- [References](#references)
- [Copyright](#copyright)
---
## Abstract
This BIP is a permanent soft fork with no expiry. It closes dedicated output templates and unenforced upgrade hooks used for bulk non-monetary data. The table is the disposition of each path. The rules below are the normative text.
Path
Result
OP_RETURN above 83 bytes, bare multisig, other non-templates
Closed
Annex, undefined versions, OP_SUCCESS, control block above 257, tapscript OP_IF, dead pushes, non-empty P2A witness
Closed
A live push an opcode reads and then ignores. The script-body caps are still TBD
Bounded
A 0x50 item that is not last. Rule 2 caps that item at 256 bytes
Bounded
Data inside a P2SH redeemScript (520 bytes per element, 10,000 per script)
Bounded
The same payload split across transactions
Priced
Hashes, amounts, nSequence, nLockTime, ordering, and coinbase scriptSig
Open
Closed means the spend or output is invalid. Bounded means today's size limits or a cap that is still TBD. Priced means each transaction pays the static per-output fee. Open means the field stays valid because a payment uses it.
Individual script-argument items are capped at 256 bytes. Aggregate witness caps and script-body push caps are part of the rule set and are not yet numbers. BIP141 witness weight is unchanged. A pre-activation UTXO remains spendable, including one reveal of data already committed in that coin. That spend does not authorize new envelopes.
This BIP is designed to work in conjunction with the [Static Per-Output Miner Fee](/bips/static-per-output-miner-fee) and [Dynamic Escalation of the Per-Output Miner Fee](/bips/dynamic-escalation-per-output-fee) pre-proposals. Those BIPs price UTXO creation. This BIP closes the dedicated templates and unenforced hooks that would otherwise let a few transactions carry the payload. The fee BIPs price output count, including a payload split across many transactions. The caps that are still TBD do not become numbers by activating the fee.
---
## Motivation
### The Problem
Bitcoin has no consensus rule preventing arbitrary data from being embedded in transactions. Policy filters and relay rules can be bypassed by routing through a miner who does not enforce them. That is why data embedding debates have continued without resolution. Policy binds willing participants. Consensus binds everyone.
Starting with the inscription technique first exploited in 2022, a sustained trend has emerged around embedding arbitrary data into Bitcoin transactions. Ordinals, BRC-20 tokens, Runes, and similar protocols use Bitcoin as a data store rather than a monetary network. This creates significant and permanent burdens on node operators: storage, bandwidth, and RAM costs that fall on roughly 60,000 full nodes, none of whom were compensated for accepting that burden.
Pruning can drop old blocks from disk. It does not skip the download at first sync. *[Full Cost of Running a Bitcoin Node](/articles/full-cost-of-running-a-bitcoin-node)* (v2.4, July 2026) estimates the aggregate non-monetary burden on the node network at approximately $4 million per year.
The core externality is structural. The actor embedding data pays a miner once. The burden of storing and serving that data falls on every node operator indefinitely. No market mechanism corrects this because node operators receive no part of the miner fee and have no mechanism to refuse specific content at the consensus layer.
### The Two Embedding Surfaces
Data embedding operates on two surfaces that require different consensus tools to close.
The first is the per-item surface: individual data fields large enough to carry meaningful payloads. Output scriptPubKeys, OP_PUSHDATA payloads, witness stack items, Taproot annexes, and control blocks have all been exploited as single-field embedding vectors. Capping each field at a size that is sufficient for legitimate cryptographic use but insufficient for image-scale payloads closes this surface.
The second is the fragmentation surface: multiple sub-cap items assembled by an off-chain indexer into a larger payload. A per-item cap creates a window of permitted size per push. A transaction can contain many inputs, each with many witness stack items. An image or arbitrary file can be reconstructed from a sequence of small chunks distributed across witness fields in one transaction or spread across multiple transactions with a reassembly index maintained off-chain. Per-item caps raise the cost and complexity of embedding; they do not close the channel.
Per-item caps and aggregate caps are both required. The aggregate caps close fragmentation inside one transaction once they are calibrated. Fragmentation across transactions stays valid under any finite per-transaction cap. The static per-output fee prices each of those transactions.
### Why Permanent Rules Are the Right Mechanism
A temporary consensus rule creates an expiry event that the data-embedding ecosystem can plan around. Tooling can be built for the post-expiry environment, and activity resumes the moment the rule lapses. A permanent rule removes that planning horizon entirely and eliminates the repeated soft-fork cost of re-litigating the same question on a cycle.
The underlying principle does not weaken over time: node operators should not bear the indefinite cost of arbitrary data storage initiated by parties who paid miners once and never compensated them. The rule should match the principle.
### The Fragmentation Surface in Detail
Two fragmentation paths matter, and they are not closed the same way.
The within-transaction path uses multiple witness stack items, each within the per-item cap, within a single transaction. No existing consensus rule limits the count of such items or their aggregate byte total per input or per transaction. Rules 8 and 9 are that limit. The numbers are TBD.
The cross-transaction path splits a payload across multiple transactions, each carrying one or more small chunks, with a reassembly index maintained off-chain. Each transaction can sit under Rules 8 and 9. The Ordinals developer community published fragmentation tooling for this path. This BIP does not reject it. The static per-output fee prices every transaction in the split.
### The Interaction With the Per-Output Fee BIPs
The [Static Per-Output Miner Fee](/bips/static-per-output-miner-fee) prices every new non-coinbase output permanently. The [Dynamic Escalation](/bips/dynamic-escalation-per-output-fee) layer keeps that price from decaying. Together they make UTXO creation costly in sats, permanently and irrecoverably.
Without data channel closure, a spammer facing the per-output fee can minimize output count while maximizing payload per output by fragmenting data within the witness fields of a small number of transactions. The fee BIPs price outputs; they do not directly price witness bytes. This BIP closes that gap. With all three proposals active, the available surface for data embedding is narrow, the per-output cost is permanent, and fragmentation increases the transaction count and thus the aggregate fee burden rather than routing around it.
---
## Specification
### Permanent Deployment
The rules in this BIP have no expiry. They take effect at `activation_height` and remain in effect for all subsequent blocks. There is no `active_duration` parameter and no EXPIRED state. The deployment transitions from ACTIVE to a permanent terminal state with continued enforcement, not expiry.
### UTXO Grandfathering
Spend-side rules and output-side rules are not the same exemption.
**Output rules (Rule 1).** Apply to every transaction output created in a block at or above `activation_height`, including coinbase outputs. A transaction that spends only pre-activation UTXOs still may not create a non-template scriptPubKey. One old input does not exempt new outputs.
**Spend rules (Rules 2 through 13).** Apply only to inputs whose prevout was created at or after `activation_height`. Inputs spending UTXOs created before `activation_height` are exempt from Rules 2 through 13 so those coins are not frozen. That exemption is per input and covers only the spend of that already-created UTXO. It is not a license to mint new inscriptions.
A pre-activation envelope UTXO may still reveal its committed witness when it is spent. The next outputs in that same transaction are new. They must satisfy Rule 1. When those new outputs are later spent, Rules 2 through 13 apply. Funding a new P2TR from old coins does not grandfather the new output's spend: P2TR is a valid template, but an inscription-style witness on that later spend is invalid.
Mixed transactions are valid if every new output satisfies Rule 1 and every post-activation input satisfies Rules 2 through 13.
Coinbase `scriptSig` / extraNonce is out of scope. The coinbase transaction has no prevout, so Rules 2 through 13 do not apply to it. Rule 1 still applies to coinbase outputs.
### Rule Set
The following rules apply to all blocks at or above `activation_height`. The paragraphs are the rule. This table is the index.
| Rule | Check |
|---|---|
| 1 | `scriptPubKey` is a listed template, or `OP_RETURN` of at most 83 bytes |
| 2 | A script-argument item is at most 256 bytes, except the BIP16 redeemScript push |
| 3 | Spending an undefined witness version or Tapleaf version |
| 4 | A Taproot annex |
| 5 | A control block longer than 257 bytes |
| 6 | `OP_SUCCESS` anywhere in a tapscript |
| 7 | `OP_IF` or `OP_NOTIF` anywhere in a tapscript |
| 8 | Script-argument witness bytes per transaction. The cap is TBD |
| 9 | Script-argument witness bytes per post-activation input. The cap is TBD |
| 10 | An unreferenced push in a Tapleaf script |
| 11 | Push bytes in a Tapleaf script. The cap is TBD. This bounds a push that an opcode reads and then ignores |
| 12 | An unreferenced push in a P2WSH witness script. A branch-end key is referenced when the signature check consumes it |
| 13 | Push bytes in a P2WSH witness script. The cap is TBD |
**Rule 1.** Every output `scriptPubKey` created at or after `activation_height` must be exactly one of the templates below, or a valid OP_RETURN output as defined here. Any other `scriptPubKey` is invalid. Templates are byte-exact (push opcodes must be the minimal opcode for that length; `OP_PUSHDATA1` for a 20-byte hash is not P2PKH).
| Name | `scriptPubKey` |
|---|---|
| P2PK compressed | `OP_PUSHBYTES_33 {33-byte pubkey} OP_CHECKSIG` |
| P2PK uncompressed | `OP_PUSHBYTES_65 {65-byte pubkey} OP_CHECKSIG` |
| P2PKH | `OP_DUP OP_HASH160 OP_PUSHBYTES_20 {20-byte hash} OP_EQUALVERIFY OP_CHECKSIG` |
| P2SH | `OP_HASH160 OP_PUSHBYTES_20 {20-byte hash} OP_EQUAL` |
| P2WPKH | `OP_0 OP_PUSHBYTES_20 {20-byte hash}` |
| P2WSH | `OP_0 OP_PUSHBYTES_32 {32-byte hash}` |
| P2TR | `OP_1 OP_PUSHBYTES_32 {32-byte x-only pubkey}` |
| P2A | `OP_1 OP_PUSHBYTES_2 0x4e73` (BIP 433) |
**OP_RETURN.** A valid OP_RETURN output has `len(scriptPubKey) <= 83` bytes, the first opcode is `OP_RETURN` (0x6a), and the remainder is at most one data push (opcodes `OP_0`, `OP_1NEGATE`, `OP_1`–`OP_16`, or a single `OP_PUSHBYTES` / `OP_PUSHDATA1` / `OP_PUSHDATA2` with its payload). No further opcodes. 83 bytes is the `scriptPubKey` length (historical Core datacarrier), not 83 bytes of payload. Multiple OP_RETURN outputs in one transaction are each subject to this cap.
Bare multisig and all other non-template forms are invalid.
**Rule 2.** On inputs whose prevout was created at or after `activation_height`, individual OP_PUSHDATA payloads in that input's `scriptSig` and script-argument witness items exceeding 256 bytes are invalid, except for the redeemScript push in BIP16 scriptSigs. Script-argument witness items are witness stack elements passed to the script interpreter as inputs, excluding witness scripts, Tapleaf scripts, control blocks, annexes, and Taproot key-path signatures. Rule 2 does not apply to `scriptPubKey` (Rule 1) or to grandfathered inputs.
**Rule 3.** Spending undefined witness versions or Tapleaf versions is invalid. Creating outputs with undefined witness versions is already invalid under Rule 1: those scriptPubKeys are not a defined template. A future soft fork that defines a new witness version must add the corresponding template to the Rule 1 whitelist in the same deployment that defines spending rules. There is no pre-creation window.
**Rule 4.** Witness stacks with a Taproot annex are invalid.
**Rule 5.** Taproot control blocks larger than 257 bytes are invalid.
**Rule 6.** Tapscripts including OP_SUCCESS opcodes anywhere, even unexecuted, are invalid.
**Rule 7.** Tapscripts containing OP_IF or OP_NOTIF anywhere, even unexecuted, are invalid. This ban is tapscript only. P2WSH branching is classified by Rule 12.
**Rule 8.** The aggregate byte count of all script-argument witness items across **post-activation inputs only** in a single transaction must not exceed `max_witness_bytes_per_tx`. Grandfathered inputs are omitted. The same exclusions as Rule 2 apply. A transaction where that aggregate exceeds `max_witness_bytes_per_tx` is invalid.
**Rule 9.** The aggregate byte count of all script-argument witness items within a single **post-activation** input must not exceed `max_witness_bytes_per_input`. Grandfathered inputs are omitted. The same exclusions as Rule 2 apply. An input where the aggregate exceeds `max_witness_bytes_per_input` is invalid.
**Rule 10.** Tapleaf scripts containing unreferenced push data are invalid. The determination is static, without execution, using the algorithm in [Unreferenced push analysis](#unreferenced-push-analysis) with `kind = TAPSCRIPT` ([Appendix A](#appendix-a-stack_items_read)).
**Rule 11.** Tapscripts containing push constants whose aggregate byte count exceeds `max_tapleaf_push_bytes` are invalid, as a secondary enforcement layer on Tapleaf script body size independent of the unreferenced push analysis in Rule 10. This cap is load-bearing for consume-and-ignore patterns (for example `OP_PUSH` followed by `OP_DROP`) that Rule 10 treats as referenced.
**Rule 12.** Segwit v0 witness scripts (the last witness stack item on P2WSH spends) containing unreferenced push data are invalid. The static analysis is the same as Rule 10 with `kind = WITNESS_V0`, including the branch-end exception in [Unreferenced push analysis](#unreferenced-push-analysis): a key or key-hash immediately followed by `OP_ELSE` or `OP_ENDIF` is referenced only when a signature check on every branch that executes it consumes that same push. That exception does not apply to tapscript. Rule 7 still rejects every tapscript `OP_IF` and `OP_NOTIF`.
**Rule 13.** Segwit v0 witness scripts containing push constants whose aggregate byte count exceeds `max_witness_script_push_bytes` are invalid. This is the P2WSH counterpart to Rule 11. Witness scripts remain excluded from Rules 2, 8, and 9: those rules cap script-argument items, not script bodies.
### Unreferenced push analysis
Used by Rules 10 and 12. Walk the script as a sequence of opcodes plus immediate payloads. A **push** is any of: `OP_0`, `OP_1NEGATE`, `OP_1` through `OP_16`, a direct push `0x01`–`0x4b`, `OP_PUSHDATA1`, `OP_PUSHDATA2`, or `OP_PUSHDATA4`.
Classification walks every **live path**. The next opcode is consulted with one branch-end exception. `OP_ELSE` and `OP_ENDIF` have `stack_items_read = 0`. A push immediately in front of either one is referenced when all of the following hold:
- The push is a key or a key-hash. In `WITNESS_V0` a key is 33 or 65 bytes and a key-hash is 20 bytes. In `TAPSCRIPT` a key is 32 bytes and a key-hash is 20 bytes. Rule 7 still rejects every tapscript `OP_IF` / `OP_NOTIF`, so the tapscript lengths are not a way around that ban.
- Every reachable branch that executes the push terminates in `OP_CHECKSIG`, `OP_CHECKSIGVERIFY`, `OP_CHECKSIGADD`, `OP_CHECKMULTISIG`, or `OP_CHECKMULTISIGVERIFY`.
- That opcode consumes the same push. A pubkey argument consumes a key. `OP_EQUAL` / `OP_EQUALVERIFY` consumes a key-hash when the same path also reaches a signature opcode. `OP_CHECKMULTISIG` consumes each key it pops.
BOLT 3 `to_local` is this case: `` is followed by `OP_ELSE`, `` is followed by `OP_ENDIF`, and `OP_CHECKSIG` after `OP_ENDIF` consumes whichever key that branch pushed. Regtest Core v28.1 accepted a delay-1 `to_local` spend, a 2-of-2 funding spend, and an offered-HTLC preimage spend. The same walk accepts `to_remote` with CSV, the anchor `OP_IFDUP` script, and the received HTLC. A key in front of `OP_ELSE` with no signature check, and any non-key in front of `OP_ELSE` or `OP_ENDIF`, stays unreferenced.
A path is live when its `OP_IF` / `OP_NOTIF` condition is not a script constant, or when it is the arm `CastToBool` selects. `CastToBool` is Core's rule: empty and negative zero are false; any other byte is true. The arm a constant condition does not take is dead. A push that no live path executes is unreferenced. That is `OP_FALSE OP_IF OP_ENDIF`, including ` OP_DROP` inside the dead arm.
On a live path, a push is referenced if an opcode on that path reads it. The read is `stack_items_read`, then the Appendix A tail when the count is a script constant:
- `OP_CHECKMULTISIG` / `OP_CHECKMULTISIGVERIFY` in `WITNESS_V0` pop `3 + nKeys + nSigs` items: `nKeys`, the keys, `nSigs`, the signatures, and the dummy. Tapscript still fails these opcodes before the walk (Appendix A step 2).
- `OP_PICK` / `OP_ROLL` require depth 2, pop `n`, and read the slot `n` down. `OP_ROLL` removes that item. Both push it.
Witness items that are not pushes in this script are external. Popping one does not mark a script push.
A script push still on the stack at the end of a live path, and not read, is unreferenced. Exception: the only stack item left has a payload of at most 4 bytes and `CastToBool` is true (the `CScriptNum` input limit in `interpreter.cpp`). That covers a witness script whose success value is `OP_1` or another small number. A 400-byte push left as the whole script is unreferenced. Core accepted that spend on regtest.
`OP_PUSH` / `OP_DROP` on a live path is referenced. Rules 11 and 13 cap it. They do not apply to a dead arm; the dead arm is already invalid.
`OP_2 OP_2 OP_CHECKMULTISIG` stays valid: every push is read. Consecutive pushes are not exempt as a class. A push is unreferenced when nothing reads it, including a push that sits beside one that is read (` OP_DROP` leaves ``).
If a live path exceeds 64 states, or a `CHECKMULTISIG` count or an `OP_PICK` / `OP_ROLL` `n` on that path is not a script constant, leftovers on that path are not flagged. A push that no live path executes is still unreferenced. Rules 6, 7, 11, and 13 still apply.
`stack_items_read(opcode, kind)` is defined for every byte `0x00`–`0xFF` in [Appendix A](#appendix-a-stack_items_read). Rule 10 uses `kind = TAPSCRIPT`. Rule 12 uses `kind = WITNESS_V0`. The value is the opcode's first `stack.size()` check in `EvalScript`. The tails for `OP_PICK`, `OP_ROLL`, and the two multisig opcodes are in Appendix A. Replacement versus deletion does not matter. `OP_DUP`, `OP_DROP`, `OP_IF`, `OP_SIZE`, and `OP_CHECKLOCKTIMEVERIFY` are all `>= 1`. `OP_NOP`, `OP_DEPTH`, `OP_FROMALTSTACK`, `OP_ELSE`, `OP_CODESEPARATOR`, disabled opcodes, `OP_RETURN`, and unknown bytes are `0`.
Tapscript `OP_SUCCESS` bytes have `stack_items_read = 0` and are independently invalid under Rule 6. Core returns success on the first such byte, before a later truncated push would be a parse error. Rule 6 uses that same order.
### Parameters
| Parameter | Description | Value |
|---|---|---|
| `max_witness_bytes_per_input` | Aggregate script-argument witness byte cap per input | TBD via calibration |
| `max_witness_bytes_per_tx` | Aggregate script-argument witness byte cap per transaction | TBD via calibration |
| `max_tapleaf_push_bytes` | Aggregate push constant byte cap per Tapleaf script body | TBD via calibration |
| `max_witness_script_push_bytes` | Aggregate push constant byte cap per P2WSH witness script body | TBD via calibration |
| `activation_height` | Set by signaling process | Determined at deployment |
Provisional anchors for calibration: `max_witness_bytes_per_input` should be set high enough that legitimate complex multisig and Lightning channel constructions are unaffected and low enough that fragmented image-scale payloads are blocked within a single input. `max_witness_bytes_per_tx` should be set to a multiple of `max_witness_bytes_per_input` sufficient for high-input-count CoinJoin and batch transactions while still blocking cross-input fragmentation at payload scales that impose meaningful node burden. `max_witness_script_push_bytes` may equal `max_tapleaf_push_bytes` after calibration; it is listed separately because segwit v0 scripts have a 10,000-byte historical ceiling and legitimate P2WSH multisig paths may need a larger push-constant budget than a Tapleaf.
### Defined Witness Versions
Rules 1 and 3 apply to all witness versions not defined as of this BIP. Creation of such outputs is invalid under Rule 1. Spending them is invalid under Rule 3. Pre-activation UTXOs remain grandfathered. The defined versions are:
- Witness v0 with a 20-byte program (P2WPKH) or a 32-byte program (P2WSH), per BIP 141.
- Witness v1 with a 32-byte program (Taproot/P2TR), per BIP 341. The only defined Tapleaf version is 0xc0 (Tapscript), per BIP 342.
- Witness v1 with the 2-byte program 0x4e73 (P2A, per BIP 433), spent with an empty witness stack only.
### Witness item classification
Rules 2, 8, and 9 count only **script-argument** witness items:
- **P2WPKH:** both items (signature, pubkey) are script-argument.
- **P2WSH:** every item except the last. The last item is the witness script (Rules 12–13).
- **P2TR key-path:** the signature item is excluded. BIP 341 already makes extra items invalid.
- **P2TR script-path:** every item except the last two (Tapleaf script, control block). An annex is invalid under Rule 4.
- **P2A:** empty witness only.
Byte counts are `len(item)` for each counted item, summed as 64-bit integers.
### Activation
This BIP deploys via BIP-8 or BIP-9 style signaling with a minimum activation window of one year and no mandatory lock-in fallback. The threshold and signaling parameters are set at deployment. Miners who do not signal are not penalized. If signaling does not reach threshold within the window, the process restarts with revised parameters or renewed community discussion.
BIP-8/9 without lock-in-on-timeout is miner signaling. Node operators absorbing non-monetary burden are a political constituency for this rule; they are not the signaling threshold. If miners do not signal, this BIP does not activate under the specified mechanism. User-activated soft fork deployment is a separate choice and is not specified here.
---
## Rationale
### Why Permanent Rather Than Temporary
The case is in [Why Permanent Rules Are the Right Mechanism](#why-permanent-rules-are-the-right-mechanism). The cost on node operators is not temporary, so the rules have no expiry.
### Why Per-Item Caps Alone Are Insufficient
A 256-byte cap per individual witness item is the correct tool for closing single-field contiguous data embedding. It does not close fragmentation because it imposes no constraint on the number of items or on their aggregate size. Rules 8 and 9 are the missing constraint. They place a ceiling on total witness data per input and per transaction that makes large-payload fragmentation invalid regardless of how finely the payload is divided. A 50 kilobyte image split into 256-byte chunks requires roughly 200 chunks. With appropriate aggregate limits, that transaction or that input is invalid. With cross-transaction fragmentation, the aggregate limit per transaction is reached before the payload fits, so the payload requires more transactions, each paying the per-output fee, making the total cost of data embedding proportional to data volume. That is the correct pricing signal.
### Why the Aggregate Limits Are Scoped to Script-Argument Witness Items
Witness scripts and Tapleaf scripts are excluded from the aggregate counts because they are scripts, not data. Their size is governed by legitimate cryptographic and contract requirements. Taproot key-path signatures are fixed-length by consensus. Control blocks encode the Merkle path to a Tapscript and are governed by Rule 5. Annexes are invalidated by Rule 4. The aggregate limits target the data surface, not the script surface, consistent with this BIP's purpose.
### Why OP_RETURN Is Capped at 83 Bytes
OP_RETURN outputs are provably unspendable and do not enter the UTXO set. Historically, up to 83 bytes of `scriptPubKey` have been tolerated to avoid unprovably unspendable spam in other output scripts. This BIP restores that cap at consensus. It does not replace the per-output fee: `OP_RETURN` still pays *[Static Per-Output Miner Fee](/bips/static-per-output-miner-fee)* when that BIP is active. At a correctly calibrated per-output fee, the cost per OP_RETURN output is negligible for legitimate low-volume use and material only for high-volume data embedding. The 83-byte figure is total script length, matching historical `-datacarriersize`, not 83 bytes of payload after `OP_RETURN`. Capping OP_RETURN at consensus restores a principle that Core relay policy previously enforced but that miners could bypass.
### Why OP_IF and OP_NOTIF Are Invalidated in Tapscript
With Taproot, branching conditions can be evaluated off-chain, revealing only the intended execution path. OP_IF is redundant in Tapscript for well-designed monetary constructions and has been commonly used to inject data that is skipped at execution. Closing this gap eliminates a common embedding abuse. Current Lightning is mostly P2WSH and is not affected. Taproot Miniscript and taproot-channel HTLC leaves that still use OP_IF must split those branches into separate leaves before activation.
### Why Undefined Witness Versions Are Closed to Creation and Spending
Undefined witness versions have unlimited witness stack sizes, creating an unconstrained embedding surface. Rule 3 closes spending. Rule 1 already closes creation: an undefined-version scriptPubKey is not a defined template. Leaving creation valid would park a new class of hash-channel UTXOs and is not required for upgrades.
A future witness version is added the same way P2TR was added: one soft fork that both whitelists the output template and defines spending rules. Senders do not need a pre-creation window. Pre-activation UTXOs, including any rare undefined-version outputs that already exist, remain spendable under grandfathering.
### Why BIP141 Weight Is Unchanged
This BIP does not reprice witness bytes. After Rules 2, 7, and 10 through 13, bulk JPEG payload is invalid, so the BIP141 discount no longer subsidizes dedicated embedding. Remaining witness bytes are signatures, scripts, and control blocks.
Repricing all witness data is a different proposal and would mix a Lightning and batching design fight into this activation. It is not required for channel closure. A later BIP could, if desired, apply full weight to script-argument witness items only (the Rule 2 set) without touching signature or script weight. That change is out of scope here.
### Why Bare Multisig Is Closed at the Output Template Layer
Bare multisig scriptPubKeys encode public keys directly in the output script. The Stamps protocol exploits this by substituting arbitrary data for valid public key bytes. Because the output script is stored permanently in the UTXO set until spent, this creates indefinite node storage burden with no monetary justification. A length cap on scriptPubKeys does not cleanly close this channel because a three-of-three bare multisig output can be constructed within plausible byte limits while still carrying meaningful data payloads in its fake keys. The output template whitelist in Rule 1 closes the channel completely: bare multisig is not a defined template and is invalid at output creation, before any data reaches the UTXO set. Legitimate monetary use cases that historically relied on bare multisig are fully served by P2SH, P2WSH, and P2TR, all of which are on the whitelist.
### Why Tapleaf Scripts Are Analyzed for Unreferenced Push Data
The exclusion of Tapleaf scripts from per-item witness caps in Rule 2 is correct for legitimate contract logic: push constants in a Tapleaf script serve as inputs to opcodes that consume them. The Taproot envelope embedding technique abuses this exemption by placing arbitrary data as push constants that no live path executes: typically `OP_FALSE OP_IF OP_ENDIF`. These dead pushes are present in the witness at spend time, visible to every node, and stored indefinitely. Rule 10 invalidates a script-body push that no live path reads. `OP_2 OP_3 OP_CHECKMULTISIG` stays valid because every push is read, not because consecutive pushes are a class exemption. Rule 11 caps consume-and-ignore patterns such as `OP_PUSH` followed by `OP_DROP` that Rule 10 treats as referenced when they sit on a live path.
### Why P2WSH Witness Scripts Get the Same Treatment
Rules 2, 8, and 9 correctly exclude witness scripts from per-item and aggregate witness-item caps: those scripts are program bodies, not data fields. Segwit v0 witness scripts can still be up to 10,000 bytes. Dead pushes inside a P2WSH script are therefore a remaining dedicated channel if only Tapleaf bodies are analyzed.
Rules 12 and 13 close that channel. Rule 12 applies the Rule 10 unreferenced-push analysis to the last witness stack item on a P2WSH spend. Rule 13 applies the Rule 11 aggregate push-constant cap via `max_witness_script_push_bytes`. BIP16 redeemScripts are not given this treatment: P2SH script-path dumps remain a leftover by scope, not a recommended embedding path. RedeemScript pushes remain excepted from the 256-byte item cap in Rule 2. P2SH is not the high-bandwidth inscription channel; P2WSH was. A later BIP could close P2SH without changing this one.
### Interaction With the Per-Output Fee BIPs
This BIP and the static fee BIP have no consensus dependency on each other. Dynamic escalation requires the static fee BIP. The combined effect is in [The Interaction With the Per-Output Fee BIPs](#the-interaction-with-the-per-output-fee-bips).
---
## Backwards Compatibility
Existing coins are never frozen. A pre-activation UTXO can be spent under pre-activation spend rules, including one inscription reveal if that coin already committed an envelope. That spend does not create a new grandfathered inscription UTXO. New outputs created at or after `activation_height` must match Rule 1 even when funded entirely by pre-activation inputs, and their later spends are fully bound by Rules 2 through 13. Coinbase outputs created at or after activation must also be a defined template or a valid 83-byte OP_RETURN. Coinbase `scriptSig` is unchanged.
Some wallet software, including certain Miniscript compilers, habitually creates Tapleaves containing OP_IF and may place required scripts deeper than 7 Taptree levels. Lightning taproot-channel designs that keep OP_IF in a Tapscript HTLC leaf must split those branches. Current P2WSH Lightning funding scripts are unaffected by Rule 7. BOLT 3 `to_local`, `to_remote` with CSV, the anchor script, the 2-of-2 funding script, and the offered and received HTLCs pass the live-path walk and the branch-end rule: `to_local`'s pubkeys sit in front of `OP_ELSE` and `OP_ENDIF`, and `OP_CHECKSIG` consumes the one that branch executes. Regtest Core v28.1 accepted the 2-of-2 close, the offered-HTLC preimage spend, and the delay-1 `to_local` CSV spend. The mitigations for Taproot Miniscript are: split OP_IF branches into separate Tapleaves and keep every required script-path leaf at depth 7 or less. Taproot control blocks are capped at 257 bytes, limiting Taptrees to 128 script leaves, which is sufficient for modern complex transactions but may constrain advanced off-chain contract schemes that rely on very large script trees.
Rules 8 and 9 require wallets and transaction construction libraries to track aggregate witness byte consumption per input and per transaction. Rules 12 and 13 require P2WSH constructors to avoid unreferenced pushes and to stay within `max_witness_script_push_bytes`. The calibration checklist must confirm that no legitimate high-witness-count use case (Lightning channel opens, complex multisig, CoinJoin, large P2WSH) is invalidated at correctly calibrated parameter values.
Wallets that do not update will produce transactions that enforcing nodes reject at and after `activation_height`. The minimum one-year signaling window provides time for updates. As with the per-output fee BIPs, updates should be complete before activation.
---
## Reference Implementation
High-level pseudocode:
```python
ACTIVATION_HEIGHT =
MAX_WITNESS_BYTES_PER_INPUT =
MAX_WITNESS_BYTES_PER_TX =
def script_argument_witness_items(input_witness):
# Exclude: witness scripts, Tapleaf scripts, control blocks,
# annexes, and Taproot key-path signatures.
# Return the remaining witness stack elements.
...
def is_valid_transaction(tx, block_height):
if block_height < ACTIVATION_HEIGHT:
return True
# Rule 1: every new output, including coinbase outputs
for out in tx.outputs:
if not is_allowed_scriptpubkey(out.scriptPubKey):
return False
if tx.is_coinbase:
return True
tx_aggregate = 0
for inp in tx.inputs:
if inp.utxo_height < ACTIVATION_HEIGHT:
continue # spend rules only; Rule 1 already applied to outputs
items = script_argument_witness_items(inp.witness)
# Rule 2: per-item cap
for item in items:
if len(item) > 256:
return False
# Rule 9: per-input aggregate cap
input_aggregate = sum(len(item) for item in items)
if input_aggregate > MAX_WITNESS_BYTES_PER_INPUT:
return False
tx_aggregate += input_aggregate
# Rule 8: per-transaction aggregate cap (post-activation inputs only)
if tx_aggregate > MAX_WITNESS_BYTES_PER_TX:
return False
# Rules 3–7, 10–13: omitted here for brevity; see Specification
...
return True
```
Detailed test vectors, integer arithmetic requirements, precise witness item classification, and edge cases will be provided in a future numbered BIP submission.
---
## Calibration Checklist
### A. Aggregate Limit Determination (Hard Gate)
- Establish the maximum script-argument witness byte count per input required by legitimate high-witness-count constructions: Lightning channel opens, complex multisig (5-of-7 and above), CoinJoin inputs at realistic participant counts, and Taproot script-path spends with deep trees up to the 128-leaf limit imposed by Rule 5.
- Set `max_witness_bytes_per_input` above the 99th percentile of legitimate per-input witness consumption observed across full chain history.
- Confirm that an image-scale fragmented payload (50 kilobytes, split into 256-byte chunks) requires per-input or per-transaction witness aggregates that exceed the calibrated limits and is therefore invalid.
- Set `max_witness_bytes_per_tx` to accommodate high-input-count CoinJoin transactions at realistic participant counts while blocking cross-input fragmentation at image scale.
- Lock in both values or document required adjustments with full reasoning before the proposal moves forward.
- Set `max_tapleaf_push_bytes` and `max_witness_script_push_bytes` above legitimate Miniscript, Lightning, and P2WSH multisig push-constant totals and below image-scale script-body dumps. Confirm Rule 11 and Rule 13 catch consume-and-ignore patterns that Rule 10 and Rule 12 treat as referenced.
### B. Collateral Damage (Must Pass)
- Lightning channel opens: confirm per-input and per-transaction aggregate witness bytes remain below limits at all relevant funding configurations.
- CoinJoin transactions at 50, 100, and 200 participants: confirm aggregate limits are not reached.
- Complex multisig up to 5-of-7 and above: confirm script-path spend witness aggregates remain within limits.
- Taproot script-path spends at maximum allowed tree depth (128 leaves, Rule 5): confirm aggregate limits not reached.
- Ordinary payments (P2WPKH, P2TR keypath): confirm negligible witness aggregates relative to limits.
- P2WSH multisig spends: confirm Rule 12 and Rule 13 do not invalidate legitimate witness scripts at calibrated `max_witness_script_push_bytes`.
### C. Spam Efficacy
- Confirm that image-scale payloads (at 50 kilobytes and above) cannot be embedded in a single transaction without exceeding Rule 8 or Rule 9 limits, and cannot be embedded in a P2WSH witness script or Tapleaf body without exceeding Rule 11 or Rule 13.
- Confirm that cross-transaction fragmentation at image scale, priced through the per-output fee BIPs, produces a per-byte cost that makes sustained spam economically irrational at calibrated fee levels.
- Model the combined cost of the three-BIP stack (per-output fee plus aggregate witness limits) against realistic attacker budgets for inscription-wave-scale activity.
### D. Consensus Edge Cases
- Confirm the witness item classification in Specification (P2WPKH, P2WSH, P2TR key-path, P2TR script-path, P2A).
- Confirm integer arithmetic for aggregate byte counting so all implementations agree bit-for-bit.
- Confirm grandfathering: Rule 1 on every output created at or after `activation_height`; Rules 2–13 only on inputs whose prevout was created at or after that height.
- Confirm reorg behavior at `activation_height`: blocks below the activation height are never subject to any rule in this BIP regardless of reorg depth.
- Confirm that the witness item classification algorithm is reproducible from block data alone without mempool history.
- Confirm implementations match the Appendix A grids bit-for-bit for both `WITNESS_V0` and `TAPSCRIPT`.
- Confirm Rule 12 accepts standard P2WSH `OP_2 OP_2 OP_CHECKMULTISIG` and BOLT 3 `to_local`, `to_remote` with CSV, the anchor script, and offered and received HTLCs. `to_local`'s pubkeys are followed by `OP_ELSE` and `OP_ENDIF`. The branch-end exception in Unreferenced push analysis accepts them because `OP_CHECKSIG` consumes the executed key. Rule 7 does not apply to these P2WSH scripts. Regtest Core v28.1 accepted the 2-of-2 close, the offered-HTLC preimage spend, and the delay-1 `to_local` CSV spend.
### E. Wallet and Exchange Validation
- Share calibration results with at least one Lightning implementation developer, one exchange wallet engineer, and one CoinJoin implementation developer before proceeding.
- Confirm that fee estimation and transaction construction tooling can enforce aggregate witness limits internally before broadcasting.
### F. Exit Criteria
- Both aggregate limit values confirmed and gate A passes.
- Collateral damage checklist B passes at calibrated values.
- Spam efficacy checklist C confirms image-scale payloads are blocked or prohibitively expensive under the three-BIP stack.
- Consensus edge cases in checklist D resolved and written into Specification.
---
## Appendix A. `stack_items_read`
Normative. Every opcode byte has an assigned integer. Implementations MUST NOT treat any byte as unspecified.
Source of the counts: Bitcoin Core `EvalScript` in `src/script/interpreter.cpp` and `IsOpSuccess` in `src/script/script.cpp` as of commit [`b2c45888`](https://github.com/bitcoin/bitcoin/commit/b2c45888fde06429e86913fab5e7b7a075f091c3) (2026-08-12). A later Core change that alters stack effects of an existing opcode requires a new consensus discussion; it does not silently amend this appendix.
### Definition
`stack_items_read(opcode, kind) -> integer >= 0`
`kind` is `WITNESS_V0` (Rule 12) or `TAPSCRIPT` (Rule 10).
The return value is how many main-stack items, counted from the top, the opcode requires at its first `stack.size()` check. `OP_PICK`, `OP_ROLL`, `OP_CHECKMULTISIG`, and `OP_CHECKMULTISIGVERIFY` then follow the tails below. Those tails are part of this appendix.
`OP_PICK` and `OP_ROLL` (`EvalScript`, the `stack.size() < 2` check, then `n`):
- If the stack has fewer than 2 items, the opcode fails.
- Pop `n` as a `CScriptNum`. If `n < 0` or `n >= stack.size()`, the opcode fails.
- Read the item `n` down from the new top (`stacktop(-n-1)`). `OP_ROLL` erases that item. Both opcodes push it.
`OP_CHECKMULTISIG` and `OP_CHECKMULTISIGVERIFY` in `WITNESS_V0`:
- If the stack is empty, the opcode fails. Pop `nKeys`. If `nKeys` is outside `0..20`, the opcode fails.
- Pop `nKeys` keys. Pop `nSigs`. If `nSigs` is outside `0..nKeys`, the opcode fails.
- Pop `nSigs` signatures, then one dummy. The dummy is the historical extra argument. Under `NULLDUMMY` it must be empty; that flag is existing consensus, not a new rule.
- The number of pops is `3 + nKeys + nSigs`. That is the interpreter's final index `i`, and the cleanup pops `i` items.
- `OP_CHECKMULTISIG` pushes the result. `OP_CHECKMULTISIGVERIFY` pops that result on success and fails on false.
Tapscript fails both multisig opcodes before any pop (Appendix A step 2). The grid value there is 0.
When `n`, `nKeys`, or `nSigs` is not a script constant, or the selected `OP_PICK` / `OP_ROLL` slot lies under the script stack (a witness item), the path walk does not guess which script push was read.
Diff against `EvalScript` at the commit above, every opcode byte. The grids match the assignment steps, including `OP_PICK` and `OP_ROLL` at 2. Unexecuted `OP_IF` / `OP_NOTIF` pop only when `fExec` is set; the integer is 1 on purpose. Disabled v0 opcodes return 0 before the switch. `OP_CHECKSIGADD` is 3 in tapscript and 0 in v0. No opcode's stack behavior is left unmodeled.
Unexecuted `OP_IF` / `OP_NOTIF` do not pop in `EvalScript`. This analysis is static and does not track `vfExec`. Both opcodes are `1` in both kinds. Tapscript still invalidates them under Rule 7.
`OP_CHECKLOCKTIMEVERIFY` and `OP_CHECKSEQUENCEVERIFY` inspect the top item and leave it in place. They are `1`. This BIP assumes the consensus flags that activate those opcodes; it does not model the historical NOP2/NOP3 fallback.
### Assignment (apply in order)
1. If `kind == TAPSCRIPT` and `IsOpSuccess(opcode)` (BIP 342): return `0`. The SUCCESS bytes are `0x50`, `0x62`, `0x7e`–`0x81`, `0x83`–`0x86`, `0x89`–`0x8a`, `0x8d`–`0x8e`, `0x95`–`0x99`, and `0xbb`–`0xfe`.
2. If `kind == TAPSCRIPT` and opcode is `OP_CHECKMULTISIG` (`0xae`) or `OP_CHECKMULTISIGVERIFY` (`0xaf`): return `0` (Core fails with `SCRIPT_ERR_TAPSCRIPT_CHECKMULTISIG` before popping).
3. If opcode is `OP_CHECKSIGADD` (`0xba`): return `3` if `kind == TAPSCRIPT`, else `0` (`SCRIPT_ERR_BAD_OPCODE` in v0).
4. If `kind == WITNESS_V0` and opcode is a disabled splice/bitwise/numeric opcode (`OP_CAT`, `OP_SUBSTR`, `OP_LEFT`, `OP_RIGHT`, `OP_INVERT`, `OP_AND`, `OP_OR`, `OP_XOR`, `OP_2MUL`, `OP_2DIV`, `OP_MUL`, `OP_DIV`, `OP_MOD`, `OP_LSHIFT`, `OP_RSHIFT`): return `0` (fail before the `EvalScript` switch).
5. If opcode is a push (`0x00`–`0x4e`, `OP_1NEGATE`, `OP_1`–`OP_16`): return `0`.
6. Otherwise use the named table below. Bytes with no named row, including `OP_RESERVED`, `OP_VER`, `OP_VERIF`, `OP_VERNOTIF`, `OP_NOP1`/`OP_NOP4`–`OP_NOP10`, and `0xff`, return `0`.
### Opcode atlas
The live map is the 256-byte `stack_items_read` table: row `R`, column `F` is byte `0xRF`. Copy-out tables are under the atlas.
```opcode-atlas
```
### Named opcodes (`stack_items_read >= 1`, plus zeros that are easy to get wrong)
Values below are for `WITNESS_V0`. Tapscript differs only on `0xae`, `0xaf`, and `0xba` (steps 1–3).
| Byte | Name | V0 | Notes |
|---|---|---|---|
| `0x63` | `OP_IF` | 1 | Pops when executed; static analysis uses 1 |
| `0x64` | `OP_NOTIF` | 1 | Same |
| `0x69` | `OP_VERIFY` | 1 | |
| `0x6a` | `OP_RETURN` | 0 | Fails without reading the stack |
| `0x6b` | `OP_TOALTSTACK` | 1 | |
| `0x6c` | `OP_FROMALTSTACK` | 0 | Reads altstack only |
| `0x6d` | `OP_2DROP` | 2 | |
| `0x6e` | `OP_2DUP` | 2 | |
| `0x6f` | `OP_3DUP` | 3 | |
| `0x70` | `OP_2OVER` | 4 | |
| `0x71` | `OP_2ROT` | 6 | |
| `0x72` | `OP_2SWAP` | 4 | |
| `0x73` | `OP_IFDUP` | 1 | |
| `0x74` | `OP_DEPTH` | 0 | Reads stack *size*, not an item |
| `0x75` | `OP_DROP` | 1 | |
| `0x76` | `OP_DUP` | 1 | |
| `0x77` | `OP_NIP` | 2 | Erases second-to-top; top still required |
| `0x78` | `OP_OVER` | 2 | |
| `0x79` | `OP_PICK` | 2 | First check `stack.size() < 2`. Then pop `n` and read the slot `n` down |
| `0x7a` | `OP_ROLL` | 2 | Same as `OP_PICK`, and the read item is removed |
| `0x7b` | `OP_ROT` | 3 | |
| `0x7c` | `OP_SWAP` | 2 | |
| `0x7d` | `OP_TUCK` | 2 | Not a SUCCESS byte |
| `0x82` | `OP_SIZE` | 1 | Inspects top; does not pop |
| `0x87` | `OP_EQUAL` | 2 | |
| `0x88` | `OP_EQUALVERIFY` | 2 | |
| `0x8b` | `OP_1ADD` | 1 | |
| `0x8c` | `OP_1SUB` | 1 | |
| `0x8f` | `OP_NEGATE` | 1 | |
| `0x90` | `OP_ABS` | 1 | |
| `0x91` | `OP_NOT` | 1 | |
| `0x92` | `OP_0NOTEQUAL` | 1 | |
| `0x93` | `OP_ADD` | 2 | |
| `0x94` | `OP_SUB` | 2 | |
| `0x9a` | `OP_BOOLAND` | 2 | |
| `0x9b` | `OP_BOOLOR` | 2 | |
| `0x9c` | `OP_NUMEQUAL` | 2 | |
| `0x9d` | `OP_NUMEQUALVERIFY` | 2 | |
| `0x9e` | `OP_NUMNOTEQUAL` | 2 | |
| `0x9f` | `OP_LESSTHAN` | 2 | |
| `0xa0` | `OP_GREATERTHAN` | 2 | |
| `0xa1` | `OP_LESSTHANOREQUAL` | 2 | |
| `0xa2` | `OP_GREATERTHANOREQUAL` | 2 | |
| `0xa3` | `OP_MIN` | 2 | |
| `0xa4` | `OP_MAX` | 2 | |
| `0xa5` | `OP_WITHIN` | 3 | |
| `0xa6` | `OP_RIPEMD160` | 1 | |
| `0xa7` | `OP_SHA1` | 1 | |
| `0xa8` | `OP_SHA256` | 1 | |
| `0xa9` | `OP_HASH160` | 1 | |
| `0xaa` | `OP_HASH256` | 1 | |
| `0xab` | `OP_CODESEPARATOR` | 0 | |
| `0xac` | `OP_CHECKSIG` | 2 | |
| `0xad` | `OP_CHECKSIGVERIFY` | 2 | |
| `0xae` | `OP_CHECKMULTISIG` | 1 | First check is one item (`nKeys`). Tail pops `3 + nKeys + nSigs`. Tapscript: 0 |
| `0xaf` | `OP_CHECKMULTISIGVERIFY` | 1 | Same tail. Tapscript: 0 |
| `0xb1` | `OP_CHECKLOCKTIMEVERIFY` | 1 | Inspects top; does not pop |
| `0xb2` | `OP_CHECKSEQUENCEVERIFY` | 1 | Same |
| `0xba` | `OP_CHECKSIGADD` | 0 | Tapscript: 3 |
Worked cases: `OP_FALSE OP_IF OP_ENDIF` is unreferenced (dead arm), including ` OP_DROP` inside that arm. ` OP_DROP` on a live path is referenced (Rules 11 and 13). ` OP_NOP` is unreferenced. `OP_2 OP_2 OP_CHECKMULTISIG` is referenced: the walk pops both keys, both signatures, and the dummy (`3 + 2 + 2 = 7`). BOLT 3 `to_local` is referenced: each branch's pubkey is followed by `OP_ELSE` or `OP_ENDIF`, and `OP_CHECKSIG` consumes that pubkey. A pubkey before `OP_ELSE` with no signature check is unreferenced.
### Complete grids (byte `0xRF` at row `R`, column `F`)
**`WITNESS_V0` (Rule 12)**
| | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | A | B | C | D | E | F |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| `0_` | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| `1_` | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| `2_` | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| `3_` | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| `4_` | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| `5_` | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| `6_` | 0 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | 2 | 2 | 3 |
| `7_` | 4 | 6 | 4 | 1 | 0 | 1 | 1 | 2 | 2 | 2 | 2 | 3 | 2 | 2 | 0 | 0 |
| `8_` | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 2 | 2 | 0 | 0 | 1 | 1 | 0 | 0 | 1 |
| `9_` | 1 | 1 | 1 | 2 | 2 | 0 | 0 | 0 | 0 | 0 | 2 | 2 | 2 | 2 | 2 | 2 |
| `A_` | 2 | 2 | 2 | 2 | 2 | 3 | 1 | 1 | 1 | 1 | 1 | 0 | 2 | 2 | 1 | 1 |
| `B_` | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| `C_` | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| `D_` | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| `E_` | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| `F_` | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
**`TAPSCRIPT` (Rule 10)**
Same as V0 except `0xae` = 0, `0xaf` = 0, `0xba` = 3. SUCCESS bytes are already 0 in both grids.
| | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | A | B | C | D | E | F |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| `0_` | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| `1_` | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| `2_` | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| `3_` | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| `4_` | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| `5_` | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| `6_` | 0 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | 2 | 2 | 3 |
| `7_` | 4 | 6 | 4 | 1 | 0 | 1 | 1 | 2 | 2 | 2 | 2 | 3 | 2 | 2 | 0 | 0 |
| `8_` | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 2 | 2 | 0 | 0 | 1 | 1 | 0 | 0 | 1 |
| `9_` | 1 | 1 | 1 | 2 | 2 | 0 | 0 | 0 | 0 | 0 | 2 | 2 | 2 | 2 | 2 | 2 |
| `A_` | 2 | 2 | 2 | 2 | 2 | 3 | 1 | 1 | 1 | 1 | 1 | 0 | 2 | 2 | 0 | 0 |
| `B_` | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 3 | 0 | 0 | 0 | 0 | 0 |
| `C_` | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| `D_` | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| `E_` | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| `F_` | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
---
## Security Considerations
**No expiry surface.** Because this BIP is permanent, there is no expiry date for the data-embedding ecosystem to plan around. The rule is stable indefinitely.
**Grandfathering boundary.** Rule 1 uses the creating block's height. Rules 2 through 13 use the prevout's creating height. A mixed transaction is not a blanket exemption. Implementations must not treat “any grandfathered input” as exempting new outputs, and must not treat a grandfathered spend as authorizing inscription witness on later spends of the new outputs. A pre-activation envelope UTXO may still reveal its committed witness once, when that coin is spent. New envelopes cannot be created: a post-activation P2TR funded from old coins is a new prevout, and Rules 2 through 13 reject inscription-style witness when it is spent.
**Undefined-version creation.** Rule 1 and Rule 3 must agree: undefined witness-version outputs cannot be created after activation and cannot be spent except via grandfathered pre-activation UTXOs. Implementations that allow creation while rejecting spends, or the reverse, will split the chain.
**Aggregate limit manipulation.** An attacker who knows the `max_witness_bytes_per_tx` limit could construct transactions that stay just below it across many transactions, accumulating a fragmented payload. The per-output fee BIPs price each such transaction through its output count, so aggregate data embedding volume remains proportional to aggregate fee spend. This is the intended outcome. Fragmentation across many transactions in one block remains possible up to the weight limit. A per-block data cap is rejected: it collides with high-throughput monetary blocks (batch payouts, many channel closes, several CoinJoins). That path is priced by the per-output fee, not by a fourth aggregate.
**Witness item classification.** The exclusion of witness scripts, Tapleaf scripts, control blocks, annexes, and key-path signatures from the aggregate counts must be specified precisely and implemented identically across all compliant implementations. Classification errors that treat script material as data (or vice versa) produce consensus failures. Witness scripts and Tapleaf scripts are instead governed by Rules 10 through 13. The calibration checklist requires a shared witness item classification algorithm before submission.
**Private mempool arrangements.** Miners accepting non-compliant transactions through private arrangements produce blocks that enforcing nodes reject. Orphan risk limits sustained defection, as with the per-output fee BIPs.
---
## Revision history
- 2026-10-27. Rules 10 and 12 use a live-path walk. A key or key-hash immediately before `OP_ELSE` or `OP_ENDIF` is referenced when a signature check on that branch consumes it. BOLT 3 `to_local` passes. Rule 7 remains a Tapscript `OP_IF` / `OP_NOTIF` ban.
- 2026-10-27. `OP_PICK` and `OP_ROLL` are 2. `OP_CHECKMULTISIG` and `OP_CHECKMULTISIGVERIFY` stay 1 in v0 and 0 in tapscript. The v0 tail pops `3 + nKeys + nSigs` items. An earlier note that those grids were unchanged is withdrawn.
---
## References
- *[BIP Pre-Proposal: Static Per-Output Miner Fee](/bips/static-per-output-miner-fee)* (Josh / Secure Sovereign, July 2026).
- *[BIP Pre-Proposal: Dynamic Escalation of the Per-Output Miner Fee](/bips/dynamic-escalation-per-output-fee)* (Josh / Secure Sovereign, July 2026).
- BIP 141: Segregated Witness.
- BIP 341: Taproot.
- BIP 342: Tapscript (`IsOpSuccess` ranges).
- Bitcoin Core `src/script/interpreter.cpp` (`EvalScript`) and `src/script/script.cpp` (`IsOpSuccess`), commit [`b2c45888`](https://github.com/bitcoin/bitcoin/commit/b2c45888fde06429e86913fab5e7b7a075f091c3).
- BIP 433: Pay-to-Anchor (P2A).
- BIP 16: Pay to Script Hash.
- *[The Achievable Floor](/articles/the-achievable-floor)* (Josh / Secure Sovereign, 2026).
- *[Bitcoin Is Not a Hard Drive](/articles/bitcoin-not-a-hard-drive)* (Josh / Secure Sovereign, 2026).
- *[Full Cost of Running a Bitcoin Node](/articles/full-cost-of-running-a-bitcoin-node)*, v2.4 (Josh / Secure Sovereign, July 2026).
- Various Delving Bitcoin and bitcoin-dev threads on UTXO bloat and data embedding (2023–2026).
---
## Copyright
This document is licensed under the BSD 2-Clause License.
---
# Work Proposals
# Getting a Quantum Upgrade Adopted Is a Security Problem
*A research proposal to the Bitcoin Security Consortium. October 2026.*
## The gap
A quantum-resistant upgrade protects Bitcoin only after the network adopts it. No one can mandate that. Thousands of independent node operators have to run the new rules, miners and economic nodes have to enforce them, and holders have to move their coins. An upgrade that stalls protects nothing. One that activates under contested legitimacy adds chain-split risk on top of the quantum exposure it was meant to remove. Adoption failure is a security failure.
The design space is wide and still open. Candidate output types include P2MR ([BIP-360](https://github.com/bitcoin/bips/blob/master/bip-0360.mediawiki)), P2TRv2, P2TRH, and P2QR, compared side by side in the [PQC output type discussion](https://delvingbitcoin.org/t/pqc-output-type-discussion/2749) on Delving Bitcoin. Leading signature candidates are hash-based, including [SHRINCS](https://blog.blockstream.com/op_checkshrincs-a-hash-based-signature-opcode-for-post-quantum-bitcoin/) and [SHRIMPS](https://delvingbitcoin.org/t/shrimps-2-5-kb-post-quantum-signatures-across-multiple-stateful-devices/2355) from Blockstream researchers. For coins that never move, the options range from leaving legacy spends valid, to rate-limiting them, to [commit-then-reveal migration](https://delvingbitcoin.org/t/post-quantum-migrations-via-commit-then-reveal-ala-bip16-an-alternative-to-sunsetting/2467), to a sunset with a recovery path as in [BIP-361](https://github.com/bitcoin/bips/blob/master/bip-0361.mediawiki).
Several of the central disputes are adoption questions in technical form. P2TRv2 keeps today's fee profile and wallet behavior to win broad early adoption, and relies on a later consensus change to disable elliptic-curve spends. P2MR gives up some spend efficiency for protection that does not depend on that later change. Which tradeoff holds up depends on how quickly users adopt an output type under each design, and on whether a contested elliptic-curve disable could activate when it is needed.
Existing migration estimates bound how long migration would take given block space. They do not say how quickly holders will actually choose to move, which is the constraint most likely to bind. Estimates of exposed supply run from about ten thousand coins at near-term risk to roughly a third of all bitcoin, depending on the exposure model, and much of the exposed value sits with a small number of large custodians. This proposal measures the behavioral side with data.
## What I propose
A research report that analyzes the network conditions a quantum migration depends on and maps the realistic paths to adoption, with the failure modes of each. The report would serve as input to the consortium's published material on Bitcoin's security. It would cover four areas.
1. **Activation precedent.** The SegWit and Taproot histories from proposal to activation, including the activation-method disputes (BIP 148 and BIP 91 in 2017, the LOT=true versus LOT=false debate and Speedy Trial in 2021). The output is what each episode shows about timelines, about where consensus held and where it nearly broke, and what that history implies for a follow-up change, such as an elliptic-curve disable, that may face organized opposition.
2. **Behavioral migration rates from chain data.** Existing work, including the [Chaincode Labs post-quantum report](https://chaincode.com/bitcoin-post-quantum.pdf), [Presidio Bitcoin's readiness report](https://github.com/presidiobtc/bitcoin-quantum/), and ongoing Delving Bitcoin and bitcoin-dev discussions on migration incentives, bounds migration time by block space. This section measures holder behavior. It tracks how quickly value moved to each new output type after activation (P2SH, SegWit, Taproot), separates custodial and exchange flows from individual holders where chain heuristics allow, and tests how fee profile and wallet support shaped each curve. The result is a set of realistic adoption curves to set against each candidate design, and a bound on how much supply any legacy-coin policy would actually catch.
3. **Process conditions.** A quantitative picture of how consensus changes move through review and merge, drawn from an existing dataset covering Bitcoin Core development from 2010 to 2026 across GitHub, the development mailing list, and IRC. This section establishes what the development pipeline can realistically carry, and on what timeline.
4. **Design and failure-mode map.** For the leading designs, and the combinations of output type, signature scheme, and legacy-coin policy their authors propose, the report sets out what has to be true for adoption, which follow-up consensus changes the design depends on, where the path can split the network, and which observable signals would show it is on or off track. The framework takes new proposals as they appear, so the map stays current as the design space moves.
The report will not recommend a specific proposal or activation method. It describes conditions and risks so that developers, node operators, and holders can make that call with better information. This keeps the work consistent with the consortium's position of not advocating code changes.
## Optional workstream
A migration rule is easier to review when it is stated precisely and tested on more than one codebase before activation. I wrote a formal mathematical specification of Bitcoin's consensus rules (the Orange Paper) and maintain an independent Rust node built from it. As an optional extension, I can express a candidate output type or opcode, such as P2MR or a SHRINCS verification opcode, in the specification, implement it in the independent node, and differential-test it against the proposal's reference implementation. Disagreements between two independent implementations of the same rule text surface ambiguities before any activation discussion.
## What already exists
- **Governance dataset.** Bitcoin Core development from 2010 to 2026, drawn from GitHub pull requests, reviews, and comments, the development mailing list, and IRC. [github.com/secsovereign/bitcoin-governance-research](https://github.com/secsovereign/bitcoin-governance-research)
- **Orange Paper.** A formal specification of Bitcoin consensus, with consensus functions checked against it using Z3. [thebitcoincommons.org/spec.html](https://thebitcoincommons.org/spec.html)
- **Independent node.** Built from that specification, with extensive differential tooling against Bitcoin Core in its bench tool, blvm-bench. [github.com/BTCDecoded](https://github.com/BTCDecoded)
## Collaboration
I will coordinate with other prominent researchers in this space, including the authors of the leading proposals, to review the technical sections.
## Disclosure
I build an independent Bitcoin implementation, I have written critically about Bitcoin Core's governance model, and I have argued publicly that implementation diversity strengthens the network. A report on adoption conditions touches those questions. I am stating the interest up front so the method can be judged on its own terms. Every finding will rest on public data, and the dataset and analysis code will be published with the report.
## Deliverables and timeline
- **Report.** Final report with published data and analysis code, delivered 16 weeks from start. An interim draft goes to the funder at week 8 for factual review. Conclusions remain mine.
- **Optional workstream.** Six additional weeks.
---