History Doesn't Repeat, But It Rhymes

What Linux's 35 Years Tell Us About Bitcoin's Future

On August 25, 1991, a 21-year-old Finnish student named Linus Torvalds posted a message to Usenet: "I'm doing a free operating system. Just a hobby, won't be big and professional like GNU."

That might be the most spectacularly wrong prediction in the history of technology. But I'm starting to think it has competition, because in 2008, a pseudonymous figure posted a nine-page paper to a cryptography mailing list describing "A Peer-to-Peer Electronic Cash System." The early response was polite skepticism. Most cryptographers had seen digital cash schemes fail before.

Both projects were dismissed as toys. Both were built by outsiders working without institutional backing. And both followed an arc that, 35 years later for Linux and 17 years in for Bitcoin, looks remarkably similar. The question I keep coming back to is whether that similarity is coincidence or pattern.

I don't think it's a coincidence. And I say that as someone who watched the first version of this story play out from inside corporate America.

Strangers Showing Up

Within months of Linus's post, a guy named Ted Tso in North America started contributing to the Linux kernel. No contract, no pay, nobody assigned him a ticket. More than three decades later, Ted still maintains EXT4, one of the most widely used file systems on the planet.

Bitcoin had its own version of this. Hal Finney ran the first transaction. Gavin Andresen started writing code. Jeff Garzik showed up. None of them were asked. None of them were paid. They looked at something unfinished and decided it was worth making better.

This is the engine that powers both projects, and it's the part that institutions consistently fail to understand. You can't manufacture it with a hiring plan or a grant program. It happens when the thing itself is compelling enough that talented people volunteer their nights and weekends. And once that starts, it's very hard to stop.

Different Is Safer Than Same

Around 2003, I was running a modest data center hosting servers for a handful of clients. A colleague suggested we cluster Linux DNS with Microsoft DNS in a mirror data center for redundancy. The idea wasn't that one operating system was better than the other. The idea was that a virus or bug that took down one OS wouldn't touch the other. Different infrastructure, different vulnerabilities, different failure modes.

One of the companies I was hosting for told me flatly: nothing but Microsoft in-house. Corporate policy. But they trusted my judgment on the hosted service they were paying for. So Linux ran quietly on their behalf, doing exactly what it was supposed to do, while their official position remained "we don't use open source."

That split personality defined the era. Companies knew open source was probably better. They also knew that if something broke, nobody ever got fired for buying Microsoft. The vendor wasn't just selling software. They were selling a name to put on the incident report when the shit hit the fan. Microsoft and IBM could weather those hits. A Linux mailing list could not.

Then, on August 14, 2003, the Northeast power grid collapsed. Fifty-five million people lost electricity across eight states and parts of Canada. The largest blackout in North American history. Our clients stayed up. The philosophy of distributing clustered services over two different operating systems in two different locations on two different power grids did exactly what it was designed to do. When one grid went dark, the other side kept serving DNS and Lotus Notes Domino like nothing had happened.

I didn't think about it in these terms at the time, but that experience taught me something I've carried ever since: resilience comes from heterogeneity, not just redundancy. A thousand copies of the same vulnerable system, spread across a thousand servers, all go down to the same exploit. Two different systems, built on different assumptions, with different attack surfaces, that's what actually survives.

And that's the strongest practical argument for Bitcoin alongside the dollar that I've found. You don't hold Bitcoin because you think the dollar is going to zero tomorrow. You hold it because when one grid goes down, the one built on different infrastructure keeps running. A centralized target gives you one thing to aim at. A distributed target built on fundamentally different infrastructure doesn't give you anything to aim at.

The Moat That Matters

Here's where the Linux and Bitcoin stories diverge, and the divergence is interesting.

Linux's protection against capture was legal. Linus re-licensed the kernel under the GNU General Public License in January 1992, and he later called it the best decision he ever made. The GPL meant that anyone could use, modify, and redistribute the software, but if you distributed a modified version, you had to share your changes under the same license. That single legal choice prevented any company from taking the code proprietary, and it made real collaboration durable.

Bitcoin's protection against capture is physical. The energy expended in proof-of-work IS the security. To rewrite Bitcoin's transaction history, you'd need to command more computational work than the entire network combined, sustained over time. No court order reverses a hash. No injunction undoes energy already spent.

Linux's moat is made of paper and legal precedent. It works because courts enforce it. Bitcoin's moat is made of thermodynamics. It works because physics doesn't negotiate.

Both moats held. But they hold against different kinds of attack, and that tells you something about what each project was actually designed to survive.

The Apex Predator Problem

In June 2001, Microsoft CEO Steve Ballmer called Linux "a cancer." He wasn't being dramatic. He was diagnosing, correctly, that the GPL was incompatible with the business model that had made Microsoft the most valuable software company on Earth. Microsoft was the apex predator of software, and it fought like one, because its revenue was directly threatened.

The Linux timeline tells us how this arc ends. Fifteen years after the "cancer" comment, Microsoft joined the Linux Foundation as a platinum member. Today, more than 60% of customer cores running in Microsoft's Azure cloud operate Linux workloads. The company that framed Linux as a disease now depends on it. Microsoft didn't choose to embrace open source. The market made the choice for them.

Now apply that pattern to money. Bitcoin threatens monetary sovereignty the way Linux threatened software licensing revenue, only the stakes are orders of magnitude higher. The apex predator of money isn't Microsoft. It's the US government with armies, with the legal authority to freeze accounts, impose capital controls, inflate the currency, and prosecute anyone who tries to build an alternative. They have a history of squashing competitors to the dollar.

So what is the apex predator doing? Buying Bitcoin for a strategic reserve.

In March 2025, an executive order established the U.S. Strategic Bitcoin Reserve. Eighteen months later, the reality is bureaucratic: cold wallets in desk drawers, no congressional authority to buy more, the BITCOIN Act working through Congress. But the direction is unmistakable. The United States government has formally declared Bitcoin a strategic asset worth holding.

Either they don't understand that Bitcoin's design is fundamentally incompatible with centralized monetary control, or the short-term political upside of appearing pro-crypto is blinding them to the long-term structural threat. This predator is feeding the thing that eats it. Microsoft fought Linux for fifteen years before capitulating. The state seems to be skipping straight to capitulation without understanding what it's capitulating to.

What Satoshi Learned

I think this is the part most people miss. Satoshi didn't just draw on the same open-source philosophy that powered Linux. Satoshi appears to have studied Linux's specific vulnerabilities and designed around them.

The SCO lawsuit is the clearest example. In 2003, The SCO Group sued IBM for $5 billion, claiming that Unix code had been improperly placed in Linux. The case dragged on for years. Linus was subpoenaed. Corporate legal departments were rattled. The whole campaign was possible because there were identifiable targets: a named creator, an employer, organizations with assets that could be seized.

Satoshi watched this play out. The Bitcoin whitepaper arrived in 2008, right as the SCO saga was winding down. And the design choices reflect the lesson. Satoshi is pseudonymous and vanished in 2011. No foundation owns the protocol. No employer can be subpoenaed. No throat to choke.

The caution was proportional to the threat. Linux threatened software licensing revenue. Bitcoin threatens monetary sovereignty. One upset companies with lawyers. The other upsets governments with armies. The level of force that can be brought against you scales with what you're threatening, and there is nothing on earth that institutions will fight harder to control than money.

The Rhymes Are Already Here

I used to think of these parallels as a framework for speculation. Then I looked at 2026 and realized the rhymes aren't predictions anymore. They're headlines.

BIP-110 proposed limiting arbitrary data in Bitcoin blocks, an anti-spam measure targeting Ordinals inscriptions. Michael Saylor publicly called it "a bad idea." The proposal attempted to activate, mined two blocks, and died. This is Bitcoin's systemd moment, the Linux community's most vicious internal fight mapped onto a new protocol. A technically defensible proposal that split the community, generated intense controversy, and failed because it couldn't achieve near-universal consensus. The immune system worked. It was ugly, but it worked.

In July 2026, a bug in Coldcard's entropy generation led to $116 million in stolen Bitcoin. The flaw had gone unnoticed for years in the code that generated the random numbers protecting people's wallets. 594 BTC were swept in 25 minutes. The pattern is identical to what Linux went through with Heartbleed in 2014: critical infrastructure, a subtle bug sitting in plain sight, maintained by a small team, and the world trusting it with enormous value without scrutinizing the foundations.

The immediate response to the Coldcard exploit was telling. Articles started appearing about how the hack would push people toward ETFs, toward custodians, toward institutions. Because when self-custody fails, there's nobody to blame, nobody to sue, nobody's insurance to claim against. The same instinct that made my hosting client say "nothing but Microsoft in-house" is the instinct that makes a corporate treasurer say "we'll hold Bitcoin through BlackRock, not in our own wallet." The security blanket of someone to blame doesn't go away just because the technology changes.

And underneath all of this, the dollar's share of global reserves has dropped to its lowest since 1994. Every historical reserve currency has eventually lost that status. The Dutch guilder, the British pound. The transition period is when alternatives become available.

How the Transition Actually Works

Everyone who draws the internet parallel to Bitcoin imagines sudden adoption, some tipping point where the whole world switches over. The open source parallel tells a different story, and I think a more accurate one.

Proprietary software didn't vanish when open source won. What happened was subtler. Open source became the default for new infrastructure. Nobody building a new web service in 2010 started with a proprietary operating system. The old stuff kept running, maintained by inertia and switching costs, but everything new grew on open source soil. The installed base of proprietary software didn't have to die. It just stopped growing, and eventually it was the legacy system in a world that had moved on.

If the dollar follows that pattern, it doesn't collapse overnight. It keeps running on inertia, on existing contracts, on the sheer weight of institutional habit. But new arrangements, new trade relationships, new reserves, new savings, they increasingly grow on different soil. And one day people look up and realize the dollar is the proprietary system in a world that defaulted to something else, the way people looked up around 2015 and realized that Linux was running everything new and Windows was running everything old.

I watched that transition from inside corporate IT. I sat in meetings where the engineers knew open source was better but the executives wouldn't authorize it. I saw skunkworks projects running Linux in server closets. A gradual shift from "we don't use that" to "we use it but don't talk about it" to "of course we use it." That same transition is happening right now with Bitcoin in corporate treasuries and sovereign wealth funds. Analysts know. Technical people know. The political leadership isn't ready to say it out loud yet.

I've seen this movie before. I know how it ends.

The Dog That Didn't Bark

The most important thing about Linux's 35-year history might be what didn't happen. No one ever took control of it. IBM invested a billion dollars and couldn't. Microsoft joined the Foundation as a platinum member and couldn't. Governments deployed it across their infrastructure and couldn't. The GPL and the maintainer structure prevented capture every time.

If Bitcoin's physics-based moat holds the same way, the story 35 years from now won't be about what Bitcoin did. It will be about what no one was able to do TO it. The most significant fact about Bitcoin in 2043 might be how it serves as a basis for a stable dollar ,the same way the most significant fact about Linux today might be the list of companies that tried to own it and share in its prosperity.

One Pattern, Two Speeds

Linux took 35 years to go from a bedroom in Helsinki to the surface of Mars. It moved at software speed, which is fast but still depends on human organizations choosing to deploy it.

Bitcoin is running the same playbook at monetary speed. Financial incentives accelerate adoption. Regulatory resistance creates friction. The forces are larger and the consequences less forgiving. The strategic reserve, the governance crisis, the Coldcard exploit: they aren't happening sequentially over decades. They're stacking on top of each other in 2026, simultaneously, while the world's reserve currency weakens underneath them.

The Linux story ended with a line from Linus's original post: "Just a hobby. Won't be big." Satoshi's version of that understatement was a nine-page PDF. Both were technically accurate at the moment they were written. And both turned out to be among the most spectacularly wrong predictions ever committed to text.

The gap between what something IS at launch and what it BECOMES when strangers keep showing up to improve it. That's the pattern. And nothing I see in 2026 suggests it's finished playing out.