Bitcoin history, told plainly

The great scaling debate

For two years the Bitcoin community argued over one number: how much data each batch of blocks should hold. The argument ended with a clever upgrade, a brand new coin, and a network stronger than ever. Here is the story, told plainly.

Reviewed and current as of September 12, 2026

01The one megabyte cap

In 2010 Satoshi Nakamoto set a 1MB cap on the transaction data each batch of blocks could carry. At the time it was a safety valve: it kept spam and junk data off the chain and kept the blockchain light enough for hobby computers to store a full copy. For years the cap sat quietly in the background, because batches of blocks rarely came close to filling it.

02Success fills the blocks

By 2015 Bitcoin was getting busy. Every batch of blocks arrived packed, and people started paying higher fees to get their transactions confirmed sooner. Confirmation times stretched. This was a good problem: it meant people wanted to use Bitcoin. The community agreed on that much. The open question was how to make room for everyone.

03Two camps, two visions

The big blockers wanted a simple fix: raise the cap so each batch of blocks carries more transactions. More room per batch means more transactions per second and lighter fees. They saw Bitcoin as digital cash for the whole planet, and cash needs room to breathe.

The small blockers wanted to protect what made Bitcoin special: the ability for anyone, anywhere, to run a node on ordinary hardware and verify everything themselves. Bigger blocks mean heavier storage and faster internet demands, and that could push everyday users out and leave the network in the hands of a few big players. They saw decentralization as the feature worth defending.

Both camps loved Bitcoin. They simply disagreed on the safest way to scale it. It is the blockchain trilemma in action: more throughput with the same decentralization, and every choice carries a trade.

04The roundtable and the clever idea

In February 2016 core developers and miners met in Hong Kong and sketched a compromise: activate a clever upgrade called SegWit first, and keep planning a bigger capacity increase for later. SegWit, short for Segregated Witness, had been proposed the year before by developer Pieter Wuille.

The idea was elegant: move the signature data out of each transaction and store it alongside, freeing room for more transactions inside the same 1MB space. Same cap, more room. It also fixed a long standing quirk called transaction malleability, which opened the door for the Lightning Network.

05August 2017, the split

By the summer of 2017 the pressure was on. Miners signaled support for SegWit through a mechanism called BIP91, and a grassroots movement called the user activated soft fork showed that everyday node operators held real power over the network's direction. On August 1, 2017, SegWit locked in, a moment fans celebrated as Bitcoin Independence Day.

That same day the big blockers took their own path: a group of miners and supporters launched Bitcoin Cash, a separate network starting with 8MB blocks. One community, two chains, each free to prove its vision in the open market.

06SegWit2x and the resolution

In May 2017 a group of companies and miners had signed the New York Agreement: activate SegWit, then double the cap to 2MB a few months later in a plan called SegWit2x. But as November approached, the wider community had settled on a different answer. Support for the second half of the plan faded, and organizers set it aside. SegWit went live on its own on August 24, 2017.

With SegWit active the Lightning Network flourished, moving millions of tiny instant payments off the main chain while settling on it. BTC kept the name, the developers, and the users. The debate had been loud, but the outcome was a network that scales in layers: a rock solid base chain plus fast payment rails on top.

For you, the reader, this story explains why Bitcoin upgrades move at the pace of consensus. Every change gets argued from every angle, tested in public, and adopted only when the community is ready. Slow on purpose is a feature, and the great scaling debate is the proof.