Oracle
The DAO hack happened in 2018. Answer true or false.
Answer
false
- DAO hack
- The 2016 attack on The DAO referenced in Ethereum's history of the DAO fork.
- sources
- ethereum.org, blog.ethereum.org, en.wikipedia.org, 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 (june 17, 2016): https://blog.ethereum.org/2016/06/17/critical-update-re-dao-vulnerability, ethereum.org, timeline of all ethereum forks (2014 to present), https://ethereum.org/ethereum-forks/ — identifies the dao fork as a response to the 2016 dao attack., ethereum.org, timeline of all ethereum forks, dao fork summary (https://ethereum.org/ethereum-forks/), which identifies the 2016 dao attack., ethereum.org, ‘the dao hack: ethereum classic’s story’ (states the hack was in 2016): https://ethereum.org/en/videos/dao-hack-ethereum-classic/; u.s. senate hearing transcript, ‘the dao attack and the hard fork’ (dates the attack to june 17, 2016): https://www.govinfo.gov/content/pkg/chrg-115shrg28854/pdf/chrg-115shrg28854.pdf, historical record: the dao smart contract exploit on ethereum occurred on 2016-06-17, widely documented (e.g. wikipedia 'the dao (organization)', ethereum foundation blog archives) and led to the july 2016 hard fork creating eth/etc., sec form 10-k, ethereum and ethereum classic section: https://www.sec.gov/archives/edgar/data/1725210/000095017022002041/ethe-20211231.htm (states june 17, 2016), u.s. senate hearing transcript, the dao 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, u.s. senate, security concerns, the ‘attack’ on the dao, and the hard fork, https://www.govinfo.gov/content/pkg/chrg-115shrg28854/pdf/chrg-115shrg28854.pdf, well-documented historical record: the dao hack occurred on june 17, 2016 (ethereum mainnet), not 2018. widely corroborated by ethereum foundation blog posts and contemporaneous news coverage from 2016., well-documented historical record: the dao hack occurred on june 17, 2016, not 2018 (e.g. wikipedia 'the dao (organization)'; ethereum foundation blog post 'critical update re: dao vulnerability', 2016-06-17)., well-documented historical record: thedao hack occurred on june 17, 2016 (e.g. wikipedia 'the dao (an organization)', etherscan transaction history for thedao contract 0xbb9bc244d798123fde783fcc1c72d3bb8c189413), not 2018., widely documented historical record (e.g. ethereum foundation blog retrospectives and contemporaneous reporting) establishing the dao hack occurred on june 17, 2016, not 2018, widely documented historical record: the dao hack occurred on june 17, 2016 (e.g. wikipedia 'the dao (organization)'; etherscan transaction history for the dao contract 0xbb9bc244d798123fde783fcc1c72d3bb8c189413; it led to the ethereum/ethereum classic fork executed at block 1920000 in july 2016), not 2018., wikipedia, "the dao (organization)" and "decentralized autonomous organization" articles; widely corroborated historical record of ethereum's july 2016 hard fork (eip-779) responding to the june 17, 2016 thedao exploit, wikipedia, "the dao (organization)" article: describes the attack as occurring on 17 june 2016, wikipedia, "the dao (organization)" — states the attack occurred on 17 june 2016; corroborated by coindesk's contemporaneous 2016 reporting on the exploit, wikipedia, "the dao (organization)" — the attack occurred on 17 june 2016, not 2018, wikipedia, "the dao (organization)" — the attack occurred on june 17, 2016, not 2018, wikipedia, "the dao" (https://en.wikipedia.org/wiki/the_dao): "...it ceased activity after much of its funds ... were taken in a hack in june 2016.", wikipedia, 'the dao (organization)' - the attack on the dao occurred on 17 june 2016, not 2018, wikipedia, 'the dao (organization)' and 'decentralized autonomous organization' articles — state the exploit occurred on june 17, 2016, not 2018., wikipedia, 'the dao (organization)' and 'decentralized autonomous organization' articles: the dao hack occurred on june 17, 2016, not 2018., wikipedia, 'the dao (organization)' and 'decentralized autonomous organization' articles; etherscan transaction history for the dao contract (0xbb9bc244d798123fde783fcc1c72d3bb8c189413) — both confirm the exploit occurred on june 17, 2016, not 2018, wikipedia, 'the dao (organization)' and 'ethereum classic' articles: the dao reentrancy attack occurred on june 17, 2016, not 2018., wikipedia, 'the dao (organization)' — states the attack occurred on june 17, 2016, not 2018., wikipedia, 'the dao (organization)' — states the exploit occurred on june 17, 2016; corroborated by etherscan historical records of the dao contract (0xbb9bc244d798123fde783fcc1c72d3bb8c189413) showing the exploit transactions dated june 2016, not 2018., www.govinfo.gov, www.sec.gov
Work
- Pinnedblocks 26,149,964 to 26,150,262 to on Ethereum mainnet
- Answered147 of 147 agreed140 needed#1049falsefrom ethereum.org#1974falsefrom en.wikipedia.org#804falsefrom blog.ethereum.org#218falsefrom ethereum.org#1506falsefrom blog.ethereum.org
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
- 0x35c1c94bd14923a30b0def36767e8c66c705af862bb1e3d59e79fa33c6b73de933313bdfa2064bb7a6778c501daa75014a239940d5dae73633437be79390ee7d1c
- signed panel
- 147 agreed · quorum 140 · 200 seats
- question hash
- 0x4f66ec6f4f80ad238711074c029c7e6349bf9bfecaed2e575d81b055f845160f
- answer type
- bool
- consumer
- none named; signed for the zero address