Terminology
| Term | Definition |
|---|---|
| Chainsplit | A split in the blockchain, resulting in two separate chains with a common ancestor. Can occur due to hardforks, softforks, or neither. |
| Hardfork | A loosening of consensus rules, making previously invalid blocks valid. Requires node upgrades. |
| Softfork | A tightening of consensus rules, making previously valid blocks invalid. Existing nodes may not require upgrades. |
(Originated April 2012, formalized in BIP99 and BIP123.)
List of Bitcoin Consensus Forks
| Date | Activation Block | BIP/Version | Description | Type | Outcome |
|---|---|---|---|---|---|
| 28 Jul 2010 | n/a | 0.3.5 | Disabled OP_RETURN, fixing a critical bug allowing arbitrary Bitcoin spends. | Softfork | Smooth upgrade, no issues. |
| 31 Jul 2010 | n/a | 0.3.6 | Disabled OP_VER/OP_VERIF, removing DoS vectors. | Softfork | Users advised to upgrade or shut down. |
| 15 Aug 2010 | 74,638 | 0.3.10 | Fixed output-value-overflow bug post-184.5B BTC exploit. | Softfork | Chainsplit (51 "bad" blocks reversed). |
| 12 Sept 2010 | 79,400 | n/a | Enforced 1MB blocksize limit. | Softfork | No issues. |
| 24 Mar 2013 | 227,835 | BIP34 | Required block height in coinbase TX. | Softfork | 95% threshold success. |
| 11 Mar 2013 | 225,430 | 0.8.0 | Unplanned hardfork from BDB to LevelDB migration. | N/A | Chainsplit (24 blocks), reverted. |
| 14 Nov 2021 | 709,632 | BIP341 (Taproot) | Combined Schnorr signatures and MAST for privacy/scalability. | Softfork | 90% miner activation success. |
Key Takeaways
- Hardforks require network-wide upgrades (e.g., Taproot).
- Softforks maintain backward compatibility (e.g., SegWit).
- Chainsplits are rare but possible (e.g., 2010 overflow bug).
👉 Explore Bitcoin’s evolution for deeper insights.
FAQ
Q: What’s the difference between hardforks and softforks?
A: Hardforks relax rules, requiring upgrades; softforks tighten rules, often backward-compatible.
Q: Did Taproot cause a chainsplit?
A: No, it activated smoothly with 90% miner support.
Q: Why was the 1MB limit introduced?
A: To prevent spam attacks and ensure network stability (2010).
(Sources: BitMEX Research, Bitcoin Core GitHub, BIP documentation.)
### SEO Keywords
1. Bitcoin consensus forks
2. Hardfork vs softfork
3. Taproot activation
4. Blockchain chainsplit
5. Bitcoin upgrade history