# Nick Szabo

> ~1964– · Computer Scientist, Cypherpunk
>
> **Recorded contribution:** Coined "smart contracts" (1994); Bit Gold concept (proto-Bitcoin); cypherpunk

## How to use this dossier

Read for a causal chain, not a hero story: inherited problem → contribution → mechanism → downstream capability → limit. Then close the page and complete the reconstruction exercise from memory.

## 1. Historical orientation

Nick Szabo wrote about “smart contracts” in the 1990s and proposed bit gold, a design sketch combining proof of work, timestamped records, and chained ownership. These writings influenced later cryptocurrency discourse by asking how digital agreements and scarce records might execute through protocols rather than trusted clerks. This work makes a security claim depend on an explicit adversary model, mathematical construction, key or randomness discipline, and a testable notion of success. The chronology is used causally: it connects the inherited constraint to an implementable mechanism and then to later reuse, instead of treating fame, job title, or eventual market success as the explanation.

## 2. The problem inherited

Digital exchange depended on institutions to remember ownership and enforce conditions; duplicable bits had no native scarcity, and contract terms remained separate from software execution. Secrecy, integrity, authenticity, privacy, and consensus cannot be delivered by obscurity. The protected asset and attacker capabilities must be stated before an algorithm can be judged.

## 3. The central contribution

A smart-contract system represents selected obligations as machine-verifiable state transitions; bit gold proposed costly proofs linked through public records and assigned through cryptographic ownership. The contribution is best understood as a construction plus its assumptions and proof target, not as a magic shield around data.

## 4. Reconstruct the mechanism

1. Specify the contractual state, authorized inputs, and transition conditions that code can observe. Define the parties, keys or randomness, messages, and exact security property.
2. Use signatures or keys to authorize a transition without equating key control with every legal right. Execute setup and the core transform on a toy instance small enough to inspect.
3. Record ordered state so later verifiers can detect conflicting ownership claims. Give the receiver or verifier only the information the construction permits and check the intended result.
4. Test oracle failure, bugs, coercion, governance, legal ambiguity, and concentration at interfaces or custodians. Strengthen the attacker, weaken randomness, reuse state, or change a hardness assumption and identify the resulting break.

## 5. What changed downstream

- The terminology influenced blockchain platforms, digital assets, and analysis of automated agreements and protocol-mediated institutions.
- The work supplied later protocols with a composable primitive or a sharper way to state what an attacker should be unable to do.
- The transferable first-principles lesson is to separate the artifact named in “Coined "smart contracts" (1994); Bit Gold concept (proto-Bitcoin); cypherpunk” from the mechanism, surrounding institution, and evidence that allowed later systems to depend on it.

## 6. Attribution, limits, and uncertainty

- Szabo’s birth year is approximate and public biography is limited. Bit gold was a proposal, not an operating precursor identical to Bitcoin, and no evidence establishes Szabo as Satoshi Nakamoto. “Smart contract” code cannot capture every legal context, remedy, or human intention.
- Mathematical security does not automatically secure implementations, endpoints, key custody, incentives, or institutions.
- The registry marks the birth chronology as approximate. This dossier therefore avoids inferring a precise date or age from the ordering.

## 7. Reconstruction lab

Write a state machine for an escrow contract with deposit, delivery evidence, timeout, dispute, and refund. Identify every fact the code cannot observe without an oracle or human authority. Separate the toy mathematics from production security; finish with an attack caused by violating one stated assumption.

## 8. Evidence trail

- [Smart Contracts](https://www.fon.hum.uva.nl/rob/Courses/InformationInSpeech/CDROM/Literature/LOTwinterschool2006/szabo.best.vwh.net/smart.contracts.html) — Nick Szabo archive
- [Nick Szabo](https://en.wikipedia.org/wiki/Nick_Szabo) — Wikipedia contributors · overview and bibliography
- [Nick Szabo structured identity record](https://www.wikidata.org/wiki/Q15410426) — Wikidata contributors · CC0

---

*Research checked 2026-08-09. Dates, roles, and claims about living people are historical snapshots. Linked sources remain the authority; this dossier is original instructional synthesis.*