A hard fork is a rule change that splits a blockchain into two incompatible networks, because old software refuses the new rules. A soft fork is a tightening of the rules that old software still accepts. The hard fork vs soft fork difference is therefore about compatibility, not about who wins an argument.
The standing note: L4 News publishes information, not investment advice. Crypto assets can lose most or all of their value quickly, and nothing on this site is a reason to buy any of them. Forks multiply networks, not certainties — as you will see, sometimes literally.
What is a soft fork?
A soft fork is a rule change that stays compatible with older software. Nodes that have not upgraded still accept the new blocks, even though they cannot enforce the new rules themselves. It is a tightening: the updated network agrees to treat as invalid something that used to be optional or unused.
The cleanest example is SegWit, activated on Bitcoin in August 2017. It changed how block data is counted — separating signature data so more transactions fit in the same block — while a node from 2015, never upgraded, would still have accepted every SegWit block as valid. Nobody was forced to move, which is what let a diverse, stubborn network adopt it.
Coordination still matters. Miners and node operators signal readiness in advance, and activation waits for thresholds, so the whole network steps onto the new rule at the same block rather than drifting apart. Slow, procedural, unglamorous — soft forks are the diplomatic channel of protocol politics.
What is a hard fork?
A hard fork is a rule change that breaks compatibility. Updated nodes produce blocks that old nodes reject outright, so unless everyone moves together the network splits into two chains with one shared history. Bitcoin Cash was born this way on August 1, 2017, at block 478,559, out of a dispute over block size.
The Bitcoin Cash split is the textbook case. One camp wanted bigger blocks for cheaper payments, the other refused on grounds of decentralization and node costs; no soft-fork compromise survived. At the agreed block height the chains separated, and everyone who held bitcoin before the split found they held two coins on two networks after it.
Not every hard fork is a divorce. Ethereum's developers ship scheduled hard forks — they call them network upgrades — as routine maintenance, and its ecosystem follows in step. The lesson is that contention splits chains; the hard-fork label merely describes the technical step used.
| Soft fork | Hard fork | |
|---|---|---|
| Compatibility | Old software accepts new blocks | Old software rejects new blocks |
| Chain split | Not required | Built-in risk; two chains can result |
| Who must upgrade | Only those enforcing the new rule | Everyone, on schedule, or be left behind |
| Famous example | SegWit, August 2017 | Bitcoin Cash, August 1, 2017; the DAO fork, July 2016 |
What happened with Ethereum's DAO fork?
In June 2016 an attacker drained about 3.6 million ether from an investment fund called The DAO. Ethereum's community executed a hard fork on July 20, 2016 that returned the funds, and the minority who refused the intervention kept the original chain alive as Ethereum Classic. It remains the most consequential fork to date.
The dispute was philosophical, not technical. One side argued code is law — whatever the buggy contract allowed, stands; the other argued a theft this large, weeks into the fund's life, warranted an extraordinary correction. Ethereum's founders sided with correction. The minority that continued the old chain turned a moral position into a second network, and both still run.
The episode set a precedent people still argue about: a blockchain community can rewrite history when enough of it wants to — and doing so costs it the members who wanted purity over mercy. Every fork since has been read against that 2016 decision.
Why does fork also mean a copy of the software?
Because open-source code is forked in the GitHub sense long before chains split. Downloading the code and starting your own network with new parameters is also called a fork, which is how many alternative coins began — as modified copies of Bitcoin's or Ethereum's code with no chain split involved at all.
Context usually disambiguates. A protocol fork changes rules on a live network; a code fork starts something new from borrowed source. Litecoin began as a Bitcoin code fork in 2011, for instance, with faster blocks — a new chain from day one, no split of the original. When a headline says fork, check which sense is meant before deciding anything.
Do forks change anything for your coins?
Usually nothing, until you act. A rule change that everyone follows leaves balances untouched. A chain split can briefly show identical balances on two networks, and handling the second network's coins — moving them, swapping them — is where mistakes and scams cluster. Wallet software support also differs per network after a split.
The safe posture after any split is patience. Keep keys offline and unused until each network's post-split software has settled; treat any urgent claim site, airdrop popup, or must-import-your-seed-phrase message as hostile by default — real forks never require your seed phrase on someone else's website. Security firms repeat this every time a prominent split happens, because victims keep supplying the counterexamples.
Then decide deliberately. Holding both coins, selling one, ignoring the new network entirely — each is defensible, and none is urgent in the first days. Forks are the blockchain's amendment process; amendments deserve reading, not reflexes.
For more context, read What is a blockchain node?.
For more context, read public vs private blockchain.
For more context, read Layer 1 vs Layer 2, explained.
