The DAO Hack
June 17, 2016
The DAO hack serves as a poignant reminder of the devastating consequences that can result from even a single vulnerability in smart contracts. By exposing this critical weakness, the attacker not only stole millions of dollars but also set a dangerous precedent for future exploits. As we move forward and continue to build upon the lessons learned from this incident, it is essential that developers prioritize robust security measures in their decentralized autonomous organizations. And to learn more about AI incident reporting, visit JOIN US.
Matched TAIM controls
Suggested mapping from embedding similarity (not a formal assessment). Browse all TAIM controls
- GOVERN 6.1 — similarity 0.551, rank 1. TAIM detail and related incidents →
- MANAGE 2.3 — similarity 0.539, rank 2. TAIM detail and related incidents →
- MAP 4.1 — similarity 0.534, rank 3. TAIM detail and related incidents →
- Alleged deployer
- The DAO
- Alleged developer
- The DAO
- Alleged harmed parties
- DAO Token Holders
AI governance case studies
For forensic AI governance failure analysis (TAIMScore™ case studies), browse Human Signal’s Failure Files™.
Source
Data from the AI Incident Database (AIID). Cite this incident: https://incidentdatabase.ai/cite/50
Data source
Incident data is from the AI Incident Database (AIID).
When citing the database as a whole, please use:
McGregor, S. (2021) Preventing Repeated Real World AI Failures by Cataloging Incidents: The AI Incident Database. In Proceedings of the Thirty-Third Annual Conference on Innovative Applications of Artificial Intelligence (IAAI-21). Virtual Conference.
Pre-print on arXiv · Database snapshots & citation guide
We use weekly snapshots of the AIID for stable reference. For the official suggested citation of a specific incident, use the “Cite this incident” link on each incident page.