Hashcash creator and one of the most respected developers in the Bitcoin community, Adam Back, published a short post that he jokingly called the "E=mc² formula for Bitcoin." Within just a few hours, the post garnered tens of thousands of views and sparked a wave of analysis in the comments. This is no surprise: Back managed to capture the entire essence of the system in a single line, much like Einstein's famous equation describes the relationship between energy and matter.
The Three Pillars of Bitcoin
To understand the formula, you don't need to be a mathematician—just imagine the three pillars on which Bitcoin rests.
- Computational Work (Proof-of-Work). To add a new record to the network, computers around the world must solve a complex numerical problem through brute force. This is intentionally costly: it's impossible to falsify history retroactively because you would have to redo all the work.
- Chain of Blocks (Blockchain). Records in Bitcoin are not scattered; they are linked together: each new block references the previous one. This creates a single, continuous chain that cannot be secretly rewritten in the middle.
- Scheduled Coin Issuance. New bitcoins appear as a reward to whoever adds the next block. The reward amount is predetermined and halves every four years—an event known as the halving. Thus, the total number of coins grows according to a predictable schedule set from the very beginning.
The genius of Back's formula lies in condensing these three pillars into a single line.
What the Formula Says
The post itself looks like this:
c | { h_(i+1) = H(h_i, c, 50/2^h ₿) } < T
Each symbol represents one of the pillars mentioned above.
The letter H is a data "shredder," or hash function. It transforms any set of information into a fixed-length string. h_i and h_(i+1) are the previous and next blocks; the fact that one references the other is the chain itself. The letter c denotes a new block template with a list of transactions.
The fraction 50/2^h ₿ is the coin issuance schedule: 50 bitcoins at the start, and each halving divides the reward in half. Finally, T is the difficulty target: the computation result must be less than this value, otherwise the block won't be accepted. The entire line reads as a condition: "find such a block template that the result falls below the target."
An important caveat, which Back himself makes, is that the formula is conceptual, not literal. In real mining, the reward doesn't enter the computation directly but indirectly—through a special coinbase transaction that is folded together with the others into the block's overall "fingerprint." Back omitted these technical layers for elegance and brevity: the line conveys the logic, not the exact sequence of machine operations.
Where the Roots Come From
This formula has a backstory spanning a quarter of a century. Back in the late 1990s, Back invented Hashcash—a system to combat spam. The idea was to force the sender of an email to perform a small amount of computational work. For a single email, this is negligible, but for a million-piece spam campaign, it becomes prohibitively expensive.
It is this very technique—"prove you did work" (Proof-of-Work)—that later became the foundation of Bitcoin. However, Hashcash had neither a chain of blocks nor rewards for work. Bitcoin's creator under the pseudonym Satoshi Nakamoto took Back's idea and built the missing pieces: linking records into a chain and adding a schedule for coin issuance. Therefore, the essence is often described with a simple scheme: work plus chain plus economics equals Bitcoin.
Community Reaction
Under the post, one user shared a detailed infographic that broke down the formula into parts and visually compared Hashcash with Bitcoin. Back publicly praised this analysis.
The episode is notable not for a new discovery, but for a successful attempt to distill Bitcoin's foundation into a single memorable line—understandable to both an engineer and someone without a technical background.
Analyst's Comment: Such "elegant" formulations are a sign of technological maturity. Bitcoin has ceased to be just code for geeks; it is becoming a cultural and engineering artifact that can be explained in a single line. This indicates that we are moving toward mass understanding, not just mass adoption.