Simple Base SwapSimple Base SwapOpen app
← All articles
Nov 15, 2026·5 min read

Hard Forks and Soft Forks, Explained

basefundamentalsethereum
base

You have probably seen the word "fork" attached to a coin you have never heard of: Bitcoin Cash, Ethereum Classic, Litecoin Cash. The term gets thrown around loosely in crypto media, but it describes a specific and fairly simple idea: a change to a blockchain's rules, and what happens to the network when that change rolls out.

What a fork actually is

A blockchain is just software that every participating computer, called a node, runs in parallel. All of those nodes have to agree on the same rules for what counts as a valid block and a valid transaction. When the people who maintain that software want to change the rules, whether to fix a bug, add a feature, or adjust something like block size or fee calculation, they release an updated version of the client software. A fork is simply the moment that update creates a fork in the road: nodes running the old version and nodes running the new version may or may not be able to agree with each other anymore.

What determines the outcome is whether the new rules are backward compatible.

Soft forks: tightening the rules without splitting the chain

A soft fork makes the rules stricter in a way that old nodes still accept. Blocks produced under the new rules look valid to a node that never upgraded, even though that old node cannot fully understand or enforce the new feature itself. Because old and new nodes keep agreeing on which chain is the real one, the network stays in one piece. Bitcoin's Segregated Witness upgrade in 2017 is a commonly cited example: it changed how transaction data was structured, but it did so in a way that unupgraded nodes could still validate the resulting blocks.

Soft forks are generally considered the smoother upgrade path because they do not require every single node operator to update immediately. That said, a soft fork is not automatically risk free. If a large share of the network has not upgraded, it can end up following rules it never explicitly agreed to, which raises its own questions about consent and coordination.

Hard forks: when the rules change enough that the chain can split

A hard fork changes the rules in a way that is not backward compatible. A node running the old software will reject blocks created under the new rules, and a node running the new software will reject blocks created under the old rules. For the network to stay unified, everyone has to upgrade together.

Most hard forks are routine. A project announces a scheduled upgrade, node operators and miners or validators update their software by an agreed block height or date, and the network moves forward as one chain with new capabilities. Ethereum has gone through many of these over the years as part of its normal development cycle, each one bundling a set of Ethereum Improvement Proposals into a single coordinated release.

The more well known version of a hard fork is the contentious kind, where part of the community refuses to adopt the new rules and keeps running the old software instead. At that point you do not get one upgraded chain, you get two separate chains that share the same history up to the fork point and then diverge. Anyone holding the original asset before the split ends up holding a balance on both resulting chains. This is how Bitcoin Cash split off from Bitcoin in 2017 over a disagreement about block size, and how Ethereum Classic split off from Ethereum in 2016 after the community disagreed about whether to reverse the effects of the DAO hack. In both cases, the split created a second, independently maintained token with its own price and its own future, separate from the original.

It is worth being precise here: a hard fork is not the same thing as a new coin automatically appearing. Plenty of hard forks happen with full community agreement and no chain split at all. A split only happens when two groups keep mining or validating separately after a disagreement.

How this idea applies to a rollup like Base

Base works differently from Bitcoin or Ethereum's base layer in a way that is relevant here. It does not have thousands of independent miners or validators who could each choose to run different software. Base runs on the OP Stack, and its upgrades are coordinated protocol releases rather than open invitations for part of the network to break away. If you want more detail on how that process actually works in practice, including the naming convention Base inherits from the broader OP Stack ecosystem, that is covered in a separate article on how Base network upgrades roll out.

The practical difference for you as a wallet user is that Base is not a candidate for the kind of contentious hard fork that produces a second, rival token the way Bitcoin Cash or Ethereum Classic did. Upgrades still happen and still matter, but they look much more like a scheduled software release than a political split.

What this means for you

If you ever see news of a hard fork on a chain you hold assets on, the first question worth asking is whether it is a coordinated, non contentious upgrade or an actual contested split. A coordinated upgrade usually just means new features or lower fees once it finishes rolling out, with nothing for you to do. A contested split is a different situation entirely: you may end up holding a balance on two separate chains, each with its own wallet support, its own exchange listings, and its own risks. Either way, the safest move is the same one that applies to most unfamiliar crypto events: do not rush to interact with a new network or claim a new token based on a social media post alone, and confirm what is actually happening from a project's own official channels before you act.

Ready to try it yourself?

Create a non-custodial wallet on Base in seconds. No account, no sign-up.

Open the web app