Nick Szabo
Computer scientist who described smart contracts and bit gold
Born 1964
Wrote about self-executing digital agreements and proposed bit gold, a scarce digital money design that predates Bitcoin.
Biography
Nick Szabo is a computer scientist, legal scholar and cryptographer whose writing in the 1990s laid out several of the ideas that Bitcoin later put into practice. He studied computer science at the University of Washington and subsequently trained in law, and much of his work sits at the point where the two subjects meet: what a contract is, what enforcement costs, and what a computer can do about either.
In the mid-1990s he described what he called smart contracts: agreements written so that their terms are carried out automatically by the systems involved, rather than relying on a court to enforce them afterwards. His standard illustration was mundane rather than financial, a vending machine, which takes payment and releases goods without any party needing to trust the other.
He also wrote about the cost of trust itself. His essay arguing that trusted third parties are security holes made the case that every institution inserted into a transaction to guarantee it becomes a target, a point of failure and a cost, and that the right engineering response is to remove the need for it rather than to secure it better.
In 1998 he proposed bit gold, a design for digital money whose scarcity would come from the computational cost of producing it rather than from an issuer's promise. Bit gold was never implemented, but its combination of proof of work, chained records and unforgeable costliness is close enough to Bitcoin's design that it is now read as its most direct predecessor. Szabo has been the subject of persistent speculation that he is Satoshi Nakamoto, which he has denied.
Career timeline
- 1989Completes a computer science degree at the University of Washington.
- 1994Describes smart contracts, agreements whose terms are executed automatically.
- 1990sWorks on digital cash systems and takes part in the cypherpunk discussions of the period.
- 1998Proposes bit gold, a design for digital money based on unforgeable computational cost.
- 2001Publishes his essay arguing that trusted third parties are security holes.
- 2005Publishes a full public description of bit gold on his blog.
- 2008Bitcoin's white paper appears, implementing several ideas his work had described.
Design philosophy
Szabo approaches money and contracts as engineering problems with legal history attached. His question is not whether an institution can be trusted but what it costs to have to trust it at all, counting the auditing, the regulation, the insurance and the failures. Once that cost is visible, removing the need for trust becomes a design goal rather than an ideological position.
His concept of unforgeable costliness explains why he thought scarcity could be engineered. Gold is valuable partly because it is expensive to find and refine, and that cost cannot be faked. Bit gold applied the same logic to computation: if producing a unit requires provable work, its scarcity does not depend on anyone promising to limit supply.
He is unusual among technologists in treating legal and institutional history as evidence rather than as an obstacle. Much of his writing examines how earlier societies solved settlement, collateral and record-keeping problems, on the argument that a protocol designer who does not know why the old institutions took the shape they did will rebuild their failures in software.
Key ideas
Tap any idea to expand a plain-English explanation, why it matters, and where to learn more.
Smart contracts
Agreements written so that their terms are executed automatically by the system itself, rather than enforced afterwards by a court.
It moves enforcement from an expensive, slow, after-the-fact process into the mechanics of the transaction, which changes what kinds of agreement are worth making at all.
His own illustration was a vending machine: it takes the money and releases the item without either party needing to trust the other.
Trusted third parties are security holes
The argument that every intermediary added to guarantee a transaction becomes a target, a single point of failure and a permanent cost.
It reframes trust as an expense to be engineered away rather than a service to be purchased, which is the reasoning behind most decentralised system design.
A payment processor holding customer records is a convenience for users and, at the same time, the most valuable thing for an attacker to breach.
Bit gold
A 1998 design for digital money whose units would be created through provable computational work and chained together in a public record.
It is the closest documented predecessor to Bitcoin, and it shows that the core ideas existed a decade before a working implementation did.
Bit gold was never built, which is itself the point: a design is not a system until someone runs it.
Unforgeable costliness
The idea that something can be scarce because producing it demonstrably costs resources, rather than because an issuer promises to limit it.
It explains why proof of work exists. Scarcity enforced by physics and arithmetic does not depend on anyone keeping a promise.
Gold has historically been valued partly because finding and refining it is expensive in a way that cannot be faked.
Learn from institutional history
Studying how earlier societies handled settlement, collateral and records before designing a protocol to replace them.
Institutions usually took their shape for reasons. A designer unaware of those reasons tends to rediscover the same failures in code.
Much of his writing examines historical forms of money and contract enforcement rather than contemporary technology.
Major contributions
- Introduced and defined the concept of smart contracts, which is now the standard term for automatically executing agreements.
- Argued that trusted third parties are structural security weaknesses, a framing that underpins most decentralised system design.
- Designed bit gold, the closest documented predecessor to Bitcoin, a decade before a working implementation existed.
- Developed the idea of unforgeable costliness, connecting the economics of scarce commodities to proof-of-work systems.
- Wrote extensively on the history of money and contract enforcement, giving protocol designers a body of institutional evidence to work from.
Major successes
- Coined the term smart contract in the 1990s, decades before the technology to run one at scale existed.
- Published the bit gold design, which is now routinely cited as the most direct conceptual predecessor to Bitcoin.
- Wrote the essay on trusted third parties that remains one of the most quoted texts in decentralised system design.
- Built a long-running body of public writing connecting cryptography, economics and legal history for a technical audience.
Influence on investors
Szabo supplied much of the vocabulary that Bitcoin and later systems are discussed in. Smart contracts, trust minimisation and unforgeable costliness were his terms before they were anyone else's, and they now appear in documentation and regulation written by people who have never read the originals.
His influence on Ethereum is especially direct, since the entire platform is organised around the idea he named. It is also a fair illustration of the gap between concept and implementation: what Ethereum built is recognisably his idea and, at the same time, not quite what he described.
Criticisms and debates
A balanced view includes the main criticisms and open debates, presented neutrally.
- Bit gold was never implemented, and the distance between a design and a working network is exactly where most of the difficulty in the field turns out to live.
- Smart contracts in practice have produced repeated and expensive security failures, because code that executes automatically also executes its own bugs automatically.
- The term smart contract is now used loosely for almost any program on a blockchain, which has drained it of the precision his original definition had.
- His writing assumes fluency in cryptography, economics and legal history at once, which puts most of it out of reach for general readers.
- Removing trusted intermediaries also removes their remedies: an irreversible transaction has no mechanism for reversing a mistake or a theft.
Lessons for investors
Plain-English takeaways. Context for learning, not advice to buy or sell anything.
- 1Trust is not free, and the cost of an intermediary is paid whether or not anything goes wrong.
- 2A design is not a system until somebody runs it and it survives contact with real users.
- 3Scarcity backed by demonstrable cost does not depend on anyone keeping a promise.
- 4Code that executes automatically executes its mistakes just as reliably as its intentions.
Notable quotes
“Trusted third parties are security holes.”
Context: A security argument: any party you are required to trust is a party that can fail or be compromised.
“A smart contract is a set of promises specified in digital form, including protocols within which the parties perform on these promises.”
Context: Szabo's original definition, written years before any blockchain existed to run one.
“Precious metals and collectibles have an unforgeable scarcity due to the costliness of their creation.”
Context: Szabo's idea of unforgeable costliness: something stays scarce because it is expensive to produce. Bitcoin later engineered the same property.
Frequently asked questions
Who is Nick Szabo?
Nick Szabo is a computer scientist, legal scholar and cryptographer known for describing smart contracts in the 1990s and for designing bit gold, a proposal for digital money that predates Bitcoin.
What is a smart contract?
It is an agreement written so that its terms are carried out automatically by the system running it, rather than depending on a court or an intermediary to enforce them afterwards.
What was bit gold?
Bit gold was a 1998 design for digital money in which units are created through provable computational work and linked in a public record. It was never implemented, but it anticipates much of Bitcoin's structure.
Why did Szabo say trusted third parties are security holes?
Because any intermediary added to guarantee a transaction becomes a concentration of value and a single point of failure, with costs in auditing, regulation and breaches that users pay for whether or not anything goes wrong.
Is Nick Szabo Satoshi Nakamoto?
There has been persistent speculation, based on the similarity between bit gold and Bitcoin and on writing style comparisons. Szabo has denied it, and no evidence has ever established the identity of Satoshi Nakamoto.
What is unforgeable costliness?
It is his term for value that comes from something being demonstrably expensive to produce. Gold is scarce because mining it costs real resources, and proof-of-work systems try to reproduce that property digitally.
What did Szabo write about the origins of money?
In an essay called Shelling Out he argued that collectibles such as shells and beads worked as early money because they were hard to produce, easy to carry and easy to verify. He used that history to explain what a digital equivalent would need to have.
Related quotes
Other people in the library writing on the same themes.
“A purely peer-to-peer version of electronic cash would allow online payments to be sent directly from one party to another without going through a financial institution.”
Satoshi Nakamoto“Running bitcoin.”
Hal Finney“Hashcash was designed to make sending a message cost the sender a small amount of computation.”
Adam BackRelated guides
Related concepts
Related tools
Related people
Get smarter about investing
Clear market insights, useful tools, and beginner-friendly investing education.
Educational content only. This is a neutral summary compiled for learning. It is not an endorsement, not investment advice, and not a claim that this person is always right. Mentioning someone here does not imply they are affiliated with Money Masters Media.