Bitcoin Classic
2016–2017 software client proposing a 2 MB block-size hard fork — never activated a lasting chain split
Overview
Bitcoin Classic was an alternative full-node implementation of Bitcoin, forked from Bitcoin Core, that emerged in early 2016 during the block-size wars. Its main goal was to raise the maximum block size from 1 MB to 2 MB via a hard fork (BIP 109-style activation).
Unlike later successful coin-producing forks such as Bitcoin Cash, Bitcoin Classic never gained enough sustained miner and economic support to trigger a permanent chain split. It remained a competing client on the same Bitcoin network and eventually shut down after Bitcoin Cash launched and the scaling debate moved on.
Context: The Block Size Wars
By 2015–2016, Bitcoin’s 1 MB block limit was producing growing mempool backlogs and rising fees. Several alternative clients appeared to push on-chain scaling:
- Bitcoin XT (2015) — more aggressive (up to 8 MB, then doubling).
- Bitcoin Classic (2016) — more modest 2 MB proposal.
- Bitcoin Unlimited — let nodes/miners set their own limits.
Bitcoin Classic was positioned as a compromise: large enough to relieve short-term congestion, small enough to be more widely acceptable than XT’s bigger jumps.
How Activation Was Supposed to Work
Classic planned a miner-activated hard fork:
- Miners would signal support in block version bits.
- Once roughly 75% of the last 1,000 blocks signaled (750/1,000), a grace period (typically 28 days) would begin.
- After the grace period, Classic nodes would accept blocks up to 2 MB.
- If a sufficient majority of economic nodes and miners upgraded, the network would move to the larger limit; otherwise a split (or stalled activation) was possible.
In practice the required sustained support never materialized at the necessary level for long enough to lock in the change.
Key People & Development
Early contributors and supporters included Jonathan Toomim (significant technical work and testing), involvement or support from figures such as Gavin Andresen (who had previously advocated larger blocks), Jeff Garzik, and others. The project released software based on Bitcoin Core 0.11.x / 0.12.x with the 2 MB limit and related improvements (faster validation/propagation work, later ideas for more flexible limits).
Over time Classic’s roadmap evolved from a fixed 2 MB hard fork toward more market-driven / node-operator-chosen limits, overlapping in spirit with Bitcoin Unlimited.
Outcome
Bitcoin Classic never activated a lasting hard fork on the main Bitcoin chain. Hashrate and node adoption peaked but then declined as the community polarized further and other proposals (SegWit, the New York Agreement / SegWit2x, and ultimately Bitcoin Cash) dominated attention.
In November 2017, after Bitcoin Cash had successfully launched as the big-block chain (August 2017) and SegWit had activated on Bitcoin, the Bitcoin Classic project announced it was shutting down. Its original goal of enabling larger on-chain capacity had, in a sense, been realized on a separate chain, and the Classic client itself was no longer needed.
Technical Snapshot
| Type | Full-node software fork of Bitcoin Core |
|---|---|
| Primary proposal | Raise max block size from 1 MB to 2 MB |
| Activation method | Miner signaling (~75% of recent blocks) + grace period |
| Produced new coin? | No — never created a permanent alternate chain with its own ticker |
| Relation to Bitcoin Cash | Philosophical predecessor in the big-block camp; BCH succeeded where Classic did not |
| Status | Project closed November 2017 |
Historical Significance
Bitcoin Classic is an important chapter in the block-size wars. It showed both the strength of demand for on-chain capacity and the difficulty of coordinating a contentious hard fork on Bitcoin itself. Its failure (and the parallel rise of Bitcoin Cash) helped clarify that major rule changes without broad consensus would more likely produce separate coins than rewrite the original chain’s rules.