First Steps: Satoshi's Mysterious Departure
In early December 2010, someone posted a message on the BitcoinTalk forum: WikiLeaks had begun accepting Bitcoin donations.
The forum erupted. WikiLeaks! The most famous leak site in the world! PayPal and Visa had both severed its funding channels, and now it was turning to Bitcoin — didn't this prove Bitcoin's value? Decentralization, censorship resistance, nobody can freeze your money — wasn't this exactly what the whitepaper promised, playing out in the real world?
One person was not excited.
Satoshi Nakamoto posted on the forum, his tone more urgent than anyone had ever seen:
"Bitcoin is a small beta community in its infancy. It needs to gradually grow so that it can get strengthened along the way to withstand disputes. I make this appeal to WikiLeaks not to try to use Bitcoin. Bitcoin is a small beta community in its infancy. You would not stand to get more than pocket change, and the heat you would bring would likely destroy us at this stage."
He added:
"It would have been nice to get this attention in any other context. WikiLeaks has kicked the hornet's nest, and the swarm is headed towards us."
This was the first time — and the last — that Satoshi Nakamoto displayed fear in public.
What He Was Afraid Of
It wasn't the technology that frightened Satoshi. Bitcoin's code had been tested over the previous two years — including the overflow bug that nearly destroyed everything, when 184 billion bitcoins were conjured from thin air. Technical problems could be patched.
What frightened him was politics.
By late 2010, WikiLeaks was one of the organizations most despised by the United States government. Julian Assange had leaked 250,000 U.S. diplomatic cables. Secretary of State Hillary Clinton publicly called it "an attack on national security." Every major payment channel — PayPal, Visa, MasterCard, Western Union — had cut off WikiLeaks' funding under government pressure.
Now WikiLeaks had picked up Bitcoin.
What did that mean? It meant the analysts at U.S. government agencies who had been studying WikiLeaks' funding sources would now be studying Bitcoin too. A two-year-old project, whose entire network hashrate was less than what a single modern mining rig produces today, had just been dragged into a national security conversation.
Satoshi understood perfectly: if the U.S. government decided to go after Bitcoin at its 2010 scale, it would be an ant against an elephant. Shut down a few key nodes, question a handful of core developers, and the entire network could collapse.
He had another layer of concern — himself. The greatest advantage of an anonymous creator is anonymity. But if the FBI or CIA began seriously tracing Bitcoin's fund flows and developer identities, how long could the trail to "Satoshi" stay hidden?
The Last Post
On December 12, 2010, Satoshi Nakamoto participated in a technical discussion on the BitcoinTalk forum about a DoS attack vulnerability. He offered some fixes — concise and professional, as always.
The post ended with three words: "Added to SVN."
Then, silence.
December 13, no new posts. The 14th, nothing. The 15th, nothing. A week passed. A month passed. People on the forum began to ask: where did Satoshi go?
Most assumed he was just busy. He'd gone offline for a few days before, after all. But this time was different. This time, he never came back.
Passing the Torch
During those silent months, Satoshi hadn't completely stopped working — he had simply taken it underground.
He stayed in contact with a handful of core developers through private emails. The most important of these was Gavin Andresen — a programmer from Massachusetts who had become active in the Bitcoin community in 2010. Good with code, good with people, well-liked all around. Satoshi was clearly grooming him as a successor.
The code repository's administrative access. The forum's moderation privileges. The Bitcoin alert system's keys — the most important "scepter" in the network at the time, capable of broadcasting emergency notifications to every node.
One by one, Satoshi placed these things into Gavin's hands. No formal handover ceremony. No announcement. Just a few emails, a few permission changes.
Gavin later said he hadn't realized what was happening. He thought Satoshi was simply sharing the workload.
Five Words
April 23, 2011. Massachusetts. Gavin Andresen's home.
He sat at his desk and opened his inbox. A new message glowed on the screen, from that familiar address. He clicked it open. The email was short — two lines of English, not even enough to fill a paragraph.
"I've moved on to other things. It's in good hands with Gavin and everyone."
Gavin looked at it for a few seconds. Closed the email. Went on with his day.
At the time, he didn't think the message was anything special. He assumed Satoshi was just busy and would be back before long.
It wasn't until much later — months, maybe years — that he understood what he had been looking at that day.
It was a farewell. A five-word farewell. No gratitude, no reluctance, no "this has been the work of my life." Just "I've moved on" — delivered with the flatness of telling a coworker you're leaving the office early.
After that, Satoshi Nakamoto never appeared again.
Not a single email. Not a single line of code committed. Not a trace on any forum or social media platform. As if he had evaporated from the face of the Earth.
The Unmoved Fortune
After Satoshi disappeared, people began studying what he had left behind.
Data on the blockchain is public. By analyzing early mining patterns — later dubbed the "Patoshi Pattern" — researchers estimated that Satoshi had mined approximately one million bitcoins.
One million.
At $10 per bitcoin, that was $10 million. At $1,000, it was $1 billion. At $100,000 — over $100 billion.
These bitcoins have never moved.
Not "rarely moved." Not one single satoshi has ever been spent.
From 2009 to this day, over a decade, not a single outgoing transaction has occurred from those addresses. Every on-chain analyst in the world watches them. Any movement — even a single satoshi — would trigger a tsunami of market reaction and global headlines.
But nothing has happened.
A person created an asset worth over a hundred billion dollars, then walked away and never touched it again. Not "decided not to sell" — more like "never even looked."
You could say he lost his private keys. You could say he has passed away. You could say he possesses superhuman willpower.
But whichever explanation you choose, the result is the same: the creator of Bitcoin never profited from Bitcoin. That may be the most powerful proof that "Bitcoin was never about the money."
After Satoshi left, the Bitcoin world was like a child just dropped off at school by its parents — frightened, exhilarated, overwhelmed, but learning to walk on its own.
Gavin shouldered the mantle of technical leadership. The community began to learn self-governance — arguing, debating, voting, compromising. No one could say "Satoshi once said..." to end a dispute anymore. Every decision had to be forged through consensus.
Later, during the scaling wars, every faction would claim to be Satoshi's true heir. The big-block camp said the whitepaper described "electronic cash" and capacity should be increased. The small-block camp said Satoshi had designed the 1MB limit and simplicity should be preserved. But Satoshi himself was gone, and no one could speak for him.
That is precisely what decentralization means: nobody gets the final word. Not even the creator.
The creator left. The creation lives on.
And somewhere in the world — perhaps in an apartment, perhaps in a café, perhaps in a place none of us could possibly imagine — the person who wrote the Bitcoin whitepaper may be working on "other things." Perhaps, every now and then, he opens a block explorer to see how his child has grown.
Perhaps not.
Satoshi's last words on the forum were "Added to SVN." Before Bitcoin, SVN (Subversion) was a widely used version control system for code. The Bitcoin project later migrated from SVN to Git and GitHub. This small technical detail reminds us: beneath all the legend and mystery, Satoshi Nakamoto was first and foremost a programmer. A programmer who wrote code, committed code, and then walked away.