Official MASTR logo MASTR Support the work
Contents
← Wiki home

Crypto history

The DAO: code, governance and the 2016 split

The application incident and the community's response became separate parts of Ethereum history.

History · 2016–2017 · 1 min read

Research articles and reference entries are published in English. Navigation is available in seven languages.

In this article
  1. Two different questions

The DAO incident in 2016 led to a disputed response in the Ethereum community and a chain split. The history illustrates that a smart-contract system operates within a social process: people still decide which software and history to follow after a major failure.

The SEC later published a 2017 investigative report concluding that the DAO tokens it examined were securities. That report concerned the facts and economic arrangement of that offering. It should not be treated as a one-line legal classification for every later DAO.

Two different questions

Technical analysis asks how assets could move and which controls failed. Governance analysis asks who had the authority and practical ability to respond. Both matter to participants, and neither can be reduced to the slogan that code decides everything.

For a contemporary treasury, examine proposal rights, voting power and execution conditions. For a contract review, examine the precise deployment and upgrade powers. See DAO governance and audit scope.

Sources

  1. Ethereum: network history and forks
  2. SEC: The DAO investigative report, 25 July 2017

Research checked 5 September 2026. Historical cases retain the date and legal status of the cited record.

Related reading

MASTR

Support independent research

The investigations, original evidence and guides here are free to read. Voluntary donations help fund the research and keep MASTR’s tools available.

Open wallet