Oracle
The DAO hack in 2016 led to a hard fork that created Ethereum Classic. Answer true or false.
Answer
true
- created Ethereum Classic
- The 2016 DAO fork caused a chain split; miners who declined the fork continued the original chain, which became Ethereum Classic.
- sources
- ethereum.org, blog.ethereum.org, en.wikipedia.org, ethereum classic, classic history (https://www.ethereumclassic.org/knowledge/history/), entries for the dao bailout hard fork and the original non-fork chain rebranded ethereum classic; ethereum improvement proposals, eip-779: hardfork meta: dao fork (https://eips.ethereum.org/eips/eip-779)., ethereum foundation blog post "hard fork completed" (2016-07-20, blog.ethereum.org) and wikipedia "ethereum classic" article, both describing the dao hack and the resulting hard fork that split ethereum into ethereum (eth) and ethereum classic (etc)., ethereum foundation blog post 'hard fork completed' (2016-07-20, https://blog.ethereum.org/2016/07/20/hard-fork-completed) and wikipedia 'ethereum classic' article, both documenting that the july 2016 hard fork responding to the dao hack split the network, with the pre-fork chain continuing as ethereum classic., ethereum foundation blog, 'hard fork completed' (july 20, 2016), https://blog.ethereum.org/2016/07/20/hard-fork-completed; corroborated by wikipedia, 'ethereum classic' article describing its origin as the chain that rejected the dao hard fork., ethereum.org, the dao hack: story of ethereum classic (https://ethereum.org/videos/dao-hack-ethereum-classic/); sec form 10-k (https://www.sec.gov/archives/edgar/data/1725210/000095017022002041/ethe-20211231.htm), ethereum.org, timeline of all ethereum forks (2014 to present): https://ethereum.org/ethereum-forks/; ethereum foundation, hard fork completed (20 july 2016): https://blog.ethereum.org/2016/07/20/hard-fork-completed, ethereum.org, timeline of all ethereum forks (dao fork section): https://ethereum.org/ethereum-forks/, ethereum.org, timeline of all ethereum forks (dao fork): https://ethereum.org/ethereum-forks/, ethereum.org, timeline of all ethereum forks (dao fork, 2016): https://ethereum.org/ethereum-forks/, ethereum.org, timeline of all ethereum forks (https://ethereum.org/en/ethereum-forks/); ethereum classic, classic history (https://www.ethereumclassic.org/knowledge/history/), ethereum.org, timeline of all ethereum forks (https://ethereum.org/ethereum-forks/); ethereum classic, classic history (https://ethereumclassic.org/knowledge/history/), ethereum.org, timeline of all ethereum forks (https://ethereum.org/ethereum-forks/); ethereum classic, classic history (https://www.ethereumclassic.org/knowledge/history/)., ethereumclassic.org, wikipedia, "ethereum classic" (https://en.wikipedia.org/wiki/ethereum_classic) and wikipedia, "the dao" (https://en.wikipedia.org/wiki/the_dao) — both describe the 2016 dao hack and the resulting hard fork that split ethereum into the forked chain (eth) and the original, unforked chain (ethereum classic, etc)., wikipedia, "ethereum classic" (https://en.wikipedia.org/wiki/ethereum_classic): states ethereum classic originated from a hard fork of ethereum in july 2016, which was a response to the exploitation of the dao. corroborated by wikipedia, "the dao (organization)" article describing the same 2016 hack and resulting hard fork/chain split., wikipedia, "ethereum classic": "ethereum classic... emerged from a hard fork... the fork was a response to the exploitation of a flaw in the dao... those who disagreed with the fork... continued with the original unforked blockchain as ethereum classic." (https://en.wikipedia.org/wiki/ethereum_classic), wikipedia, 'ethereum classic' (https://en.wikipedia.org/wiki/ethereum_classic): 'ethereum classic ... is a blockchain ... it is the unaltered, original form of the ethereum network ... the hard fork was performed on 20 july 2016, in order to reappropriate the funds of the dao ... part of the community did not agree with this intervention ... they rejected the hard fork and continued to mine the original chain, naming it ethereum classic.', wikipedia, 'ethereum classic': 'ethereum classic ... is a blockchain ... it is the unaltered, original version of the ethereum network ... following a hard fork of the ethereum foundation-supported ethereum blockchain, in response to the dao hack in 2016.', wikipedia, 'the dao (organization)' and 'ethereum classic' articles: the 2016 dao hack led to a contentious hard fork of the ethereum blockchain at block 1,920,000 to recover stolen funds; the portion of the network that rejected the fork continued as ethereum classic (etc)., wikipedia, 'the dao (organization)' and 'ethereum classic' articles: the 2016 dao hack prompted a contentious hard fork of ethereum at block 1,920,000 to recover the stolen funds; the minority that rejected the fork persisted as ethereum classic., wikipedia, 'the dao (organization)' and 'ethereum classic' articles: the 2016 dao hack prompted a contentious hard fork of ethereum to reverse the theft; the minority of nodes/miners that rejected the fork continued the original chain, which was renamed ethereum classic (etc)., wikipedia, 'the dao (organization)' and 'ethereum classic' articles: the june 2016 dao hack led to a contentious hard fork of ethereum in july 2016; the original, unforked chain was continued and renamed ethereum classic., wikipedia, 'the dao (organization)' and 'ethereum classic' articles; ethereum foundation blog post 'hard fork completed' (july 20, 2016) describing the dao hack and the resulting hard fork that split ethereum into eth and ethereum classic (etc)., www.ethereumclassic.org, www.sec.gov
Work
- Pinnedblocks 26,149,962 to 26,150,260 to on Ethereum mainnet
- Answered150 of 151 agreed140 needed#635truefrom ethereum.org#1274truefrom ethereum.org#1507truefrom ethereum.org#1310truefrom ethereum.org#462truefrom ethereum.org
146 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
- 0xae3272773bd5a6e3d5e219fec2e42f1426ff9e5721f35434b500b82efcbb019233b4ef01289f222dfaa4aef4519af8be87b3282c5fbf03dbac255b9f7bc50cbd1b
- signed panel
- 150 agreed · quorum 140 · 200 seats
- question hash
- 0x72bd2e059dc0965751a518e74138ac92782222be9adba8912074ff34a7816de7
- answer type
- bool
- consumer
- none named; signed for the zero address