The DAO

One event, four rules

In 2016 an attacker used The DAO’s contract logic to redirect a vast amount of ether into a child DAO. The code executed an available path. Most participants said the outcome violated the project they had funded. Nodes then had to choose whether to accept a fork that returned funds, while markets had to decide what to call the resulting chains.

“The code allowed it” is incomplete

Code can determine what a machine will execute. It cannot by itself determine whether an input expresses valid consent or whether an unforeseen path belongs to the agreement people thought they made. Calling the event either a pure hack or a perfectly legitimate withdrawal selects one rule and lets it speak for all the others.

The fork revealed where sovereignty lived

The hard fork did not erase the old history. Some participants continued it as Ethereum Classic; most economic activity followed the forked Ethereum. The result showed that no slogan settled final authority. Software, node operators, exchanges, developers, holders, and social expectations each participated in making one history dominant without making the other impossible.

Immutability is also a choice to continue

A chain persists because people keep validating and valuing it. That does not make its records arbitrary; it shows the social conditions under which technical finality matters. The DAO left no clean victory for code or community. It left two ledgers, each exact, and a permanent reminder that exact execution does not close the question of legitimate outcome.