Definition
Fork is a divergence in a blockchain or its software, where two valid versions of the chain (or two codebases) split from a common ancestor. In Bitcoin, a fork can be a temporary split in the block history, a permanent change to the consensus rules, or a copy of an open-source project that goes its own way.
Also known as: chain split, protocol fork, code fork.
The three meanings of “fork”
The word does heavy lifting in Bitcoin, so it helps to separate three distinct ideas. First, a natural or temporary fork happens when two miners find a valid block at nearly the same moment and the network briefly holds two competing tips. This resolves on its own: under the longest-chain rule, the branch that accumulates the most proof-of-work wins, and the losing block becomes an orphan block or stale block.
Second, a consensus fork is a deliberate change to the rules every node enforces. These come in two flavours: a soft fork, which tightens the rules so old nodes still accept new blocks (SegWit and Taproot were soft forks), and a hard fork, which loosens or breaks the old rules so non-upgraded nodes reject the new chain entirely. A contentious hard fork can permanently split the network into two coins.
Soft forks, hard forks, and chain splits
The distinction matters because of who has to upgrade. A soft fork is backward-compatible: as long as a majority of hashrate enforces the new rule, the network stays unified and old software keeps following along. This is how SegWit and later Taproot were activated — incremental upgrades signalled in part through the block version field.
A hard fork is not backward-compatible. Every node and every miner must adopt the new rules or be left behind on a different chain. When the community disagrees, the result is a chain split: a single shared history that diverges into two separate ledgers, each with its own coin. Several Bitcoin hard-fork coins exist for exactly this reason — they branched away rather than reaching consensus on the same rules. This is decentralization in its rawest form: nobody can force a rule change, and anyone who disagrees is free to fork off and let the market decide which chain has value.
Why an ASIC miner should care
For someone running an ASIC at home, forks touch the bottom line in three ways. Temporary forks cost you directly: if your mining pool finds a block that loses the race, the reward evaporates and your share of it disappears. Pools with low propagation delay and well-connected nodes orphan fewer blocks, which is one quiet reason pool choice matters beyond just the pool fee.
Consensus forks affect what your hardware is even mining for. A soft fork like SegWit changed how transactions are packed into a block, which in turn shaped transaction fees and the economics of every block reward you chase. Because Bitcoin’s SHA-256 algorithm has stayed stable across these upgrades, your S19, S21, or Bitaxe keeps working through them — you simply want your pool’s full node upgraded so you are always building on the chain the economic majority follows. If you run your own node behind a solo setup, keep Bitcoin Core current so a fork never leaves you mining a dead branch. You can browse current-generation hardware on the miners catalogue, or explore small open-source rigs at the Bitaxe hub.
Software forks: the open-source kind
The term also describes copying a codebase. Most of the open-source mining world is built on forks: pool software like CKPool has dozens of community forks, and lightweight firmware projects such as ESP-Miner have been forked to support new chips and boards. Forking is how a permissively or GPL-licensed project spreads — one developer builds on another’s work, credits the original, and improves it. That collaborative, stand-on-the-shoulders-of-giants pattern is the same spirit behind every open-source firmware effort. If you want to dig into community-built tooling and hardware, the open-source category is a good starting point.
Related terms: Hard Fork, Soft Fork, Orphan Block, Longest Chain Rule, SegWit, Taproot
In Simple Terms
A split in the blockchain into two paths. Can be temporary from competing blocks or permanent from rule changes.
Fork is a divergence in a blockchain or its software, where two valid versions of the chain (or two codebases) split from a common ancestor. In Bitcoin, a fork can be a temporary split in the block history, a permanent change to the consensus rules, or a copy of an open-source project that goes its own way.
Also known as: chain split, protocol fork, code fork.
The three meanings of "fork"
The word does heavy lifting in Bitcoin, so it helps to separate three distinct ideas. First, a natural or temporary fork happens when two miners find a valid block at nearly the same moment and the network briefly holds two competing tips. This resolves on its own: under the longest-chain rule, the branch that accumulates the most proof-of-work wins, and the losing block becomes an orphan block or stale block.
Second, a consensus fork is a deliberate change to the rules every node enforces. These come in two flavours: a soft fork, which tightens the rules so old nodes still accept new blocks (SegWit and Taproot were soft forks), and a hard fork, which loosens or breaks the old rules so non-upgraded nodes reject the new chain entirely. A contentious hard fork can permanently split the network into two coins.
Soft forks, hard forks, and chain splits
The distinction matters because of who has to upgrade. A soft fork is backward-compatible: as long as a majority of hashrate enforces the new rule, the network stays unified and old software keeps following along. This is how SegWit and later Taproot were activated — incremental upgrades signalled in part through the block version field.
A hard fork is not backward-compatible. Every node and every miner must adopt the new rules or be left behind on a different chain. When the community disagrees, the result is a chain split: a single shared history that diverges into two separate ledgers, each with its own coin. Several Bitcoin hard-fork coins exist for exactly this reason — they branched away rather than reaching consensus on the same rules. This is decentralization in its rawest form: nobody can force a rule change, and anyone who disagrees is free to fork off and let the market decide which chain has value.
Why an ASIC miner should care
For someone running an ASIC at home, forks touch the bottom line in three ways. Temporary forks cost you directly: if your mining pool finds a block that loses the race, the reward evaporates and your share of it disappears. Pools with low propagation delay and well-connected nodes orphan fewer blocks, which is one quiet reason pool choice matters beyond just the pool fee.
Consensus forks affect what your hardware is even mining for. A soft fork like SegWit changed how transactions are packed into a block, which in turn shaped transaction fees and the economics of every block reward you chase. Because Bitcoin's SHA-256 algorithm has stayed stable across these upgrades, your S19, S21, or Bitaxe keeps working through them — you simply want your pool's full node upgraded so you are always building on the chain the economic majority follows. If you run your own node behind a solo setup, keep Bitcoin Core current so a fork never leaves you mining a dead branch. You can browse current-generation hardware on the miners catalogue, or explore small open-source rigs at the Bitaxe hub.
Software forks: the open-source kind
The term also describes copying a codebase. Most of the open-source mining world is built on forks: pool software like CKPool has dozens of community forks, and lightweight firmware projects such as ESP-Miner have been forked to support new chips and boards. Forking is how a permissively or GPL-licensed project spreads — one developer builds on another's work, credits the original, and improves it. That collaborative, stand-on-the-shoulders-of-giants pattern is the same spirit behind every open-source firmware effort. If you want to dig into community-built tooling and hardware, the open-source category is a good starting point.
Related terms: Hard Fork, Soft Fork, Orphan Block, Longest Chain Rule, SegWit, Taproot