Historical retrospective · Security
The DAO exploit forced a difficult Ethereum response
In 2016 a vulnerability in The DAO’s contract logic enabled an attacker to divert funds into a child DAO structure, triggering an intense community response.
The event exposed how smart contracts can behave exactly as coded while still violating user expectations or design intent.
It prompted one of the most consequential governance decisions in Ethereum’s early history.
Audits, formal reasoning and upgrade plans matter; “code is law” does not settle what a community should do after an exploit.
Primary source
This retrospective summarizes the source below in original language. The displayed year refers to the dated event, proposal or specification; it is not the article’s publication date. This is not investment, legal or security advice.