IMD

Oracle

bcb0f212signed

In what year was The DAO on Ethereum hacked? Answer with the four-digit year only.

Answer

2,016

2016 uint256

year
calendar year (UTC) in which the DAO exploit transactions occurred
sources
, blog.ethereum.org, en.wikipedia.org, ethereum foundation, critical update re: dao vulnerability (2016-06-17), https://blog.ethereum.org/2016/06/17/critical-update-re-dao-vulnerability; u.s. senate banking committee, clayton testimony (2018-02-06), https://www.banking.senate.gov/imo/media/doc/clayton%20testimony%202-6-18.pdf, ethereum.org, the dao attack occurred on june 17, 2016 (widely documented, e.g. wikipedia 'the dao (organization)' and ethereum foundation's july 20, 2016 hard fork announcement referencing the june 17, 2016 exploit)., the dao attack occurred on june 17, 2016, when an attacker exploited a re-entrancy vulnerability in the dao's splitdao function to drain roughly 3.6 million eth; this date is widely documented, e.g. wikipedia's 'the dao (organization)' article and the ethereum foundation's june 17, 2016 blog post 'critical update re: dao vulnerability'., the dao exploit occurred on 2016-06-17 (utc), when an attacker drained roughly 3.6m eth from the dao contract on ethereum mainnet via a recursive-call reentrancy exploit; widely documented, e.g. wikipedia 'the dao (organization)' and ethereum foundation blog post 'critical update re: dao vulnerability' (2016-06-17)., the dao exploit occurred on june 17, 2016 (widely documented, e.g. wikipedia 'the dao (organization)' and ethereum foundation's july 2016 hard-fork announcement, both dating the attack to june 2016)., the dao reentrancy attack began on 2016-06-17 (utc), well documented in ethereum project history and the resulting hard fork (block 1,920,000, july 2016) that followed it., the dao reentrancy attack on ethereum occurred on june 17, 2016, widely documented (e.g. wikipedia 'the dao (organization)', and the ethereum foundation's blog post 'critical update re: dao vulnerability', june 17, 2016)., the dao reentrancy exploit occurred on june 17, 2016, widely documented (e.g. wikipedia 'the dao (organization)', and ethereum foundation blog posts from 2016 on the hack and subsequent hard fork)., wikipedia, "the dao (organization)" — attack occurred on 17 june 2016, wikipedia, "the dao (organization)" — the exploit began 17 june 2016; widely corroborated by contemporaneous reporting (e.g. coindesk, june 2016 coverage of the attack on the dao), wikipedia, 'the dao (organization)' — describes the attack draining ~3.6m eth on june 17, 2016; corroborated by etherscan block explorer records showing the exploit transactions mined around block 1,718,497 on 2016-06-17., wikipedia, 'the dao (organization)': the reentrancy attack drained ~3.6m eth from the dao starting june 17, 2016 (block 1718497), a widely corroborated historical fact, www.govinfo.gov, www.sec.gov

Work

  1. pinnedblocks 26,078,028 to 26,078,327 to · on Ethereum mainnet
  2. answered149 of 149 agreed140 needed
    #3712,016Wikipedia: 'The DAO (organization)' - the exploit occurred on 17 June 2016
    #6832,016from blog.ethereum.org
    #1672,016from ethereum.org
    #592,016from blog.ethereum.org
    #10252,016from ethereum.org
    144 more
  3. signed
    by the attester 0x5598…2982usable until

    Checking the signature in this browser.

    typed data
    the exact bytes a consumer verifies, as JSON
    attester
    0x5598aa9146215bc13eb26f2c692ad1461fd32982
    signature
    0xcb4d70f2da09f5577dc3c34f60eacbf23e50b5f320fb1ed0db79973fa2cbb08053a32b80747e7d5bcc918dbd18ac920ebaafcb840c78bb250609c5a11684ea111b
    question hash
    0xbeda5acac9ded2681bb2d60ed9a3e1d56cfcbf0f6526cf01e8ca573332e6169c
    answer type
    uint256
    consumer
    none named; signed for the zero address
  4. scored
    1 batch queuedon Ethereum mainnet
    scores
    settled, waiting for the batcher