Nick Szabo

Nick Szabo is an American computer scientist and legal scholar who coined the term "smart contract" in the 1990s and designed bit gold, the closest documented precursor to Bitcoin. He never launched a currency, never ran a company that shipped one, and has no token to his name. He is nonetheless one of the most cited figures in the field, because almost every argument crypto makes for itself was first made precisely by him.

"Trusted third parties are security holes." - Nick Szabo

Smart Contracts, and What He Actually Meant

Szabo introduced "smart contract" in 1994 and developed it through the mid-1990s, and the term has since drifted a long way from his definition.

He was not describing code on a blockchain. He was describing any mechanism that embeds contractual terms into hardware or software so thoroughly that breaching them becomes impractical rather than merely illegal. His favourite example was a vending machine: it holds a small amount of value, enforces the bargain mechanically, and resists tampering well enough that no court needs to be involved in a one-dollar transaction. A car loan that disables the ignition on default was another.

The insight was legal as much as technical. Contract enforcement has a fixed cost, and below some transaction value that cost exceeds what is at stake, so vast categories of agreement simply never get made. Mechanical enforcement lowers the floor. That is a different and more precise claim than "contracts on a blockchain are better," and it explains why he cared about the idea a decade before a platform existed to implement it generally.

When Ethereum arrived in 2015 it gave the concept a general-purpose execution environment, and the industry adopted his vocabulary wholesale. Szabo has periodically noted that much of what gets called a smart contract is neither smart nor a contract, which remains fair.

Bit Gold: The Blueprint, Missing One Piece

Between 1998 and 2005 Szabo worked out bit gold, and reading it after Bitcoin is uncanny.

Bit gold proposed solving computational puzzles, timestamping each solution, and cryptographically chaining it to the next, so the chain itself recorded the work done. Value came from what he called unforgeable costliness: the asset is expensive to produce and cheap to verify, which is the property that made gold money for millennia and that proof of work reproduces digitally. The puzzle, the chain, the timestamps and the scarcity argument are all there.

What bit gold lacked was a way to make a distributed network agree on which chain was the real one. Szabo proposed a Byzantine quorum of servers, and the problem is that quorum membership has to be decided by someone. Satoshi Nakamoto's contribution was to replace that with the longest-chain rule weighted by accumulated work, so agreement emerges from the same mechanism that creates the scarcity. That is the difference between a design and a working currency, and Szabo has been candid about it.

Why Trusted Third Parties Are Security Holes

His 2001 essay of that title is the most quoted thing he wrote, and it is more rigorous than the slogan suggests.

The argument is that a trusted intermediary is not merely an inconvenience but a structural vulnerability, because it concentrates risk at a point the parties to a transaction cannot inspect or control. Trust has to be paid for, in due diligence, insurance, regulation and audit, and those costs are borne by everyone including the honest. Worse, the intermediary becomes the cheapest thing for an attacker to compromise, which means security spending flows to protecting the middleman rather than the transaction.

Every exchange failure since has been a demonstration. The people who lost money at Mt. Gox, at Celsius and at FTX were not defeated by cryptography. They were defeated by having trusted a third party with custody. This is the intellectual root of the advice to understand how to store crypto yourself, and of why crypto scams almost always work by inserting a trusted-looking intermediary.

Social Scalability

His later framework, developed most fully in a 2017 essay, is the one most worth knowing and the least understood.

Szabo argued that the meaningful limit on an institution is not how many transactions it can process but how many people can participate in it without knowing or trusting each other. Traditional finance achieves scale through hierarchy: courts, regulators, correspondent banks, each layer vouching for the one below. That works, and it excludes anyone the hierarchy declines to serve.

Bitcoin trades computational efficiency for social scalability. It is spectacularly wasteful compared with a database, and that waste buys the ability for strangers under different governments with no shared legal system to transact without a common authority. Judged as a payment system it looks absurd. Judged as a mechanism for extending an institution across jurisdictions that do not trust each other, the cost is the point.

This reframing answers the standard efficiency objection more effectively than most of what the industry says on its own behalf, and it applies well beyond currency into Web3 and DeFi claims that rarely examine whether they need social scalability at all.

The Satoshi Question

Szabo is a perennial candidate for Satoshi Nakamoto, and the reasons are not frivolous. Bit gold anticipates Bitcoin's structure more closely than any other prior design. Stylometric comparisons of his writing against the whitepaper have returned similarities. He had the cryptographic knowledge, the legal framing and the motive.

He has consistently and unambiguously denied it. He has also pointed out, reasonably, that he would have cited bit gold in the whitepaper had he written it, and that his own public reaction to Bitcoin read as a man encountering someone else's solution to a problem he had failed to solve.

No evidence has established Satoshi's identity, and the speculation persists mainly because the resemblance is genuine. What actually settles such claims is a cryptographic signature from the early coins, which nobody has ever produced. The Satoshi Nakamoto question remains open, and Szabo's denial is as credible as anyone's.

Why a Theorist Who Shipped Nothing Still Matters

Szabo built no product, holds no notable public position, and has been comparatively quiet in recent years, with no confirmed operational role at any major crypto project. By the industry's usual scoreboard he barely registers.

By a more durable measure he supplied the conceptual apparatus. The vocabulary that Vitalik Buterin and the Ethereum researchers use to describe programmable agreements is his. The argument for why trust-minimisation is worth its enormous costs is his. The framing of digital scarcity as unforgeable costliness is his. When a protocol designer asks whether a system actually needs to be decentralised or is merely expensive, that is a Szabo question.

His unusual value is that he thought about the legal and social mechanics before the technology existed, which is why the ideas have aged better than most implementations built on them. He also offers a useful corrective: the point of these systems was never speed or returns. It was removing the need to trust institutions that had proven untrustworthy, and every design decision that quietly reintroduces a trusted third party gives that away.