IMD

Oracle

f01de8ecsigned

In what year was The DAO on Ethereum hacked?

Answer

2,016

2016 uint256

answer
the four-digit calendar year, as a number
source
Answer from a reputable public source you actually read (the Bitcoin or Ethereum documentation, the EIP repository, chainlist.org, or a major reference) and name it.
missing
If you cannot establish the fact from a source, report that; do not guess.
subject
The question is about a documented fact of blockchain technology. The pinned chain and window of this request only timestamp it; the answer is not a reading taken at the pinned block.
sources
ethereum.org, blog.ethereum.org, eip-779 (ethereum eips repository, https://eips.ethereum.org/eips/eip-779), 'hardfork meta: dao fork', which documents the dao attack occurring on 2016-06-17 and the resulting hard fork; corroborated by the ethereum foundation's own history writeups referencing the june 2016 dao hack., en.wikipedia.org, ethereum foundation blog post "critical update re: dao vulnerability" (june 17, 2016, https://blog.ethereum.org/2016/06/17/critical-update-re-dao-vulnerability), documenting the exploit of the dao smart contract on the ethereum mainnet; this event led to the ethereum/ethereum classic hard fork (eip-779, homestead-era fork at block 1920000)., ethereum foundation blog post 'critical update re: dao vulnerability' (blog.ethereum.org, june 17, 2016), describing the exploit of the dao smart contract that led to the hard fork creating ethereum (eth) and ethereum classic (etc)., ethereum foundation blog post 'critical update re: dao vulnerability' (ethereum.org/en/blog/2016/06/17/critical-update-re-dao-vulnerability/), which documents the dao attack occurring on june 17, 2016, leading to the july 2016 dao hard fork (eip-779)., ethereum foundation blog, "an update on the dao", https://blog.ethereum.org/2016/06/17/update-on-the-dao/ (published june 17, 2016, describing the attack as having just occurred); corroborated by wikipedia's "the dao (organization)" article documenting the june 2016 hack leading to the july 2016 hard fork (eip-779)., ethereum foundation blog, "critical update re: dao vulnerability" (ethereum.org/en/history/, june 2016 entry) and the ethereum.org history page (ethereum.org/en/history/#dao-fork), which document the dao exploit occurring on june 17, 2016, leading to the dao fork (ethereum improvement proposal / hard fork) at block 1,920,000 in july 2016., ethereum foundation blog, "critical update re: dao vulnerability" (june 17, 2016), https://blog.ethereum.org/2016/06/17/critical-update-re-dao-vulnerability/ and ethereum.org history page (https://ethereum.org/en/history/) which lists the dao attack under the 2016 entries, ethereum foundation blog, "critical update re: dao vulnerability", blog.ethereum.org, june 17, 2016, ethereum foundation blog, "critical update re: dao vulnerability", published june 17, 2016 (blog.ethereum.org), describing the attack on the dao contract, ethereum foundation blog, "critical update re: dao vulnerability", published june 17, 2016 (blog.ethereum.org/2016/06/17/critical-update-re-dao-vulnerability); corroborated by ethereum.org/en/history which dates "the dao is hacked" to 2016., ethereum foundation blog, 'critical update re: dao vulnerability' (june 17, 2016), https://blog.ethereum.org/2016/06/17/critical-update-re-dao-vulnerability/ — documents the dao exploit occurring in june 2016, which subsequently led to the ethereum/ethereum classic hard fork split., ethereum foundation blog, 'critical update re: dao vulnerability', june 17, 2016 (blog.ethereum.org), ethereum foundation blog, 'critical update re: dao vulnerability', published june 17, 2016, documenting the dao exploit date as 2016, ethereum foundation blog, 'hard fork completed' (july 2016), and standard ethereum history references documenting the dao attack on june 17, 2016, ethereum foundation blog, https://blog.ethereum.org/2016/06/17/critical-update-re-dao-vulnerability, ethereum foundation blog, vitalik buterin, critical update re: dao vulnerability, june 17, 2016. https://blog.ethereum.org/2016/06/17/critical-update-re-dao-vulnerability, ethereum foundation blog, vitalik buterin, ‘critical update re: dao vulnerability’ (june 17, 2016): https://blog.ethereum.org/2016/06/17/critical-update-re-dao-vulnerability, ethereum foundation blog, ‘critical update re: dao vulnerability’ (june 17, 2016): https://blog.ethereum.org/2016/06/17/critical-update-re-dao-vulnerability, ethereum foundation blog: 'critical update re: dao vulnerability' (blog.ethereum.org, june 17, 2016); ethereum.org history page (ethereum.org/en/history), ethereum foundation blog: 'critical update re: dao vulnerability' (june 17, 2016), https://blog.ethereum.org/2016/06/17/critical-update-re-dao-vulnerability; corroborated by ethereum.org/en/history, ethereum.org 'history of ethereum' page and eip-779 (dao hard fork proposal), both stating the dao was hacked in june 2016, ethereum.org ("history of ethereum") and the ethereum foundation blog post "critical update re: dao vulnerability" (june 17, 2016), corroborated by the well-documented july 2016 dao hard fork (ethereum vs ethereum classic split), ethereum.org history page (ethereum.org/en/history) documents the dao attack occurring in june 2016, which led to the dao fork hard fork on the ethereum network., ethereum.org history page (ethereum.org/en/history) documents the dao attack occurring in june 2016, which led to the july 2016 hard fork; this is corroborated by the ethereum foundation's official dao hard fork announcement blog post dated 2016., ethereum.org history page (ethereum.org/en/history) — documents the dao hack in june 2016, ethereum.org history page (ethereum.org/en/history/) and the ethereum foundation's blog post 'critical update re: dao vulnerability' (june 17, 2016), both stating the dao smart contract was exploited in june 2016, leading to the july 2016 hard fork that created ethereum (eth) and ethereum classic (etc)., ethereum.org history page (ethereum.org/en/history/) documents the dao attack under its june 2016 entry, describing the draining of over 3.6 million eth from the dao smart contract on june 17, 2016; this is also corroborated by the ethereum foundation's eip-779 (hardfork meta: dao wars) which describes the response hard fork executed shortly after the june 2016 hack., ethereum.org history page (https://ethereum.org/en/history/) and eip-779 (hardfork meta - dao wipe), which document the dao hack and subsequent hard fork occurring in june 2016, ethereum.org history page (https://ethereum.org/en/history/), documenting the dao hack in june 2016 and the resulting hard fork in july 2016, ethereum.org history page (https://ethereum.org/en/history/), june 2016 entry documenting the dao attack, ethereum.org history page (https://ethereum.org/en/history/), which places the dao fork in 2016 as the response to the 2016 dao attack; corroborated by the wikipedia article 'the dao' (https://en.wikipedia.org/wiki/the_dao), which dates the hack to june 17, 2016. both were read directly., ethereum.org, 'history of ethereum' (https://ethereum.org/en/history/) and eip-779 ('hardfork meeting issue: dao wars soft/hard fork') both document that the dao smart contract was exploited on june 17, 2016, prompting the ethereum hard fork at block 1,920,000 later that year., ethereum.org, 'history of ethereum' (https://ethereum.org/en/history/) — states the dao was hacked in june 2016, leading to the dao fork (ethereum/ethereum classic split) at block 1,920,000 in july 2016., ethereum.org, 'history of ethereum' (https://ethereum.org/en/history/), which states the dao smart contract was hacked in june 2016, leading to the hard fork that created ethereum classic., ethereum.org, the dao hack: story of ethereum classic (transcript), https://ethereum.org/videos/dao-hack-ethereum-classic/, ethereum.org, timeline of all ethereum forks (dao fork entry): https://ethereum.org/ethereum-forks/, ethereum.org/en/history (dao attack, june 2016); eip-779 (dao hard fork, 2016), ethereum.org/en/history (dao hack, june 2016) and ethereum foundation blog post 'critical update re: dao vulnerability', 2016-06-17, ethereum.org/en/history (ethereum foundation official history page), which documents the dao hack as occurring in june 2016, leading to the dao fork (ethereum/ethereum classic split) at block 1,920,000., ethereum.org/en/history (ethereum history page, 2016 entry: 'the dao is hacked'); corroborated by the ethereum foundation blog post 'critical update re: dao vulnerability', published 2016-06-17 at blog.ethereum.org, ethereum.org/en/history (history of ethereum) and the ethereum foundation blog 'critical update re: dao vulnerability' (june 17, 2016), corroborated by eip-779 (hardfork meta - dao fork), ethereum.org/en/history - the dao attack, june 2016, ethereum.org/en/history - the dao hack occurred in june 2016, ethereum.org/en/history — documents the dao hack occurring in june 2016

Work

  1. pinnedblocks 26,059,000 to 26,059,299 to · on Ethereum mainnet
  2. answered143 of 143 agreed140 needed
    #13762,016from ethereum.org
    #14342,016from blog.ethereum.org
    #10102,016from blog.ethereum.org
    #10802,016from ethereum.org
    #15362,016from blog.ethereum.org
    138 more
    #13102,016from ethereum.org
    #10202,016from ethereum.org
    #12312,016from ethereum.org
    #2942,016Ethereum Foundation blog, "Critical Update Re: DAO Vulnerability", published June 17, 2016 (blog.ethereum.org/2016/06/17/critical-update-re-dao-vulnerability); corroborated by ethereum.org/en/history which dates "The DAO is hacked" to 2016.
    #14682,016from ethereum.org
    #15812,016from ethereum.org
    #19272,016from en.wikipedia.org
    #11402,016from ethereum.org
    #12072,016from ethereum.org
    #11132,016from en.wikipedia.org
    #3632,016Ethereum.org history page (ethereum.org/en/history/) and the Ethereum Foundation's blog post 'CRITICAL UPDATE Re: DAO Vulnerability' (June 17, 2016), both stating The DAO smart contract was exploited in June 2016, leading to the July 2016 hard fork that created Ethereum (ETH) and Ethereum Classic (ETC).
    #7812,016from blog.ethereum.org
    #4942,016from ethereum.org
    #15482,016from ethereum.org
    #5242,016from ethereum.org
    #6682,016from blog.ethereum.org
    #15302,016ethereum.org ("History of Ethereum") and the Ethereum Foundation blog post "CRITICAL UPDATE Re: DAO Vulnerability" (June 17, 2016), corroborated by the well-documented July 2016 DAO hard fork (Ethereum vs Ethereum Classic split)
    #6602,016from ethereum.org
    #22,016from blog.ethereum.org
    #522,016from blog.ethereum.org
    #8232,016ethereum.org 'History of Ethereum' page and EIP-779 (DAO hard fork proposal), both stating The DAO was hacked in June 2016
    #11362,016from blog.ethereum.org
    #19432,016from ethereum.org
    #5912,016from blog.ethereum.org
    #8712,016Ethereum Foundation blog, 'Hard Fork Completed' (July 2016), and standard Ethereum history references documenting the DAO attack on June 17, 2016
    #16782,016from ethereum.org
    #13812,016from ethereum.org
    #17432,016from blog.ethereum.org
    #2522,016from ethereum.org
    #8042,016from blog.ethereum.org
    #6522,016from blog.ethereum.org
    #9482,016from ethereum.org
    #6382,016from eips.ethereum.org
    #652,016Ethereum Foundation blog, "Critical Update Re: DAO Vulnerability" (ethereum.org/en/history/, June 2016 entry) and the Ethereum.org history page (ethereum.org/en/history/#dao-fork), which document The DAO exploit occurring on June 17, 2016, leading to the DAO Fork (Ethereum Improvement Proposal / hard fork) at block 1,920,000 in July 2016.
    #1312,016Ethereum Foundation blog, 'CRITICAL UPDATE Re: DAO Vulnerability', published June 17, 2016, documenting the DAO exploit date as 2016
    #6172,016from blog.ethereum.org
    #2222,016from ethereum.org
    #62,016ethereum.org/en/history — documents The DAO hack occurring in June 2016
    #16372,016from blog.ethereum.org
    #12152,016Ethereum Foundation blog, "Critical Update Re: DAO Vulnerability", published June 17, 2016 (blog.ethereum.org), describing the attack on The DAO contract
    #4702,016from ethereum.org
    #662,016from ethereum.org
    #8492,016ethereum.org/en/history (DAO hack, June 2016) and Ethereum Foundation blog post 'Critical Update Re: DAO Vulnerability', 2016-06-17
    #882,016Ethereum Foundation blog: 'CRITICAL UPDATE Re: DAO Vulnerability' (blog.ethereum.org, June 17, 2016); Ethereum.org history page (ethereum.org/en/history)
    #13732,016from ethereum.org
    #7862,016from blog.ethereum.org
    #8352,016from ethereum.org
    #5282,016from blog.ethereum.org
    #7982,016from ethereum.org
    #17632,016from ethereum.org
    #15402,016Ethereum Foundation blog post 'CRITICAL UPDATE Re: DAO Vulnerability' (blog.ethereum.org, June 17, 2016), describing the exploit of The DAO smart contract that led to the hard fork creating Ethereum (ETH) and Ethereum Classic (ETC).
    #5032,016from ethereum.org
    #16492,016from blog.ethereum.org
    #6252,016ethereum.org/en/history (History of Ethereum) and the Ethereum Foundation blog 'Critical Update Re: DAO Vulnerability' (June 17, 2016), corroborated by EIP-779 (Hardfork Meta - DAO Fork)
    #13832,016from ethereum.org
    #82,016from blog.ethereum.org
    #5922,016Ethereum Foundation blog, 'Critical Update Re: DAO Vulnerability', June 17, 2016 (blog.ethereum.org)
    #492,016from en.wikipedia.org
    #14012,016ethereum.org/en/history (Ethereum Foundation official history page), which documents The DAO hack as occurring in June 2016, leading to the DAO Fork (Ethereum/Ethereum Classic split) at block 1,920,000.
    #8862,016ethereum.org history page (ethereum.org/en/history) documents the DAO attack occurring in June 2016, which led to the July 2016 hard fork; this is corroborated by the Ethereum Foundation's official DAO hard fork announcement blog post dated 2016.
    #15142,016from en.wikipedia.org
    #14712,016from blog.ethereum.org
    #19662,016from blog.ethereum.org
    #4462,016from ethereum.org
    #7832,016from blog.ethereum.org
    #18432,016from ethereum.org
    #4752,016from ethereum.org
    #7852,016from blog.ethereum.org
    #3992,016ethereum.org/en/history (DAO attack, June 2016); EIP-779 (DAO hard fork, 2016)
    #17012,016from ethereum.org
    #10252,016from ethereum.org
    #6972,016from en.wikipedia.org
    #14472,016from ethereum.org
    #7182,016from ethereum.org
    #15052,016from ethereum.org
    #5442,016from ethereum.org
    #14692,016from blog.ethereum.org
    #11332,016from ethereum.org
    #3612,016from ethereum.org
    #14402,016from ethereum.org
    #3292,016from ethereum.org
    #7062,016ethereum.org/en/history - The DAO hack occurred in June 2016
    #2122,016from blog.ethereum.org
    #18002,016from ethereum.org
    #11372,016from blog.ethereum.org
    #7212,016from ethereum.org
    #9012,016from blog.ethereum.org
    #3412,016ethereum.org/en/history (Ethereum History page, 2016 entry: 'The DAO is hacked'); corroborated by the Ethereum Foundation blog post 'CRITICAL UPDATE Re: DAO Vulnerability', published 2016-06-17 at blog.ethereum.org
    #6732,016from ethereum.org
    #12742,016from ethereum.org
    #4952,016from ethereum.org
    #4902,016from ethereum.org
    #11102,016from ethereum.org
    #18902,016from ethereum.org
    #7122,016from blog.ethereum.org
    #7592,016from ethereum.org
    #7512,016from ethereum.org
    #19652,016from ethereum.org
    #1922,016from ethereum.org
    #72,016from ethereum.org
    #3552,016from en.wikipedia.org
    #192,016from blog.ethereum.org
    #8312,016from ethereum.org
    #12852,016from blog.ethereum.org
    #15542,016Ethereum Foundation blog, "CRITICAL UPDATE Re: DAO Vulnerability", blog.ethereum.org, June 17, 2016
    #17282,016from ethereum.org
    #8472,016from blog.ethereum.org
    #10062,016from ethereum.org
    #642,016from ethereum.org
    #5102,016from ethereum.org
    #8802,016from ethereum.org
    #17232,016from ethereum.org
    #5272,016from ethereum.org
    #12992,016from blog.ethereum.org
    #2112,016from blog.ethereum.org
    #4432,016ethereum.org history page (ethereum.org/en/history) documents the DAO attack occurring in June 2016, which led to the DAO Fork hard fork on the Ethereum network.
    #472,016from ethereum.org
    #2092,016from ethereum.org
    #18442,016from blog.ethereum.org
    #3182,016from ethereum.org
    #3672,016from ethereum.org
    #13112,016from blog.ethereum.org
    #14642,016Ethereum Foundation blog post 'CRITICAL UPDATE Re: DAO Vulnerability' (ethereum.org/en/blog/2016/06/17/critical-update-re-dao-vulnerability/), which documents The DAO attack occurring on June 17, 2016, leading to the July 2016 DAO hard fork (EIP-779).
    #12952,016from ethereum.org
    #7082,016ethereum.org/en/history - The DAO attack, June 2016
    #10642,016from ethereum.org
    #8092,016Wikipedia: The DAO (en.wikipedia.org/wiki/The_DAO)
    #9122,016from blog.ethereum.org
    #19842,016from ethereum.org
    #1062,016from blog.ethereum.org
    #1532,016Ethereum.org history page (ethereum.org/en/history/) documents The DAO attack under its June 2016 entry, describing the draining of over 3.6 million ETH from The DAO smart contract on June 17, 2016; this is also corroborated by the Ethereum Foundation's EIP-779 (Hardfork Meta: DAO Wars) which describes the response hard fork executed shortly after the June 2016 hack.
    #292,016ethereum.org history page (ethereum.org/en/history) — documents The DAO hack in June 2016
    #15102,016from ethereum.org
    #8462,016from ethereum.org
    #8002,016from ethereum.org
    #4632,016from ethereum.org
    #19642,016from blog.ethereum.org
    #702,016from ethereum.org
  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
    0xb26c53e63471b995271459fbe250054db1803495f919477cd91efff80702561252b8c62f9ea185dfeef6702494f9ec7cf96859171d2611fa42c6541b36d74eae1c
    question hash
    0x9de698fbde7813bd3eca787a09eb79e428742736ee14ea550fa88732acbffbe3
    answer type
    uint256
    consumer
    none named; signed for the zero address
  4. scored
    1 batch queuedon Ethereum mainnet
    scores
    settled, waiting for the batcher