The Origins of the Bitcoin Scalability Debate
In the early days of the Bitcoin network, Satoshi Nakamoto implemented a soft fork in September 2010 that established a 1MB block size limit. This design was originally intended to prevent malicious transactions and network attacks, ensuring that ordinary nodes could easily synchronize the ledger. However, with the global adoption of cryptocurrencies and the surge in transaction volume, the 1MB block capacity gradually became unable to meet the growing transfer demand, leading to network congestion and soaring transaction fees, which laid the groundwork for subsequent divergences in scaling roadmaps.
The Technical Roadmap Struggle Between Two Core Camps
Facing the scalability bottleneck, two distinct technical roadmaps gradually emerged within the community:
- SegWit and the Core Faction: Adhering to the 1MB block size limit, they advocate optimizing transaction data structures through Segregated Witness (SegWit) and relying on Layer 2 solutions such as the Lightning Network to achieve efficient off-chain settlement, thereby safeguarding the decentralization and security of the network.
- The Radical Scaling Faction and the Big Block Camp: They advocate directly expanding the block capacity limit (such as increasing it to 8MB or higher) to accommodate more on-chain transactions, believing this is the most direct way to resolve network congestion and maintain low transaction fees.
Major Hard Forks and Derived Cryptocurrencies
Due to irreconcilable roadmap divergences, the Bitcoin network experienced several major hard forks throughout its development history:
- The Birth of Bitcoin Cash (BCH): On August 1, 2017, at block height 478,558, supporters of the big block roadmap officially executed a hard fork, giving birth to Bitcoin Cash (BCH) with a larger block capacity.
- The Split of Bitcoin SV (BSV): From November 15 to 16, 2018, due to further severe disagreements within the BCH camp over block size and protocol development roadmaps, Bitcoin SV (BSV) split off.
