Coinbase throws support behind Bitcoin Classic as Bitcoin community faces schism over block size issue
Context & Ripple Effects
Coinbase's endorsement of Bitcoin Classic turns a developer-level argument about the block size limit into a fight between named commercial interests and the Core maintainers. Weeks later, CEO Brian Armstrong escalated sharply, arguing in his warning that the Core team is a systemic risk that bitcoin should switch to Classic now and pursue more scalable solutions after.
The dispute is an early round of the scaling war that culminated a year later: by mid-2017 competing proposals like SegWit2x and UASF had the community on the edge of a chain split, and when Bitcoin actually divided in two, many exchanges — Coinbase among them — declined to support the Bitcoin Cash fork at launch.
First-order effects
- Miners, wallet operators, and node runners must now choose between Bitcoin Classic and Core, and Coinbase's weight as a major consumer-facing exchange gives Classic a credibility boost it lacked as a minority proposal.
Second-order effects
- Other exchanges and wallet providers are pushed to take public positions on the block size question rather than stay neutral, since their customers' balances sit on whichever chain wins; Armstrong's framing of Core as a collapse risk forces Core-aligned businesses to defend the incumbent team explicitly.
Third-order effects
- The pattern points toward protocol governance being settled less by core developers than by whichever commercial infrastructure — exchanges above all — commits to a client, a dynamic that foreshadows the 2017 split where exchange support determined whether a fork's coins were usable at all.
The trend: Bitcoin's scaling fights are shifting governance power from volunteer core developers to commercial infrastructure operators like Coinbase, whose client endorsements and fork-support decisions increasingly decide which chain survives.