What it means
Blockchains such as Bitcoin run on rules that every participating computer, called a node, agrees to follow. When the community wants to change those rules, it can do so by a soft fork or a hard fork.
In a soft fork, the new rules are a stricter subset of the old rules. Blocks of transactions created under the new rules are still accepted as valid by old software, so the network does not split into two separate chains as long as most of the computing power follows the upgrade.
A hard fork, by comparison, changes the rules in a way that old software rejects. That can lead to two competing chains and, sometimes, two different digital assets.
Bitcoin Cash, created by a hard fork of Bitcoin, is a well-known example. For businesses and investors, the difference affects risk.
A soft fork usually causes little disruption for holders and exchanges, while a hard fork can require action such as updating software, pausing deposits or deciding how to treat a new coin. Soft forks are often used to add features, fix security weaknesses or improve efficiency.
They still depend on broad support, because if enough participants refuse the change, the network can become unstable. Soft forks are usually activated when a required share of the network signals support, and each blockchain sets its own threshold.
Until that point is reached, the old rules continue to apply. Businesses that rely on a blockchain should follow these signals so they know when the new rules take effect.
In practice
Real-world examples.
Example
A cryptocurrency exchange receives notice of a planned soft fork to improve transaction privacy. Its operations team confirms that customer balances will not change, upgrades its software in a scheduled window, and keeps trading open throughout. A short notice to customers explains that no action is needed on their part, which avoids a flood of support questions.
Example
A fintech company that settles payments over a blockchain reviews a proposed upgrade. Its technology lead checks that the change is a soft fork, so its existing wallets will keep working without migration. She records the review in the technology risk log so that auditors can see the change was assessed.
Example
A venture investor holding a stake in a blockchain start-up asks whether the next planned network change is a soft fork or a hard fork. A hard fork would require valuing a possible new token, so the investor asks for a legal and tax review first. The review covers whether any new asset would be taxable on receipt and how it would be valued for reporting.
Case study
Seen in the real world.
Ledgerline Network is an illustrative, fictional blockchain used by trade finance companies to record shipping documents. Its developers wanted to reduce the size of each record so that more transactions could fit in a block. Slow confirmations had frustrated customers who waited for shipping records to be finalised.
They designed the change as a soft fork so that participants who updated slowly would not be cut off. Within three weeks, about 85% of the network's validating computers had upgraded, and the remaining ones continued to see valid blocks. The developers published weekly progress updates so that user firms could plan their own testing.
The illustrative outcome was a smooth upgrade with no new token and no customer disruption. Because the change reduced the size of each record, the network could also handle more trade documents in the same time, which helped the busy shipping season. The finance lead at one user firm recorded only a small staff-time cost and no accounting change, because the assets held were unaffected. The only real cost was a few hours of testing in the technology team.
Watch out
Common mistakes.
- Assuming a soft fork creates a new coin and expecting a free asset to appear in the wallet, when only a hard fork can split a chain into two assets, and even then the outcome depends on how many participants follow each version.
- Believing that old software is completely unaffected, since nodes that do not upgrade may not enforce or understand the new rules.
- Ignoring the need for broad agreement, because even a soft fork can fail if too few participants adopt it.
Questions
People also ask.
What is the difference between a soft fork and a hard fork?
A soft fork stays compatible with older software, while a hard fork breaks compatibility and can create two separate chains. Think of a soft fork as a tighter set of house rules that old players can still follow, and a hard fork as a different game.
Do holders need to do anything after a soft fork?
Usually not, since their balances stay where they are, though holders should check with their wallet provider or exchange in case of recommended software updates, because exchanges and wallets sometimes need to upgrade their own systems.
Why do developers choose a soft fork?
It lowers the risk of a chain split and lets the network upgrade gradually, which is less disruptive for users and businesses. It also avoids the need to value or account for a brand new asset.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%