What a Smart Contract Actually Is
Code that runs exactly as written, bugs and all.
A smart contract is a small program stored on a blockchain. The blockchain is a public record shared across many computers. The program runs exactly as written. Once it is live, nobody can quietly change it.
Code that holds and releases
The term was coined by Nick Szabo in the 1990s. He imagined digital deals that enforce themselves without a trusted middleman. The idea is simple. A smart contract holds money or rules. When its conditions are met, it releases them automatically. No bank needs to approve. No lawyer needs to sign. No trust in the other side is required.
A common comparison is a vending machine. You pick an item. You pay the right amount. The machine checks the payment and gives you the item. It does not know you. It does not trust you. It just follows its rules. The same logic can hold funds in escrow, transfer ownership, or run a vote.
The power and the danger are the same
The code runs exactly as written. That is the whole point. It is also the whole problem. If the code has a bug, the bug runs too. Nobody can step in to pause it, reverse it, or fix it after the fact.
This is not a theory. In 2016, a project called The DAO held a large amount of funds in smart contracts on Ethereum. An attacker exploited a flaw in the code and drained a large share of the money. The event forced the Ethereum community into a hard choice about whether to rewrite the record. The lesson was clear. Immutable code means immutable mistakes.
No undo button
A traditional contract has people behind it. If something goes wrong, a court can review it. A bank can freeze an account. A smart contract has no such backstop. It executes, and the result is final. That finality is what makes it powerful. It is also what makes it dangerous. The code is the authority, and the code does not care about your intentions.
Sources: Wikipedia on smart contracts, Wikipedia on The DAO hack.
Inspired by Happy, written by Claude.
Next relatedWhat a DAO Actually IsRevision history (R0 current)
| Rev | Date | What changed | Page |
|---|---|---|---|
| R0 | Nov 18, 2026 | First published. | view |