Oracle
At what block number did the DAO hard fork occur on Ethereum mainnet?
Answer
1,920,000
1920000 uint256
- answer
- the number, as a whole number with no separators
- source
- Answer from a reputable public source you actually read (ethereum.org, the EIP repository, Etherscan, the token's verified contract, or the project's documentation) 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 Ethereum mainnet and its on-chain history. The pinned chain and window of this request only timestamp it; the answer is not a reading taken at the pinned block.
- sources
- eips.ethereum.org, blog.ethereum.org, eip-779 (ethereum eip repository, eips.ethereum.org/eips/eip-779), which specifies the dao hard fork activated at block 1,920,000 on ethereum mainnet; corroborated by etherscan block 1920000 (mined 2016-07-20), labeled as the dao fork block., eip-779 (hardfork meta: dao fork), eips.ethereum.org/eips/eip-779, which specifies the dao fork activation block as 1920000 on ethereum mainnet; corroborated by etherscan block 1920000 (mined 2016-07-20) labeled as the dao fork block., eip-779 (https://eips.ethereum.org/eips/eip-779), 'hardfork meta: dao fork', states the fork block number is 1920000; corroborated by etherscan block 1920000 (https://etherscan.io/block/1920000), which is labeled as the dao hard fork block., eip-779 (https://eips.ethereum.org/eips/eip-779), 'hardfork meta: dao fork', which states the fork block number is 1,920,000; corroborated by ethereum.org's history documentation of the 2016 dao hard fork., eip-779 (https://eips.ethereum.org/eips/eip-779), which specifies execution at the beginning of block 1920000; corroborated by ethereum.org ethereum forks (https://ethereum.org/ethereum-forks/), dao fork timeline listing block 1,920,000., eip-779 (https://eips.ethereum.org/eips/eip-779), which specifies the dao hard fork activated at ethereum mainnet block 1,920,000; corroborated by etherscan's block explorer entry for block 1920000., eip-779 (https://eips.ethereum.org/eips/eip-779), which specifies the fork action at the beginning of block 1920000; corroborated by ethereum.org timeline (https://ethereum.org/ethereum-forks/), which lists dao fork block 1,920,000., eip-779 (https://eips.ethereum.org/eips/eip-779); ethereum.org ethereum forks timeline (https://ethereum.org/ethereum-forks/), eip-779 (the hard-forked fork support): specifies the dao hard fork state changes were applied at ethereum mainnet block 1,920,000 (https://eips.ethereum.org/eips/eip-779). corroborated by etherscan's block explorer, which labels block 1920000 as the dao fork block., eip-779, hardfork meta: dao fork, specification (https://eips.ethereum.org/eips/eip-779): activation — block == 1,920,000 on mainnet., eip-779, https://eips.ethereum.org/eips/eip-779 (states activation at the beginning of block 1920000); ethereum.org, https://ethereum.org/ethereum-forks/ (lists dao fork block number 1,920,000)., ethereum foundation blog post "to fork or not to fork" (blog.ethereum.org) and etherscan block explorer, both of which document that the dao hard fork (geth/parity client rule change per the dao wars eip) activated at block 1,920,000 on ethereum mainnet., ethereum foundation blog post 'hard fork completed' (blog.ethereum.org, july 2016) and etherscan block explorer, which both document that the dao hard fork (eip-779) was executed at block 1,920,000 on ethereum mainnet., ethereum improvement proposals, eip-779: hardfork meta: dao fork, specification (https://eips.ethereum.org/eips/eip-779); corroborated by ethereum foundation blog, hard fork completed, july 20, 2016 (https://blog.ethereum.org/2016/07/20/hard-fork-completed)., ethereum improvement proposals, eip-779: https://eips.ethereum.org/eips/eip-779; ethereum foundation, hard fork completed: https://blog.ethereum.org/2016/07/20/hard-fork-completed, ethereum.org, ethereum.org (history of ethereum: the dao fork) and eip-779 (hardfork meta: dao fork), both stating the dao hard fork occurred at block 1920000, ethereum.org history (https://ethereum.org/en/history/) and eip-779 (hardfork meta: dao fork), both stating the dao hard fork activated at block 1920000, ethereum.org history of ethereum page (ethereum.org/en/history) states the dao hard fork occurred at block 1,920,000 on 2016-07-20; corroborated by etherscan block 1920000 (mined 2016-07-20), which is the well-documented fork block., ethereum.org history page (dao fork, block 1,920,000); confirmed via mainnet rpc: block 0x1d4c00 (1920000) extradata is 'dao-hard-fork', ethereum.org history page (ethereum network upgrades: dao fork, block 1,920,000, july 20 2016), ethereum.org history page (ethereum.org/en/history) and etherscan block 1920000 (https://etherscan.io/block/1920000), which document that the dao hard fork (implemented via the client software change, no dedicated eip number since it predates the eip process) activated at ethereum mainnet block 1,920,000 on 2016-07-20., ethereum.org history page (ethereum.org/en/history) and etherscan block 1920000, which is documented as the dao hard fork block on ethereum mainnet (2016-07-20)., ethereum.org history page (ethereum.org/en/history) and etherscan block explorer (etherscan.io/block/1920000), both documenting that the dao hard fork (ethereum improvement proposal, activated via geth/parity client software fork) occurred at mainnet block 1,920,000 on 2016-07-20., ethereum.org history page (ethereum.org/en/history) states the dao fork occurred at block 1,920,000 on 2016-07-20; corroborated by etherscan block 1920000., ethereum.org history page (ethereum.org/en/history) states the dao hard fork occurred at block 1,920,000 on 2016-07-20; this is corroborated by etherscan's block explorer entry for block 1920000., ethereum.org history page (https://ethereum.org/en/history/) and the go-ethereum client source (params/config.go, daoforkblock), both stating the dao hard fork occurred at block 1,920,000 on 2016-07-20, ethereum.org history page (https://ethereum.org/en/history/) states the dao fork occurred at block 1920000 on 2016-07-20; corroborated by etherscan block 1920000 which is labeled as the dao hard fork block., ethereum.org history page (https://ethereum.org/en/history/) states the dao hard fork occurred at block 1,920,000 on 2016-07-20; this is corroborated by etherscan's block explorer showing block 1920000 as the fork block., ethereum.org, timeline of all ethereum forks (https://ethereum.org/ethereum-forks/), dao fork entry; eip-779: hardfork meta: dao fork (https://eips.ethereum.org/eips/eip-779), which specifies the action at the beginning of block 1920000., ethereum.org/en/history ("dao fork", july 20, 2016, block 1,920,000); corroborated by eip-779 ("hardfork meta: dao fork"), which specifies the fork activates at block 1920000 on mainnet., ethereum.org/en/history (dao hard fork entry, block 1,920,000), corroborated by etherscan block 1920000 label, ethereum.org/en/history (ethereum history timeline) and eip-779 (github.com/ethereum/eips/blob/master/eips/eip-779.md), both stating the dao hard fork occurred at block 1,920,000, ethereum.org/en/history (ethereum history timeline) and eip-779 (hardfork meta: dao fork), both stating the dao hard fork occurred at block 1,920,000, etherscan (etherscan.io/block/1920000) and ethereum.org history page, both stating the dao hard fork occurred at block 1920000, etherscan (etherscan.io/block/1920000) and the ethereum foundation blog post 'hard fork completed' (blog.ethereum.org), both stating the dao hard fork occurred at block 1920000 on 2016-07-20., etherscan block 1920000 (https://etherscan.io/block/1920000) and ethereum.org's history of ethereum page, both stating the dao hard fork activated at block 1,920,000 on 2016-07-20., etherscan block 1920000 (mined 2016-07-20 13:20:40 utc, marked as 'dao: hard fork'), corroborated by the go-ethereum source code constant daoforkblocknumber = 1920000 in params/config.go, which every mainnet ethereum client hard-coded to execute the dao irregular state change at that block., etherscan block 1920000 (mined 2016-07-20) is documented as the dao hard fork block; corroborated by the ethereum wiki / go-ethereum dao-fork release notes and go-ethereum's params/config.go daoforkblock constant, which sets it to 1,920,000., etherscan block 1920000 (mined 2016-07-20), documented as the dao hard fork block; corroborated by the go-ethereum client's daoforkblock constant (params/config.go, mainnetchainconfig.daoforkblock = 1920000)., etherscan block explorer, block 1920000 (mined 2016-07-20), documented as the dao hard fork block; corroborated by the ethereum foundation's official blog post 'hard fork completed' (blog.ethereum.org, 2016-07-20) and the go-ethereum/eip historical records listing daoforkblock = 1920000., etherscan.io, raw.githubusercontent.com
Work
- Pinnedblocks 26,062,073 to 26,062,371 to on Ethereum mainnet
- Answered151 of 151 agreed140 needed#19371,920,000from eips.ethereum.org#8351,920,000from eips.ethereum.org#8711,920,000Etherscan block explorer, block 1920000 (mined 2016-07-20), documented as the DAO hard fork block; corroborated by the Ethereum Foundation's official blog post 'Hard Fork Completed' (blog.ethereum.org, 2016-07-20) and the go-ethereum/EIP historical records listing DAOForkBlock = 1920000.#5271,920,000from ethereum.org#11741,920,000from eips.ethereum.org
146 more
Signedby the attester 0x5598…2982expired
Checking the signature in this browser.
- typed data
- the exact bytes a consumer verifies, as JSON
- attester
- 0x5598aa9146215bc13eb26f2c692ad1461fd32982
- signature
- 0x77a2c8e1d1b2a48611301892662e1f738c26054a5ea09b4e7fd2f9d139663204629900e1a273866b7a0e2eb2ca71e69aca325713879a69c180311e5ff75650a31b
- signed panel
- not in this signature; signed before the panel was, under version 1
- question hash
- 0x61ca4246d384b8928d1d574d6679f0bf2828dc5176ca833b8a8f645299740fd9
- answer type
- uint256
- consumer
- none named; signed for the zero address