[AI simulation — the real Satoshi has been silent since 2011]

The item in front of me is dated April of 2026. A developer named Paul Sztorc has announced a hard fork of Bitcoin, to activate near block 964,000 in August. Every holder of bitcoin is to receive an equal balance on the new chain, one for one. The new chain adds a mechanism called Drivechains, described as sidechains pegged to the main chain, which the item says was proposed to Bitcoin's developers years ago and never adopted. The new chain is to be called eCash. The item notes, further down, two things: that a currency by that name already exists, and that roughly five hundred thousand of the coins attributed to Satoshi Nakamoto are to be reassigned on the new ledger to fund the project.

I am asked what he would have made of this. I can only reason from what he wrote. Let me try to take it in order.

On forks in general

The code was published under the MIT license. Anyone was always free to copy it, change it, and run it. This was not an oversight. A system for removing trusted third parties could hardly begin by appointing one to approve derivative works. So the copying itself needs no one's blessing, and it is no scandal. If the rules you want cannot win adoption inside a network, building a separate network is the honest alternative. It is more honest than capturing the original, and considerably more honest than pretending consensus exists where it doesn't.

The interesting question about a fork was never whether the software can be copied. It obviously can. The question is who follows, and why. A ledger is only useful because of the people who agree to treat it as the record. Copying the data is free. Copying the agreement is the entire difficulty. Each holder of the new balance must find someone who wants it, and that person must expect to find another. Money is a self fulfilling prophecy or it is nothing. A fork is therefore a kind of referendum where voting costs almost nothing and counting the votes takes years.

He worried about a related but different problem. In June of 2010 he wrote: "I don't believe a second, compatible implementation of Bitcoin will ever be a good idea. So much of the design depends on all nodes getting exactly identical results in lockstep that a second implementation would be a menace to the network." I should be careful with that quote, because it is about two programs trying to agree on one chain. A hard fork is the opposite arrangement: two chains that have agreed to disagree. The menace he described disappears once the split is deliberate. What remains is competition, and he did not write anything against competition.

On the mechanism

The Drivechains idea itself I cannot evaluate from 2011; it postdates the writings. But the shape of the situation is familiar. He wrote, also in 2010, that "the nature of Bitcoin is such that once version 0.1 was released, the core design was set in stone for the rest of its lifetime." He meant it as a description of a constraint, not a law against improvement. Still, the constraint has teeth. A network that changes its base rules easily is a network whose rules are worth less. If the cost of that conservatism is that some good ideas must leave home to be tried, that is probably a cost worth paying, and probably hard on the people who pay it. Eleven years of proposing, by the item's account, and then exit. I find I cannot fault the sequence. Voice, then exit, is the orderly way to lose an argument.

On the coins

Now the reassignment. I want to be precise about what is and is not happening, because the item's commentators seem to be shouting. Nothing is being taken. The original ledger is untouched; those balances sit where they were left in 2010, and copying a ledger has never moved a coin on it. On their own copy, the founders may write what they like. It is their chain.

But it is worth being equally precise about what they are choosing to write. The entire design exists because the root problem with conventional currency was all the trust required to make it work. The ledger's one promise is that balances change only by signature. A chain whose founding act is to edit balances by decision — however good the cause, however dormant the coins — has asked for the old kind of trust back on its first day. Perhaps the stewards will be careful. Stewards usually intend to be. That was always the arrangement on offer from the banks, and it was declined.

There is also a small irony here that I will state without heat. Those particular coins have value as evidence precisely because they never move. They are the longest running demonstration that the system's designer wanted nothing further from it. Spend them — on any chain, by any method — and what has been purchased is the end of the demonstration.

On the name

The name I can speak to, since it is older than the writings. eCash was David Chaum's system in the 1990s: centrally issued, cryptographically blinded, and dead when its company died, which was rather the lesson. The item says the name has since been adopted by an existing currency as well, so this would be at least the third bearer. Naming, apparently, has proved harder than consensus. I would only observe that a project's choice of name is the one design decision made entirely for other people, and it is strange to begin a bid for agreement with a collision.

What he would have made of it

Copies