English English

Hard Fork: How Blockchain Upgrades Can Lead to a Split

Paul Ferguson - Author at Coinminutes Paul Ferguson Published November 14, 2026 04:41 PM
Learning crypto often means encountering familiar words in unfamiliar settings. “Hard fork” is a striking example: a phrase that offers few clues to readers seeing it for the first time.
Hard Fork: How Blockchain Upgrades Can Lead to a Split
Table of contents
    View more

    The 2016 DAO hard fork of Ethereum created a lasting debate. This debate continues today in the form of two cryptocurrencies: ETH and ETC (Ethereum Classic). Five years later, Ethereum’s London hard fork changed transaction fees without requiring holders to exchange their ETH for a replacement coin.

    This can cause confusion when you receive an upgrade notification in your wallet. Is this a new coin, a software upgrade, or a reason to stop sending money?

    In this Coinminutes’ guide, I have compared the technical details to user friendly guidelines. This shows how upgrading the rules is a completely different process to maintaining two distinct blockchains. This makes the terminology much less scary.

    1Hard Fork Fundamentals

    Blockchain technology uses computers to agree on what transactions are valid. A hard fork changes the basis of that agreement.

    Hard Fork Meaning in Plain English

    A hard fork is an upgrade to a blockchain that is not backward compatible. This means that the consensus rules (rules around what constitutes a valid transaction and block) have been changed. Nodes running the old rules will reject blocks that are valid under the upgrade but violate those earlier rules. The definition of a hard fork by NIST is: when a blockchain upgrade changes consensus rules in a way that is not backward compatible.

    Hard Fork Meaning in Plain English A hard fork changes a blockchain’s validation rules so that older software rejects blocks that the new rules allow.

    For example, a blockchain limits blocks to 1 megabyte and an upgrade raises that limit to 2 megabytes. A node enforcing the old limit will reject a 2-megabyte block, while an upgraded node can accept it if it meets all other requirements. The disagreement comes from different validation rules, regardless of how many people support either version.

    This causes a disagreement around the validity: what the ledger is allowed to contain.

    Why Blockchains Change Their Consensus Rules

    There are many reasons a network may wish to change consensus rules. This could be to fix vulnerabilities, increase capacity, add features or change incentives. Sometimes these changes require a hard fork as they cannot be done without breaking backward compatibility.

    EIP-1559 was implemented with the London upgrade. It introduced a protocol-calculated base fee that adjusts according to block utilization. This required a number of changes to the software on the network to ensure these base fees were validated in blocks. This was a large change to the network.

    The term “hard fork” simply refers to whether the upgrade was backward compatible.

    Does Every Hard Fork Split a Blockchain?

    If the upgrade is widely adopted and there is no viable alternative, then the network will continue with the new rules.

    A lasting split would only occur when people continue creating blocks, maintaining software and using both chains. While Ethereum has had generally well-coordinated upgrades, there have been rare disagreements such as the DAO fork. The possibility of divergence does not necessarily cause a split between two long-term currencies.

    The node may stop following the upgraded chain as it is outdated. That is a problem for their operators, but it doesn’t create a working alternative chain.

    2How a Hard Fork Works: From Proposal to Activation

    An upgrade specifies an activation condition, such as a block height, timestamp, or epoch. Any associated calendar date may be exact or estimated, depending on that condition.

    Proposals, Client Releases, and Network Testing

    Proposals will be made for how the change will work, why and what impact it will have on compatibility. Ethereum has a standard format for this in the form of Ethereum Improvement Proposals (EIPs). The EIP itself will not cause any changes to happen.

    Once a proposal has been agreed upon, client teams will develop the software to implement this. A client is the software used to run a node (the computer on the network). This is tested to ensure that the clients all produce the same outcome. This may be done on testnets so any errors won’t risk any funds on mainnet.

    Proposals, Client Releases, and Network Testing An Ethereum Improvement Proposal (EIP) describes a proposed change without activating it.

    London’s announcement had a very specific example of this. In July 2021, there was an issue on testnet which showed that different clients were validating transactions differently. They released fixed versions of the software and then activated the hard fork on mainnet. The clients need to produce the same outcome even if the code is different.

    What Happens at the Activation Block or Epoch?

    The updated software will have a condition to activate the new rules. Once this is met, the new requirements will be automatically applied. Developers won’t manually approve each node at the time of activation.

    The trigger can involve a block height, a timestamp, or an epoch. For example, the Shapella announcement for Ethereum had a specific consensus-layer epoch (194,048) and time (April 2023).

    Before activation, operators can install compatible software to prepare. Installing it after activation may leave the node unable to keep up with the updated network.

    Who Decides Which Rules the Network Follows?

    There are many people involved in influencing the decision. Developers will propose and implement the changes. Node operators will decide what software to use. Miners and validators will create the blocks. Exchanges, applications, and users will decide which network to support.

    Who Decides Which Rules the Network Follows? No single group controls a hard fork.

    On Ethereum, protocol governance is done off-chain. While holding ETH, you won’t necessarily have a binding vote on every upgrade. Public nodes won’t necessarily mean a one-node-one-vote system.

    Bitcoin Core contributors also explain that software is released for users to consider using. While this may introduce new rules, others need to use and accept this.

    3Hard Fork vs Soft Fork: Compatibility, Adoption, and Trade-Offs

    Both forks modify consensus rules. However, the key difference lies in how the new rules interact with existing software.

    How Old Nodes Treat New Blocks

    A soft fork narrows the range of valid blocks. Any blocks that meet the new criteria will also meet the existing rules. This means nodes running older software can accept the new blocks.

    A hard fork allows blocks that the older nodes cannot accept to be added to the upgraded chain. This causes a break in compatibility.

    How Old Nodes Treat New Blocks Differences in compatibility between hard fork and soft fork.

    Accepting a block and checking every rule behind it are different levels of assurance. Backward compatibility preserves the former for older nodes, without supplying the latter.

    Different Upgrade Paths and Coordination Costs

    A hard fork provides flexibility to implement changes that do not fit within the existing validation rules. This causes a clear coordination issue as the relevant operators must have compatible software before the upgrade.

    A soft fork maintains backward compatibility. However, there still needs to be a plan for activating and enforcing the upgrade. If there isn’t enough enforcement, issues can occur. The word soft doesn’t mean there aren't any coordination issues. The Bitcoin developer documentation mentions a few different ways of activating the change.

    The correct fork to use depends on the change being made and the situation of the network. The terms do not reflect the quality of the engineering.

    Protocol Forks, Code Forks, and Temporary Chain Splits

    A protocol fork refers to changes to the rules of an active blockchain. A code fork is a copy of a software project to be developed separately. Forking a repository on GitHub creates a copy that can be developed separately. However, it doesn’t split the live ledger. The repository is just a copy that links back to the upstream project. Copying the code does not cause a split in the live ledger or duplicate the holder's balances.

    A temporary chain split can occur if miners on the Bitcoin network discover alternative valid blocks. Over time the nodes will come to a consensus based around the total proof-of-work. As the chain is valid, any extra work cannot make an invalid block pass the checks of a node.

    This helps to avoid confusion between a short-lived alternative branch and a new cryptocurrency.

    4Hard Fork Examples: Three Events, Different Outcomes

    The best way to understand how a hard fork works is to consider what people decided to keep going with. Here are three examples.

    Bitcoin and Bitcoin Cash: A Dispute Over Scaling

    Bitcoin Cash was created as a result of a long-running argument over how to scale Bitcoin. Supporters wanted to increase the size of blocks on the blockchain to allow more transactions. Bitcoin Core’s stated aim is to ensure decentralization while scaling.

    Bitcoin and Bitcoin Cash: A Dispute Over Scaling Bitcoin Cash split from Bitcoin on August 1, 2017, over how to handle more transactions.

    The Bitcoin Cash specification from 2017 included that the first block after the fork would be over 1 megabyte big, supporting blocks up to 8 megabytes. This can be confirmed using the implementation documentation. Such a block would not have been able to be processed due to the original Bitcoin’s size limit.

    Both blockchains continued, but with separate currencies: BTC and BCH. While the two have the same transaction history, this does not mean that later payments are interchangeable.

    The main takeaway here is that there may be differing opinions on what should be prioritized with a payment network.

    Ethereum and Ethereum Classic: The DAO Fork

    The DAO fork happened because of an exploit on an application called The DAO, running on the Ethereum blockchain. The fork happened at block 1,920,000 and included a special state change to return funds from specific DAO-related accounts to a recovery contract.

    This is an easy thing to miss. The EIP-779 does not include any changes to the structure of transactions or virtual machine instructions. The fork applied a one-off state change that transferred ether from specified DAO-related accounts to a recovery contract. It did not erase the blockchain’s transaction history.

    While supporters agreed that this change should happen, others disagreed and the chain that did not go through the change continued as Ethereum Classic. Ethereum went through the change and now has ETH as its currency, while Ethereum Classic has ETC.

    For readers of Coinminutes, this example really highlights that there can be human disagreements over what should be done. Even with the same code, people can have differing opinions on if this change should be made.

    Ethereum’s London Upgrade: New Rules Without a New Mainstream Coin

    The London upgrade was implemented on August 5, 2021 at block 12,965,000. The most famous part of this upgrade was EIP-1559. This changed the way fees worked. Instead of using the previous model, it uses a base fee and optional priority fee, along with other changes. The base fee is burned; congestion can still make transactions expensive.

    Ethereum’s London Upgrade: New Rules Without a New Mainstream Coin Ethereum’s London upgrade activated at block 12,965,000 on August 5, 2021, introducing EIP-1559’s burned base fee and optional tip.

    This does not create the same long-term split between ETH and a new coin. Those holding ETH continued to use it, and those running the network needed to use compatible clients.

    After reading the holder FAQ, I was surprised at how different the tasks were. For normal users, there is generally nothing to do unless you are told by your provider. This was a major upgrade!

    5What a Hard Fork Means for Your Coins and Wallet

    Your next step will depend on the fork and how you’re holding your assets.

    Do You Automatically Receive Coins After a Hard Fork?

    Typically you won’t get any more assets from a planned upgrade. If there are two chains remaining and you have control of the relevant private keys, you may have control of the assets from both chains.

    For example, if you had 1 BTC before the Bitcoin Cash fork, you may have 1 BTC and 1 BCH post-fork, but only if you have control of the relevant keys and compatible software. This doesn’t mean the value will be equal or you’ll make a profit. If you buy BTC after the fork, you won’t have any claim to the historical amount.

    Do You Automatically Receive Coins After a Hard Fork? One BTC held before the Bitcoin Cash split could give its holder access to one BTC and one BCH with the right keys and software.

    The relevant balance is the one recorded at the split. A transfer still waiting for confirmation has not yet changed that ledger, which is another reason to avoid last-minute movements between services.

    If you’re holding your assets on an exchange or custodian, this will depend on what they’re offering. Coinbase had a discussion in March 2018 about its policies. However, this doesn’t guarantee you’ll have safe access to all the forked assets. This is a historical document.

    Do You Need to Update Your Wallet or Move Your Funds?

    If you’re running a node, you’ll generally have to update the relevant client. The validator operator may have multiple components to update, for example, Shapella mentions regular holders, node operators and stakers. The validator software must be updated.

    If you’re holding your assets in a wallet that uses the provider's infrastructure, there may not be much to do. However, you should follow the instructions from your provider. If you’re using a hardware wallet, you won’t need to generate a new seed phrase.

    Don’t move your assets just because someone says you’ll get a reward. Make sure you know if you need to move them, what chain they’re on and if you can deposit or withdraw. The Bitcoin fork guidance explicitly mentions to be wary of scams offering to split your coins.

    Replay Attacks, Scams, and Split-Chain Risks

    A replay attack occurs when a signed transaction can be used on another chain. This can be replayed by someone else, which may cause unintentional transfer without them knowing your private keys.

    To prevent replay attacks, your transactions should be unique to each network. Ethereum has implemented EIP-155, which adds a chain ID to the signature. However, the spec also allows for old signatures. This will depend on the chains and transactions you’re using.

    Replay Attacks, Scams, and Split-Chain Risks Ethereum’s EIP-155 uses a chain ID to prevent a signed transaction from being reused on another chain with a different ID.

    Scams can also cause issues. Never input your seed phrase into a website that claims to "activate" your forked coins. MetaMask has security guidance stating that you won’t need to input your seed phrase into legitimate websites.

    There may also be low liquidity on the remaining branch. Just because there’s a price doesn’t mean you’ll be able to safely access and sell your balance. Coinbase had criteria in their historical review, including security flaws and consistent low liquidity.

    A Five-Point Checklist Before You Act

    Ask yourself the following questions before making any changes:

    • What is happening? Is it a coordinated upgrade or proposed alternative chain?

    • When is it activating? Check the official block, epoch, timestamp, and latest release notice.

    • Who has control of the keys? Check if your wallet or custodian supports the relevant network and distribution.

    • Are transfers safe? Check if there is replay protection, supported transaction types, and whether the service is available.

    • What do I actually need to do? Follow verified guidance from your provider and keep your recovery credentials private.

    From looking at these documents, I have learned that the first thing to do is identify what role you have. If you are a validator, hardware wallet holder, or exchange customer, you may have three different responsibilities to complete for the same activation.

    6Final Thoughts on Hard Forks

    A hard fork reveals where software agreement ends and human choice begins. Code can specify exactly what changes at a particular block; it cannot guarantee that everyone will accept the result.

    That is the distinction to carry into the next announcement you read on Coinminutes. Look beyond the upgrade’s name to the people maintaining the chain and the instructions that apply to your funds. Sometimes the lasting evidence is a second currency. Sometimes it is simply another block arriving under new rules.