A blockchain is, at its core, a shared rulebook. Thousands of computers around the world each keep a copy of the same ledger, and each one independently checks every new block against a list of rules: how big a block can be, what a valid signature looks like, how new coins are issued, and so on. As long as every participant runs software with the same rulebook, everyone arrives at the same answer about which chain is the real one. A fork is what happens when that agreement breaks down, or when the rulebook is deliberately changed.
The word "fork" gets used for two rather different things, so it helps to separate them. The first is a temporary, accidental fork. Two miners or validators can produce a valid block at almost the same moment, and for a short time part of the network sees one version of history and part sees another. This is normal and self-correcting: the network's consensus rules eventually pick one branch, usually the one that accumulates the most work or the most attestations, and the other block is discarded. Transactions in the orphaned block typically go back into the queue and get confirmed later. This is exactly why wallets and exchanges wait for several confirmations before treating a deposit as final.
The second kind of fork is a protocol fork: a deliberate change to the rules themselves. Because no single company owns a public blockchain, upgrading one means persuading node operators, miners or validators, wallet providers, and businesses to adopt new software. How that upgrade is designed determines whether it is a soft fork or a hard fork.
A soft fork tightens the rules. Anything the new software accepts would also have been accepted by the old software, but the new version rejects some things the old version allowed. Because the new rules are a subset of the old ones, nodes that never upgrade still see the upgraded chain as valid. They may not understand the new features, and they may not be able to fully verify them, but they stay on the same chain as everyone else. Soft forks are described as backward compatible for this reason, and they are often used to add features in a cautious way. The catch is that soft forks generally need a strong majority of block producers to enforce the tighter rules; if enforcement is weak, the network can temporarily split anyway.
A hard fork loosens or otherwise changes the rules in a way old software cannot accept. Blocks that are valid under the new rules look invalid to a node running the old version. That means everyone who wants to follow the upgraded chain has to update their software. If the whole community upgrades, the old chain simply stops being produced and the fork is smooth. If a meaningful group refuses, two chains continue in parallel, each with its own rules, its own block producers, and its own coin. Both chains share an identical transaction history up to the split point and diverge from there.
When a chain splits permanently, anyone holding coins at the moment of the split holds a balance on both chains, because both inherit the same ledger snapshot. This does not create value out of nothing; it divides a community, its security budget, and its developer attention between two networks, and the market prices each independently. Splits also raise practical issues. If the two chains use the same transaction format, a transaction broadcast on one might be replayable on the other, which is why developers usually add replay protection. Exchanges and custodial services often pause deposits and withdrawals around a contentious fork so that balances can be reconciled safely.
Forks are not a malfunction. They are the mechanism by which a decentralised system with no central authority changes, and also the mechanism by which disagreements get resolved: rather than one side winning a vote, both can run the software they prefer and let users, developers, and block producers decide where to go. Understanding whether a given upgrade is backward compatible, and whether your own software needs updating, is the practical takeaway for anyone holding or running a node.
This article is for general education only — not financial advice, and nothing here is a recommendation to buy, sell, or hold any asset. Cryptocurrency carries real risk of loss; always do your own research before making a financial decision.
