Who is Nick Szabo? Smart contract pioneer and bit gold designer

Nick Szabo is an American computer scientist and legal scholar who in the 1990s formulated the concept of the smart contract, a computerized protocol that executes the terms of a contract. In 1998 he described bit gold, a design for digital money based on proofs of work and a distributed property title registry, which is often cited among Bitcoin's precursors.

Szabo did not found a blockchain network or a widely known company. His influence comes from his essays, which combine cryptography, contract law and economic history, and from the way others applied them later. Satoshi Nakamoto mentioned bit gold in 2010 among the proposals Bitcoin put into practice, and since then Szabo has repeatedly been named as Bitcoin's possible author, which he has denied.

Education and career

Szabo graduated in computer science from the University of Washington in 1989, according to the university's computer science department. The profile on his blog, Unenumerated, added in 2006 that he held a law degree (Juris Doctor) from George Washington University and had experience in internet security, e-commerce and software engineering.

In the 1990s he took part in the debates of the cypherpunks, programmers and cryptographers who discussed how encryption could protect privacy and transactions on computer networks. He was closely familiar with the electronic cash of DigiCash, David Chaum's company, and, as he told IEEE Spectrum, he rejected a model that left oversight of the currency to banks. Sources disagree on the extent of his professional relationship with DigiCash, and this profile does not detail it.

The smart contract idea

In an essay dated 1994, Szabo defined a smart contract as "a computerized transaction protocol that executes the terms of a contract." The idea was to move into programs and cryptographic protocols some of the clauses that normally depend on the parties' good faith or on a court: payment conditions, collateral, deadlines or access rights.

His best-known development of the idea is "Formalizing and Securing Relationships on Public Networks", published in the journal First Monday in September 1997. There he presented the vending machine as a primitive ancestor of the smart contract: it accepts coins, dispenses the product and change, and its security mechanisms protect the money and goods well enough to make deploying it profitable. Anyone with coins can take part in that agreement. The essay sets out three design objectives taken from law. Observability lets each party check that the other is performing; verifiability lets a party prove to a third party that the contract has been performed or breached; and privity distributes knowledge and control of the contract's contents only to those who need them.

When Szabo wrote these texts, no public network could execute such code. The definition was later applied to smart contracts on networks such as Ethereum, where a program deployed on-chain changes its state according to rules that every node checks. The match is not complete: a smart contract today executes software rules, but it does not by itself establish whether those rules reflect a legally valid agreement.

Bit gold: scarce money on the internet

Szabo also asked how to create a scarce good on the internet that did not depend on trusting an issuer. In Shelling Out, a 2002 essay on the origins of money, he argued that shells, beads and other collectibles served to store and transfer wealth because they were durable and hard to counterfeit. Bit gold aimed to reproduce those properties. As he told IEEE Spectrum, he was trying to mimic in cyberspace the security and trust characteristics of gold.

The mechanism, described on his blog, combines several pieces. A participant solves a computational puzzle derived from a public string, so the result demonstrates a computing cost. That result is timestamped by several independent services and recorded in a distributed property title registry, which Szabo had described in 1998 in Secure Property Titles. Each new string becomes the starting point for the next, and ownership is established through digital signatures.

The bit gold blog post has a permanent address from December 2005, although the page displays 27 December 2008 as its date. That discrepancy has been used in speculation about Bitcoin's authorship, without proving anything on its own.

The link with Bitcoin

Bit gold was never implemented as a complete system. Hal Finney built a variant in 2004 with RPOW, which Szabo mentions in his post, but it depended on a server. Bitcoin solved the problem bit gold left open: how many participants can agree on a single transaction history without a central registry.

The Bitcoin white paper does not cite bit gold, though it does cite b-money, Wei Dai's proposal. In July 2010, Satoshi Nakamoto wrote on the Bitcoin forum that the system was an implementation of b-money and Nick Szabo's Bitgold proposal. The profiles of Satoshi Nakamoto and Hal Finney complete that story.

Is Nick Szabo Satoshi Nakamoto?

The closeness between bit gold and Bitcoin has led several writers to suggest that Szabo is Satoshi. In 2014, author Dominic Frisby argued it in a book based on circumstantial evidence, and in 2015 The New York Times published an article in which Nathaniel Popper described the parallels with Szabo as the most convincing he had found.

Szabo has denied it publicly and privately. In 2014 he replied to Frisby that he was wrong to identify him as Satoshi and that he was used to it. None of those investigations provides conclusive proof, and this profile takes no side. What is documented is his work: the essays on smart contracts, bit gold and the origins of money that Bitcoin and Ethereum made more relevant.

Current situation

As of 31 October 2026, the sources consulted attribute no executive role in a blockchain project to Szabo. His work remains available on his blog and in archives such as the Satoshi Nakamoto Institute, which preserves his 1990s essays alongside those of other Bitcoin precursors.

Nick Szabo's contribution

Szabo gave a name and a structure to an idea that now underpins much of the industry: that the rules of an agreement can be written as software and executed without depending, at every step, on the parties' goodwill. His merit was not only coining the term but analyzing which properties a contract needs to work on a public network, using criteria drawn from law as well as engineering.

His essays also pointed to the limits. The 1997 paper warned that time, the user interface and the completeness of the specification shape what cryptography can protect. A smart contract does not interpret intentions or fix a poorly framed agreement; it executes what has been written. That is why smart contract development starts by defining each contract's operations, permissions and conditions precisely before writing code, a requirement already present in those texts.