What are Blockchain Forks?

Forks have appeared several times across this series already; introduced in our blockchain protocolBlockchain ProtocolA blockchain protocol is the set of rules and standards that govern how a blockchain network operates, validates transactions, and reaches consensus.Keep learning article as the mechanism by which blockchain networksBlockchain NetworkA blockchain network is a system of computers connected to each other that follow the same set of rules to record, share, and validate transactions.Keep learning handle rule changes, referenced in our BitcoinBitcoinBitcoin is a decentralized digital currency that enables secure peer-to-peer transactions without relying on a central authority.Keep learning article as the path through which SegWit and Taproot were activated, and mentioned in our EthereumEthereumEthereum is a decentralized blockchain platform that runs smart contracts and dApps, using its native cryptocurrency (ETH) for transactions and fees.Keep learning article in the context of The Merge. Like several concepts before it, the topic has earned a dedicated article: not because the basic definitions are particularly complex, but because forks are genuinely consequential events that touch nearly every layer of a blockchain network simultaneously; consensusBlockchain consensus mechanismsA consensus mechanism is a method for validating transactions and securing a blockchain without relying on a central authority.Keep learning, nodesBlockchain NodesA node is simply a computer that participates in a blockchain network. Each node stores a copy of the blockchain and helps verify transactions.Keep learning, economic incentives, governanceGovernanceGovernance in crypto is how decisions about a blockchain or protocol are made, often through token holders voting on changes and proposals.Keep learning, and community; and understanding them properly requires looking at all of those layersBlockchain LayersBlockchain layers are the different levels of a blockchain ecosystem, typically including Layer 1 (base network), Layer 2 (scaling), and Layer 3 (applications).Keep learning together.

What a Fork Actually Is

In software development generally, a fork simply means taking a copy of an existing codebase and developing it independently from the original. In a blockchain context, the term carries an additional, specific meaning: a change to the network's rules that causes, or has the potential to cause, different nodes on the same network to disagree about which blocks are valid.

This framing is the key to understanding why forks matter so much in the blockchain context specifically. On a centralized system; a bank's database, a company's software; updating the rules is a straightforward administrative act: the operator deploys a new version, and that's that. On a decentralizedDecentralizationDecentralization is the distribution of control and decision-making across a network instead of a single central authority.Keep learning network, with no central operator and thousands of independently operated nodes each enforcing the rules for themselves, changing those rules requires every node to independently choose to adopt the new version; and when they don't all do so simultaneously, or don't all agree to do so at all, the result is a network that briefly, or permanently, diverges.

Soft Forks: Tightening the Rules

A soft fork is a rule change that is backward-compatible with the existing protocol. More precisely, it makes the rules stricter; blocks valid under the new rules are a subset of blocks valid under the old rules, meaning that old nodes (running the pre-fork software) will still accept blocks produced under the new rules as valid, even if they don't understand or take advantage of the new features themselves.

This backward compatibility is what makes soft forks the less disruptive of the two categories. Old and new nodes can coexist on the same chain without splitting it; old nodes may not understand the full detail of what's in a new block, but they don't reject it outright, so the network remains unified throughout the transition. As long as a majority of the network's miningCrypto MiningCrypto mining is the process of using computing power to validate blockchain transactions and earn cryptocurrency rewards.Keep learning or validation power has adopted the new rules, the new rules will be enforced in practice, because the majority produces the longest chain (in Proof of WorkProof of WorkProof of Work (PoW) is a consensus mechanism where miners use computing power to validate transactions and secure the blockchain.Keep learning terms, as established in our consensus mechanisms article) that all nodes follow.

Bitcoin's most significant protocol upgrades have been implemented as soft forks specifically because they preserve this continuity. SegWit (Segregated Witness), activated in August 2017, restructured how transaction signature data is stored within a block, effectively increasing the amount of transaction data that can fit within a block's weight limit without changing the block size limit itself; a soft fork because old nodes could still validate the new blocks, even without understanding the new witness data structure fully. Taproot, activated in November 2021, introduced improved privacy (through Schnorr signatures, which make certain complex multi-signature transactions indistinguishable from simple ones on-chain) and enhanced smart-contractSmart ContractsA smart contract is a self-executing computer program deployed on a blockchain. It contains rules and conditions written directly into code.Keep learning-like scripting capabilities at Bitcoin's base layerLayer 1 BlockchainLayer 1 blockchain is the base network of a blockchain system that processes transactions and provides security without relying on another chain.Keep learning; again, implemented as a soft fork to preserve backward compatibility across the full node ecosystem.

Both of these upgrades were proposed, debated, and coordinated through the Bitcoin Improvement Proposal (BIP) process documented in our blockchain protocol article, and you can read their full technical specifications; BIP 141 for SegWit, BIPs 340-342 for Taproot; directly in the Bitcoin BIPs repository on GitHub. The full, unfiltered record of the debates surrounding each is also preserved there, offering a genuinely illuminating window into how a decentralized network without any central governance body actually coordinates meaningful protocol changes over time.

Hard Forks: Changing the Rules Entirely

A hard fork is a rule change that is not backward-compatible. It expands or alters what constitutes a valid block in a way that old nodes, running the pre-fork software, will reject; meaning that unless essentially the entire network upgrades simultaneously, old and new nodes will diverge onto separate chains, each following their own rules from the point of the fork onward.

Hard forks come in two meaningfully different varieties, which are easy to conflate but important to distinguish.

Planned Hard Forks

A planned hard fork is one where the entire network agrees in advance to adopt the new rules at a specific block height, and the overwhelming majority upgrades their software before that point. The result is a clean, smooth transition: old nodes are effectively deprecated, the new rules take effect network-wide, and the chain continues as a single, unified history.

Ethereum has used planned hard forks as its primary protocol upgrade mechanism throughout its history; the Byzantium, Constantinople, Istanbul, and Berlin upgrades are all examples of planned hard forks that passed cleanly because near-universal community consensus existed before the event. The Merge itself was a particularly complex planned hard fork (actually a combination of several coordinated changes) that executed exactly as designed. These events are announced well in advance, supported by clear community consensus, and coordinated through the EIP process documented throughout this series; you can read the complete archive of past and proposed Ethereum hard forks and their associated EIPs at ethereum.org/en/history.

Contentious Hard Forks

A contentious hard fork is where the distinction becomes genuinely dramatic: a proposed rule change that a meaningful faction of the network refuses to accept, resulting in a permanent chain split; two separate blockchains sharing an identical history up to the point of the fork, diverging from that point onward into entirely independent networks, each with its own validator set, its own community, and its own version of every transaction and asset that existed before the split.

The two most historically significant contentious hard forks in the industry are both worth understanding directly.

The DAO Fork (Ethereum / Ethereum Classic, 2016). The DAODAOsA DAO is an organization governed by code and community members rather than a central authority.Keep learning was an early Ethereum smart contract; a decentralized investment fund; that was exploited through the reentrancy vulnerability discussed in our blockchain securityBlockchain SecurityBlockchain security is the protection of blockchain networks and assets against attacks, fraud, and vulnerabilities using cryptography and consensus mechanisms.Keep learning article, with an attacker draining approximately $60 million worth of ETH at the time. Ethereum's community faced a genuinely difficult choice: allow the exploit to stand (preserving the principle that code is law and the blockchain is immutable, established throughout this series), or implement an irregular state change; a hard fork specifically altering the blockchain's state to return the drained funds, overriding the smart contract's "correct" execution. The majority chose the latter; a minority refused, preserving the original chain under the name Ethereum Classic (ETC). The debate this event ignited; around the limits of immutability, the role of developer intervention in crisis scenarios, and the nature of decentralized governance; remains one of the most philosophically significant episodes in the industry's history.

The Bitcoin Cash Fork (Bitcoin / Bitcoin Cash, 2017). A long-running debate within Bitcoin's community about how to address the block size limit and its role in driving up transaction fees reached an irreconcilable disagreement: one faction advocated for a soft fork approach (SegWit, ultimately adopted) to increase effective capacity; another argued that a direct, hard-fork increase to the block size limit itself was necessary for Bitcoin to function as a medium of exchange at scale. Unable to reach consensus, the latter faction hard forked Bitcoin at block 478,559 in August 2017, creating Bitcoin Cash (BCH) with an initially enlarged block size. Every Bitcoin holder at the time of the fork received an equal amount of BCH automatically; a consequence of the shared pre-fork history; making the event noteworthy for tokenCrypto TokensCrypto tokens are digital assets built on existing blockchains that represent value, access, or utility within a specific project or ecosystem.Keep learning holders as well as protocol developers. Further contentious splits from Bitcoin Cash itself (producing Bitcoin SV and other variants) illustrate how contentious forks can continue to propagate, since any sufficiently motivated minority can fork any public blockchain at any time.

What Happens to Users During a Fork

For ordinary users holding cryptocurrencyCryptocurrencyCryptocurrency, often called “crypto,” is a form of digital currency that uses cryptography (advanced math and code) to keep it secure.Keep learning at the time of a contentious hard fork, the experience is practically important and often misunderstood.

Because both post-fork chains share a complete, identical history up to the point of the split, a user holding, say, 1 BTC before the Bitcoin Cash fork found themselves, immediately afterward, holding 1 BTC on the original chain and 1 BCH on the new chain simultaneously; the same private keyPrivate KeysPrivate keys are secret cryptographic codes that give users full control over their crypto assets and are used to sign and authorize transactions.Keep learning valid on both, because both chains started from the same shared history. This is commonly referred to as receiving an airdropAirdropsAirdrops are free distributions of cryptocurrency tokens to wallets, often used to promote projects, reward users, or encourage adoption.Keep learning of the new chain's token, though it's more accurately understood as a direct consequence of chain splitting rather than a deliberate distribution.

This also creates a genuine security risk worth flagging directly: a transaction valid on both chains (sending funds using the same inputs) can be replayed on the opposite chain to drain funds there as well; an attack known as replay protection. Well-managed hard forks include explicit replay protection mechanisms; typically a chain ID embedded in transaction signatures that makes them valid on one chain only; to prevent this. Not all forks implement this cleanly, and users should verify what replay protection measures are in place before transacting on either chain immediately after a fork event.

Monitoring Forks in Real Time

Our blockchain protocol article referenced ForkMonitor.info for tracking chain divergence as it happens, and it's the most direct tool for understanding how fork detection actually works in practice. ForkMonitor watches Bitcoin, Ethereum, and several other networks continuously, alerting the community the moment any node reports a different chain tip than the consensus majority; catching both planned upgrade transitions and unexpected, unintended divergences the moment they occur.

For the broader context of how the Bitcoin community debates and coordinates protocol changes; including the full record of past fork events, rejected proposals, and ongoing discussions; Bitcoin Optech publishes weekly technical newsletters specifically tracking protocol developments and upgrade proposals, and maintains a searchable archive going back to its founding, representing one of the most thorough, technically accurate records of Bitcoin's ongoing protocol evolution available publicly.

The Governance Dimension

Forks are, ultimately, as much a governance story as a technical one. The ability to fork a public blockchain is, in a meaningful sense, the ultimate democratic safeguard of a decentralized network: if a community of sufficient size disagrees strongly enough with the direction of a network, they always have the option of forking; taking the shared history and building something different from that point forward.

This is also why the governance processes described in our blockchain protocol article; BIPs for Bitcoin, EIPs for Ethereum; are so important: they represent an attempt to build broadly legitimate, community-legible processes for reaching consensus about protocol changes before the question of an irreconcilable fork ever has to be raised. Contentious forks tend to happen precisely when those processes break down, or when a faction concludes that the process itself is being captured or ignored.

It's worth noting, too, that the economic weight of miners, validators, exchangesCEXs (Centralized Exchanges)Centralized exchanges (CEXs) are platforms run by companies that facilitate crypto trading by acting as intermediaries between buyers and sellers.Keep learning, walletsCrypto WalletsA crypto wallet doesn’t store coins like a piggy bank. Instead, it keeps keys that let you access your crypto on the blockchain.Keep learning, and large holders all play a meaningful role in determining which side of a contentious fork ultimately attracts the most users and economic activity; a reminder that blockchain governance, despite its technical surface, ultimately resolves through the same combination of persuasion, incentive alignment, and collective action as any other form of human coordination.

Bringing It Together

Forks are the mechanism through which decentralized networks change; sometimes smoothly and by broad agreement, sometimes messily and with lasting consequences for the communities involved. To summarize:

• A fork is any change to a blockchain's rules that causes, or risks causing, nodes to disagree about what's valid
• Soft forks tighten the rules in a backward-compatible way, allowing old and new nodes to coexist on the same chain throughout the transition; the mechanism behind Bitcoin's SegWit and Taproot upgrades
• Planned hard forks change rules in a non-backward-compatible way by broad pre-arranged agreement, resulting in a clean transition; the mechanism behind Ethereum's historical upgrade series
• Contentious hard forks result in permanent chain splits when a meaningful minority refuses to adopt new rules; producing Ethereum Classic from Ethereum and Bitcoin Cash from Bitcoin, in the two most historically significant examples
• Users holding assets at the time of a contentious fork automatically hold assets on both resulting chains, with replay protection (or its absence) being a critical practical concern
• Forks are fundamentally a governance story as much as a technical one; the ultimate expression of the fact that in a truly decentralized network, no single party can force a rule change on everyone else

Taken together with our earlier articles on protocols, consensus mechanisms, and the specific networks that have experienced them firsthand, forks emerge as the clearest possible illustration of what decentralized governance actually looks like in practice: messy, contested, sometimes dramatic, and ultimately resolved not by any authority's decree but by the collective choices of thousands of independent participants.