The first smart contract: the moment tech wrote itself

Code as law is the future, or the disaster.

Somewhere around 2013, someone at a web3 hackathon in Toronto wrote the first smart contract. It was probably trivial. Two variables, some logic. Nothing complicated. But the concept was revolutionary.

A smart contract is code that executes itself. You write the rules. The blockchain executes them. No intermediary. No jurisprudence. No interpretation. Only logic.

At the time this felt like liberation. No bank holding your money. No government denying your permit. Only logic.

What nobody said is: code is just as liable to errors as language. Nick Szabo documented this years earlier, but nobody listened. Code has bugs. Code can be hacked. Code can be wrong in ways the writer didn't see.

The hackers of The DAO in 2016 proved this. DAO was a smart contract-based investment fund. A hundred million dollars. Someone found a bug. A recursion error. They pulled everything out. The code said they could. Legally it was theft. Technically it was correct.

What now? You can reverse it. But that means the blockchain is compromised. It means "immutability" means: actually mutable if you have enough power. Or you leave it. Then everyone loses billions. Both outcomes are catastrophe.

This is why I'm cautious with "code as law." Code is never law. Code is always optional. It takes power. It requires engineering. It requires consent. We'd rather have that.

But smart contracts did something important. They showed that you can decentralize transactions. You don't need to trust a bank. You don't need to trust a government. You trust the code. Under certain conditions.

In iRecord we use the same mechanics. Not smart contracts specifically. But decentralization of trust. You don't trust iRecord. You trust crypto: SHA-256 can't be hacked. You trust architecture: your biometrics never leave your phone. You trust open standards: anyone can implement this.

The question for web3 is: can it scale? Can it be secure? The answer is: not as it works now. Ethereum is slow. Bitcoin is expensive. Innovation is needed.

But the idea that you can verify yourself without a central database? That works. That will scale.

The first smart contract in Toronto was probably a joke. A test. Nobody knew what they wanted to build. But the moment code could execute itself without human intervention, that's the moment tech declared itself independent.

That moment could be liberating. Or it just feels like the Wild West right now.

Sources: Ethereum Smart Contracts documentation; Nick Szabo, 'Formalizing and Securing Relationships on Public Networks' (1997); Andreas M. Antonopoulos, 'Mastering Ethereum' (O'Reilly, 2018); DAO hack analysis, 2016