Critics sometimes say “they can just change Bitcoin.” Understanding how Bitcoin governance actually works shows why meaningful changes require extraordinary consensus, and why that is a feature, not a bug.
Anyone can propose changes to Bitcoin via a BIP (Bitcoin Improvement Proposal). Soft forks are backward-compatible tightenings of the rules; hard forks are incompatible changes that create chain splits. Meaningful upgrades require near-universal consensus among developers, miners, node operators, exchanges, and wallets, because any significant non-upgrading subgroup simply stays on the old chain. The blocksize war of 2015–2017 proved this empirically: the side that lost the consensus debate forked off as Bitcoin Cash and became irrelevant. Nobody has changed the 21 million cap because doing so would require convincing essentially every participant. They won't.
Anyone can write a BIP, a formal technical proposal for a change to Bitcoin, and submit it to the public BIP repository[1]. BIPs are numbered sequentially, stored as plain text in a public Git repository, and debated openly on mailing lists, developer forums, and IRC.
There is no gatekeeper. There is no vote. A BIP becomes real only if it gains broad enough support among the people who actually run Bitcoin, developers writing reference implementations, miners choosing which software to run, node operators who validate rules, exchanges and wallet providers who interact with users. Without all of them, a proposal remains a document.
A backward-compatible change. The rules get tighter. Old nodes continue to accept new blocks because the new blocks also satisfy the old rules. Examples:
A backward-incompatible change. Old nodes reject the new blocks because the new blocks violate the old rules. The chain splits permanently. The non-upgrading side continues as a separate coin. Example:
Between 2015 and 2017, Bitcoin had its most contentious governance debate. The core question was how to scale transactions as adoption grew. Two camps:
The small-block faction won decisively. On August 1, 2017, Bitcoin Cash forked off with 8MB blocks. BCH's market capitalization today is a tiny fraction of Bitcoin's[2].
What the war showed: you can fork Bitcoin's code, but you cannot take Bitcoin's network, hashrate, exchange liquidity, node count, and monetary premium with you. All of those stayed with the chain the majority of participants continued to run. The fork became a separate coin; Bitcoin continued being Bitcoin. The book-length account is Jonathan Bier's The Blocksize War (2021)[3].
For a change to take effect on the canonical Bitcoin chain, roughly every group of participants must cooperate:
Soft-fork activation typically requires 90–95% miner signaling. Miners who don't signal risk producing orphaned blocks.
Every full node validates rules. Nodes running the old software continue to enforce old rules. A minority of nodes can keep an alternative chain alive.
Exchanges choose which chain trades as "BTC." If the major exchanges back one side, that side takes the ticker and most of the liquidity.
A change that wallets do not adopt cannot be used in practice. Wallet developers are a functional veto.
If any significant portion of the network does not upgrade, the result is a chain split, not a change. This is why nobody has raised the 21 million cap. Not because it is technically impossible, a different chain certainly could, but because it would require convincing essentially every participant to accept it. They won't, because the 21 million cap is the single most valuable property Bitcoin offers.
Taproot activated November 14, 2021[4]. It took roughly four years of development, multiple BIPs (340, 341, 342), and signaling reaching >90% of mined blocks before activation. It passed without controversy because developers, miners, exchanges, and node operators all agreed on the merits. This is what the Bitcoin upgrade process looks like when it works.
Post-quantum signatures (various BIPs in discussion, including BIP-360 drafts) are the likely next major proposal, addressing a long-term but real threat from sufficiently large quantum computers. Development is active; activation is years away at minimum. The timeline shows that Bitcoin can adapt when a case is made, but only slowly, and only with broad consensus.
Bitcoin governance is deliberately slow and deliberately distributed. Any meaningful change requires buy-in from developers, miners, nodes, exchanges, and wallets, five different constituencies with different incentives. A proposal that cannot convince all of them does not become a Bitcoin change; it becomes a failed fork, and the failed fork does not carry the network effects with it. This is the feature. It is why Bitcoin's rules have held for 16 years and why they will likely hold for many more.
Last updated 2026-04-18 · Not financial advice. Governance processes evolve; BIPs are the canonical source of record.