Who Is Satoshi Nakamoto?

There is no established answer to the question in the title. That is not a gap in the reporting but a property of the system. And the property matters more to a company than the name.

What is documented

In November 2008 the concept for Bitcoin was published under the pseudonym Satoshi Nakamoto. The Deutsche Bundesbank calls this a central milestone on the way towards a new, digital form of money. The paper is titled “Bitcoin: A Peer-to-Peer Electronic Cash System” and remains freely available.

The Bank for International Settlements describes the authorship in its 2018 annual report as cautiously as the facts allow: the concept was laid out in a white paper by an anonymous programmer — or group of programmers — under that pseudonym. To this day, nothing more is settled.

A note on wording in passing: the Bundesbank deliberately speaks of crypto-assets rather than currencies. A crypto-asset in that sense is the digital representation of a value or a right. It can be transferred using distributed ledger technology (DLT), and it is not a recognised means of payment like the euro.

Why the search for the name is not the subject

There have been several attributions, and none of them is established. This article therefore does not list them: a conjecture does not become more solid by being repeated.

A thought experiment matters more. Suppose authorship were settled beyond doubt tomorrow — what would change? Nothing about how the system works. Nothing about its rules. Nothing about who may decide on a change either. A named author would hold no authority over a network that belongs to no one.

That is precisely where the real subject shows. The interesting question is not who wrote the system, but who can change it today.

A system without an author still has governance

It is merely unfamiliar. Changes run through a documented proposal process, the Bitcoin Improvement Proposals. The process states expressly that no single authority decides — a proposal prevails by being demonstrably adopted.

What is notable is that the threshold depends on the kind of change. A backwards-compatible change requires a clear majority of miners. A change that is not backwards-compatible requires adoption by the entire Bitcoin economy, expressly including those selling desirable goods and services. For changes to interfaces it is enough that two independent, mutually compatible programs implement them.

This is not governance in the sense of a committee with rules of procedure. It is governance by actual adoption: whoever wants a change has to persuade enough participants to use it voluntarily. No one can order it — and no one can prevent it if enough people go along.

The price of this design is called a fork

Where no one decides, a dispute is not settled but fought out. The BIS describes the mechanism plainly: some participants coordinate on a new version of the ledger and protocol while others stay with the original. One network becomes two.

That this is not a theoretical case is shown in the same report by an incident from 2013. An incompatibility between software versions let two chains grow side by side. The situation ended because miners temporarily departed from the protocol and ignored the longest chain. That was an arrangement among participants, not the application of a rule.

For judging the system this is the most honest point. Independence from a central authority is real, and it has a price: there is no body that decides in a dispute, and none that answers for the outcome.

What a company notices

The difference shows as soon as someone needs a commitment. A mid-sized company setting up a payment route over an open network asks its provider about availability, fee development and lead time for changes. The provider can promise all of that — but only for its own service. It cannot promise it for the network, because it does not control it.

That shifts what a contract can achieve at all. It governs the relationship with the service provider, not the behaviour of the infrastructure. Anyone used to covering operational risk through availability commitments and escalation paths finds a gap here that renegotiation cannot close.

In practice this means two things. First, someone has to watch: who follows protocol changes, and who decides internally what follows from them? Second, there has to be a rule for the case of a split. Which chain counts as authoritative for internal systems, and how is a second holding arising from it treated? What a holding is in accounting terms at all is covered in Bitcoin in a Corporate Context.

What remains

The missing name is not an unsolved case but a design decision with measurable consequences. It explains why there is no issuer against whom a claim could be directed. It also explains why no one can order a change, and why a dispute ends in a split rather than a decision.

For your own assessment, then, two other questions are more useful than the one about authorship. Who could change something in this system that affects me? And how would I notice in time? Anyone with an answer to those does not need the name.