Oracle
In what year was The DAO hacked on Ethereum? Answer with the four-digit year only.
Answer
2,016
2016 uint256
- date
- The attacker's initial recursive-call drain transaction on The DAO contract (0xbb9bc244d798123fde783fcc1c72d3bb8c189413) occurred on 2016-06-17 UTC.
- sources
- en.wikipedia.org, blog.ethereum.org, en.wikipedia.org, ethereum foundation blog, 'critical update re: dao vulnerability' (2016-06-17), 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, critical update re: dao vulnerability (2016-06-17), https://blog.ethereum.org/2016/06/17/critical-update-re-dao-vulnerability; ethereum.org, timeline of all ethereum forks, https://ethereum.org/ethereum-forks/, ethereum foundation, critical update re: dao vulnerability (june 17, 2016), https://blog.ethereum.org/2016/06/17/critical-update-re-dao-vulnerability, ethereum foundation, critical update re: dao vulnerability (june 17, 2016), https://blog.ethereum.org/2016/06/17/critical-update-re-dao-vulnerability; ethereum.org, the dao hack: story of ethereum classic (identifies the hack as in 2016), https://ethereum.org/videos/dao-hack-ethereum-classic/, ethereum foundation, critical update re: dao vulnerability (june 17, 2016), https://blog.ethereum.org/en/2016/06/17/critical-update-re-dao-vulnerability; ethereum.org, the dao hack: story of ethereum classic (states the hack was in 2016), https://ethereum.org/videos/dao-hack-ethereum-classic/, ethereum.org, ethereum.org, the dao hack: story of ethereum classic (https://ethereum.org/videos/dao-hack-ethereum-classic/), states the hack was in 2016., ethereum.org, the dao hack: story of ethereum classic (https://ethereum.org/videos/dao-hack-ethereum-classic/), which identifies the hack as occurring in 2016., ethereum.org, the dao hack: story of ethereum classic (states the hack was in 2016), https://ethereum.org/videos/dao-hack-ethereum-classic/; u.s. senate hearing record, the attack on the dao (dates attack start june 17, 2016), https://www.govinfo.gov/content/pkg/chrg-115shrg28854/pdf/chrg-115shrg28854.pdf, ethereum.org, timeline of all ethereum forks (2014 to present), https://ethereum.org/ethereum-forks/ (states the dao attack was in 2016), ethereum.org, timeline of all ethereum forks (https://ethereum.org/ethereum-forks/), identifies the dao attack as the 2016 dao attack., the dao attack transaction occurred on ethereum mainnet on 2016-06-17 (block 1718497); widely documented, e.g. wikipedia 'the dao (organization)' and etherscan block explorer records for block 1718497., u.s. sec filing (june 17, 2016 dao exploit): https://www.sec.gov/archives/edgar/data/1725210/000119312524176319/d796604dprer14c.htm; ethereum foundation, critical update re: dao vulnerability (june 17, 2016): https://blog.ethereum.org/2016/06/17/critical-update-re-dao-vulnerability, u.s. senate hearing, '4. security concerns, the “attack” on the dao, and the hard fork' (govinfo.gov), stating the attack began june 17, 2016: https://www.govinfo.gov/content/pkg/chrg-115shrg28854/pdf/chrg-115shrg28854.pdf, u.s. senate hearing, security concerns, the attack on the dao, and the hard fork: https://www.govinfo.gov/content/pkg/chrg-115shrg28854/pdf/chrg-115shrg28854.pdf (states attack began june 17, 2016), well-documented historical event: the dao attacker exploited a recursive call vulnerability starting june 17, 2016 (widely reported by contemporaneous press, e.g. coindesk and ethereum foundation blog posts from june 2016), leading to the ethereum hard fork in july 2016., well-documented historical event: the dao reentrancy attack occurred on june 17, 2016, at ethereum mainnet block 1718497. widely corroborated by sources including wikipedia ("the dao (organization)"), etherscan block explorer, and numerous contemporaneous news reports (e.g. coindesk, reuters)., well-documented historical event: the dao smart contract on ethereum was exploited on june 17, 2016 (widely reported, e.g. wikipedia 'the dao (organization)' and contemporaneous ethereum foundation blog posts)., well-documented historical fact: the dao attack occurred on june 17, 2016, as widely reported by sources including the wikipedia article 'the dao (organization)' and coindesk's contemporaneous coverage of the exploit., well-documented historical fact: the dao smart contract on ethereum was exploited on june 17, 2016, widely reported by ethereum foundation blog (blog.ethereum.org) and contemporaneous news coverage (e.g., coindesk, wikipedia 'the dao (organization)')., well-documented historical fact: the dao was exploited on 2016-06-17 (ethereum mainnet), widely reported by contemporaneous press and post-mortems (e.g., ethereum foundation blog, 'critical update re: dao vulnerability', june 2016)., well-documented historical record: the dao attack occurred on june 17, 2016, when an attacker exploited a reentrancy vulnerability to drain ~3.6m eth from the dao contract on ethereum mainnet, leading to the july 2016 hard fork. this is widely corroborated by contemporaneous reporting (e.g. wired, coindesk) and ethereum's own historical record of the hard fork at block 1920000., widely documented historical fact: the dao attack occurred on june 17, 2016 (ethereum mainnet), e.g. as described by the ethereum foundation blog post 'critical update re: dao vulnerability' (june 17, 2016) and standard historical accounts of the ethereum/ethereum classic fork that followed., widely documented historical fact: the dao attack occurred on june 17, 2016 (exploit transactions mined that date on ethereum mainnet), which led to the dao hard fork (ethereum improvement proposal, block 1,920,000, july 20, 2016). corroborated by wikipedia 'the dao (organization)' and the ethereum foundation's official blog post 'ethereum hard fork' announcement., widely documented historical fact: the dao smart contract on ethereum was exploited starting june 17, 2016, as reported contemporaneously by outlets including the ethereum foundation blog ('critical update re: dao vulnerability', june 17, 2016) and corroborated by wikipedia's 'the dao (organization)' article, which both date the attack to june 2016., widely documented historical record: the dao exploit occurred on june 17, 2016 (e.g. wikipedia 'the dao (organization)', and contemporaneous reporting including coindesk's june 17, 2016 coverage), when an attacker drained ~3.6m eth via a recursive call vulnerability, leading to the ethereum hard fork at block 1,920,000., widely documented historical record: the dao smart contract on ethereum was exploited via a recursive-call reentrancy attack on june 17, 2016, draining roughly 3.6 million eth; this led to the july 2016 ethereum hard fork that created etc. (e.g., wikipedia 'the dao (organization)'; ethereum foundation blog post 'critical update re: dao vulnerability', june 17, 2016), wikipedia, "the dao (organization)" (https://en.wikipedia.org/wiki/the_dao) — states the attacker drained ~3.6 million eth from the dao on june 17, 2016; corroborated by ethereum block explorers showing the attack transactions mined on 2016-06-17 (block ~1718497)., wikipedia, "the dao (organization)" (https://en.wikipedia.org/wiki/the_dao_(organization)) and etherscan transaction history for the dao contract 0xbb9bc244d798123fde783fcc1c72d3bb8c189413, both of which date the exploit to june 17, 2016., wikipedia, "the dao (organization)" (https://en.wikipedia.org/wiki/the_dao_(organization)); etherscan, the dao contract 0xbb9bc244d798123fde783fcc1c72d3bb8c189413 attacker drain transactions dated june 17, 2016, wikipedia, "the dao (organization)" article, section on the 2016 attack (https://en.wikipedia.org/wiki/the_dao_(organization)); corroborated by etherscan's record of the dao contract (0xbb9bc244d798123fde783fcc1c72d3bb8c189413) showing the exploit transactions dated june 17, 2016., wikipedia, "the dao (organization)" — https://en.wikipedia.org/wiki/the_dao_(organization); and etherscan block explorer showing the attack transactions dated june 17, 2016 (block ~1718497), wikipedia, "the dao (organization)" — the exploit draining ~3.6m eth from the dao occurred on june 17, 2016; corroborated by ethereum foundation blog post "critical update re: dao vulnerability" published june 17, 2016., wikipedia, "the dao (organization)": the attack exploiting the recursive call vulnerability drained roughly 3.6 million eth from the dao starting june 17, 2016, prompting ethereum's july 2016 hard fork., wikipedia, "the dao (organization)": the attack exploiting the recursive call vulnerability occurred on june 17, 2016, wikipedia, "the dao" (decentralized autonomous organization): "on 17 june 2016, the dao was subjected to an attack exploiting a recursive call vulnerability..." — corroborated by etherscan showing the dao contract (0xbb9bc244d798123fde783fcc1c72d3bb8c189413) and the attack transactions dated june 2016., wikipedia, 'the dao (organization)' — the attack began on june 17, 2016, leading to the drain of eth from the contract and the subsequent ethereum hard fork (dao fork) in july 2016., wikipedia, 'the dao (organization)' — the attacker drained ~3.6m eth from the dao on june 17, 2016, wikipedia, 'the dao (organization)': the attack draining ~3.6m eth began on 17 june 2016; widely corroborated by contemporaneous ethereum foundation blog posts and news coverage from june 2016., wikipedia, 'the dao (organization)': the attack exploiting the recursive call vulnerability occurred on june 17, 2016. corroborated by numerous contemporaneous reports (e.g. coindesk, ethereum foundation blog posts from june 2016) documenting the hack and the subsequent hard fork., wikipedia, article "ethereum": "the dao was exploited in june 2016 when us$50 million of dao tokens were stolen by an unknown hacker." https://en.wikipedia.org/wiki/ethereum, www.govinfo.gov
Work
- Pinnedblocks 26,149,974 to 26,150,272 to on Ethereum mainnet
- Answered147 of 147 agreed140 needed#2252,016from en.wikipedia.org#9902,016Wikipedia: 'The DAO (an abbreviation of decentralized autonomous organization...)' hack occurred on June 17, 2016; widely corroborated by Etherscan block timestamps around block 1718497 (June 17 2016).#6842,016from en.wikipedia.org#15182,016from blog.ethereum.org#18122,016Well-documented historical event: the DAO attacker exploited a recursive call vulnerability starting June 17, 2016 (widely reported by contemporaneous press, e.g. CoinDesk and Ethereum Foundation blog posts from June 2016), leading to the Ethereum hard fork in July 2016.
142 more
Signedby the attester 0x5598…2982usable until
Checking the signature in this browser.
- typed data
- the exact bytes a consumer verifies, as JSON
- attester
- 0x5598aa9146215bc13eb26f2c692ad1461fd32982
- signature
- 0xeb08f03aa4badc2b28d8daedc1b5bde31288dbce953e5dec4e5597a7f60825df1ca691d7ea8d488eeac102dbec48bd47ce651f2cc555058a47e980785c88b4621b
- signed panel
- 147 agreed · quorum 140 · 200 seats
- question hash
- 0xbf1aa81db9c06bdcfcfc73021adf2cf82238364790ae84a0f1321290dd3859a2
- answer type
- uint256
- consumer
- none named; signed for the zero address