Skip to main content

The DAO Hacked

  • Chapter
  • First Online:
Blockchain Enabled Applications

Abstract

Here, we want to highlight a historic moment leading to the creation of the first DAO, and how it eventually got hacked. Our discussion begins with a fresh perspective on decentralized organizations from Buterin, and leads into the story of Slock.it, the company at the heart of the DAO revolution. Then, we present some code that made The DAO dysfunctional: pieces of the smart contract relevant to the vulnerability, the conditions that allowed repetitive withdrawals from The DAO, and the exploit itself. We conclude the chapter by talking about the consequences of this hack: the debate about hard vs. soft forks, and the creation of Ethereum Classic.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 39.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Notes

  1. 1.

    See https://blog.ethereum.org/2014/05/06/daos-dacs-das-and-more-an-incomplete-terminology-guide/

  2. 2.

    See https://bitcoinmagazine.com/articles/bootstrapping-a-decentralized-autonomous-corporation-part-i-1379644274/

  3. 3.

    To put this in perspective, 15 days into the DAO’s crowdsale, members of the MakerDAO subreddit were discussing proposals that would trigger an investment in MakerDao by the DAO.

  4. 4.

    https://blog.slock.it/the-history-of-the-dao-and-lessons-learned-d06740f8cfa5

  5. 5.

    This could be the case because proposals required a quorum of 20 percent of votes to have weighed in on a proposal for the vote to be valid.

  6. 6.

    Curators weren’t necessarily human gatekeepers. Gavin Wood “resigned” as a curator of The DAO to make a point that curation was merely a technical role and that the curator had no proactive control over The DAO.

  7. 7.

    http://hackingdistributed.com/2016/05/27/dao-call-for-moratorium/

  8. 8.

    http://vessenes.com/more-ethereum-attacks-race-to-empty-is-the-real-deal/

  9. 9.

    Rentrancy is a characteristic of software in which a routine can be interrupted in the middle of its execution, and then be intiated (reentered) from its beginning, while the remaining portion of the original instance of the routine remains queued for execution.

  10. 10.

    https://www.reddit.com/r/ethereum/comments/4p7mhc/update_on_the_white_hat_attack/

  11. 11.

    https://bitcoinmagazine.com/articles/rejecting-today-s-hard-fork-the-ethereum-classic-project-continues-on-the-original-chain-here-s-why-1469038808/

Author information

Authors and Affiliations

Authors

Rights and permissions

Reprints and permissions

Copyright information

© 2017 Vikram Dhillon, David Metcalf, and Max Hooper

About this chapter

Check for updates. Verify currency and authenticity via CrossMark

Cite this chapter

Dhillon, V., Metcalf, D., Hooper, M. (2017). The DAO Hacked. In: Blockchain Enabled Applications. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-3081-7_6

Download citation

Publish with us

Policies and ethics