Oracle
At what block number did the Spurious Dragon upgrade activate on Ethereum mainnet?
Answer
2,675,000
2675000 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
- raw.githubusercontent.com, blog.ethereum.org, eip-607 (hardfork meta: spurious dragon), ethereum eips repository, https://eips.ethereum.org/eips/eip-607 — specifies mainnet activation at block 2,675,000; corroborated by ethereum.org's history of hard forks page listing spurious dragon at block 2675000., eip-607 (hardfork meta: spurious dragon), ethereum eips repository, specifies activation at block 2,675,000 on ethereum mainnet; corroborated by ethereum.org/en/history/ which lists the spurious dragon upgrade at block 2675000 (2016-11-22)., eip-607 (hardfork meta: spurious dragon), ethereum/eips repository, and ethereum.org history page - both list the spurious dragon fork's mainnet activation at block 2675000, eip-607 (hardfork meta: spurious dragon), ethereum/eips repository, and ethereum.org's history of ethereum upgrades page both state the spurious dragon fork activated on ethereum mainnet at block 2675000., eip-607 (hardfork meta: spurious dragon), ethereum/eips repository, https://eips.ethereum.org/eips/eip-607 — states activation at ethereum mainnet block 2,675,000; corroborated by ethereum.org's history of hard forks page (ethereum.org/en/history), which lists spurious dragon at block 2675000 on 2016-11-22., eip-607 (hardfork meta: spurious dragon), ethereum/eips repository, states the spurious dragon hard fork activated on ethereum mainnet at block 2,675,000. this is corroborated by ethereum.org's history of hard forks page, which lists the same activation block., eip-607 (hardfork meta: spurious dragon), https://eips.ethereum.org/eips/eip-607 — 'activation: block >= 2,675,000 on mainnet'; corroborated by ethereum.org's history of hard forks page (ethereum.org/en/history) listing spurious dragon at block 2,675,000 (2016-11-22)., eip-607 (hardfork meta: spurious dragon), https://eips.ethereum.org/eips/eip-607, which specifies activation at ethereum mainnet block 2,675,000; corroborated by ethereum.org's history of hard forks page (ethereum.org/en/history)., eip-607 (https://eips.ethereum.org/eips/eip-607) and ethereum.org/en/history/, both stating the spurious dragon hard fork activated at ethereum mainnet block 2,675,000, eip-607 (https://eips.ethereum.org/eips/eip-607), 'hardfork meta: spurious dragon' (activation: block >= 2,675,000 on mainnet); corroborated by eip-6953 (https://eips.ethereum.org/eips/eip-6953)., eip-607, ethereum improvement proposals: https://eips.ethereum.org/eips/eip-607 ; hard fork no. 4: spurious dragon, ethereum foundation blog: https://blog.ethereum.org/2016/11/18/hard-fork-no-4-spurious-dragon, eips.ethereum.org, ethereum eip repository, eip-608 (hardfork meta: spurious dragon), which lists 'activation: at block 2,675,000, mainnet' for ethereum mainnet; corroborated by ethereum.org's history of ethereum page listing the spurious dragon upgrade at block 2,675,000., ethereum foundation blog, hard fork no. 4: spurious dragon (https://blog.ethereum.org/2016/11/18/hard-fork-no-4-spurious-dragon), ethereum foundation eip-6953 — network upgrade activation triggers: https://eips.ethereum.org/eips/eip-6953, ethereum foundation, hard fork no. 4: spurious dragon (https://blog.ethereum.org/2016/11/18/hard-fork-no-4-spurious-dragon); ethereum improvement proposals, eip-6953 (https://eips.ethereum.org/eips/eip-6953), ethereum improvement proposals, eip-607: hardfork meta: spurious dragon — https://eips.ethereum.org/eips/eip-607, ethereum.org, ethereum.org hard fork history (ethereum.org/en/history) and eip-607 (hardfork meta: spurious dragon), both stating spurious dragon activated at mainnet block 2675000, ethereum.org hard fork history (ethereum.org/en/history) lists spurious dragon as activated at block 2,675,000 on 2016-11-22, matching eip-607's specification of the spurious dragon fork activation block., ethereum.org hard fork history (ethereum.org/en/history/) and the ethereum eip repository, both listing spurious dragon activation at mainnet block 2675000, ethereum.org history of ethereum hard forks (https://ethereum.org/en/history/), which lists the spurious dragon upgrade as activating at block 2,675,000 on ethereum mainnet., ethereum.org history of ethereum page (ethereum.org/en/history) and eip-155 / eip-160 specifications, which both list the spurious dragon hard fork as activating on ethereum mainnet at block 2,675,000 (2016-11-22)., ethereum.org history of ethereum page (ethereum.org/en/history) lists the spurious dragon upgrade as activated at block 2,675,000 on 2016-11-22; this matches eip-608 (hardfork meta: spurious dragon), which specifies activation at block 2,675,000 on ethereum mainnet., ethereum.org history of ethereum upgrades (ethereum.org/en/history) and the go-ethereum mainnet chain config (params/config.go, eip158block), both stating the spurious dragon (eip-150/158/160/161) hard fork activated at mainnet block 2,675,000 on 2016-11-22., ethereum.org history of forks (ethereum.org/en/history) and go-ethereum's params/config.go mainnetchainconfig, both of which document the spurious dragon hard fork (eip-150/158/160/161) activating on ethereum mainnet at block 2675000, ethereum.org history of forks page (ethereum.org/en/history) and eip-155/eip-161 specifications, which list the spurious dragon fork as activated on ethereum mainnet at block 2,675,000., ethereum.org history of hard forks (ethereum.org/en/history) and eip-155 specification, both stating spurious dragon activated on ethereum mainnet at block 2,675,000, ethereum.org history of hard forks (ethereum.org/en/history) and eip-607 (hardfork meta: spurious dragon, eips.ethereum.org/eips/eip-607), both of which state the spurious dragon fork activated at ethereum mainnet block 2,675,000., ethereum.org history of hard forks (ethereum.org/en/history) lists spurious dragon activating at block 2,675,000 on 2016-11-22; corroborated by the ethereum execution-specs repository (ethereum/execution-specs, spurious_dragon fork config), which records the mainnet activation block as 2675000., ethereum.org history of hard forks (ethereum.org/en/history/) and eip-607 (hardfork meta: spurious dragon), both stating spurious dragon activated at block 2675000 on ethereum mainnet, ethereum.org history of hard forks (https://ethereum.org/en/history/) lists spurious dragon activation at block 2,675,000, mined 2016-11-22; corroborated by eip-155 and eip-608 (hardfork meta: spurious dragon) in the ethereum/eips repository, which specify the same activation block., ethereum.org history of hard forks page (ethereum.org/en/history) lists spurious dragon activating at mainnet block 2,675,000 on 2016-11-22, consistent with the eip-607 (hardfork meta: spurious dragon) specification in the ethereum eips repository., ethereum.org history of hard forks page (https://ethereum.org/en/history/), which lists the spurious dragon upgrade as activated at block 2675000 on ethereum mainnet (2016-11-22), bundling eip-150, eip-155, eip-160 and eip-161., ethereum.org history of network upgrades (ethereum.org/en/history) and the ethereum eips repository (eips.ethereum.org, eip-155/eip-607 meta), both stating the spurious dragon hard fork activated at mainnet block 2,675,000 (2016-11-22)., ethereum.org history page (ethereum.org/en/history) and ethereum core devs' eip-155/eip-158 meta docs, which list the spurious dragon hard fork as activated at mainnet block 2,675,000 on 2016-11-22, ethereum.org, history of ethereum network upgrades (https://ethereum.org/en/history/), which lists the spurious dragon upgrade as activating at block 2675000 on 2016-11-22, alongside the go-ethereum eip-155/eip-160/eip-161/eip-170 fork-block constants that also fix mainnet spurious dragon activation at block 2675000., ethereum.org/en/history (ethereum mainnet fork history) and eip-155 (simple replay attack protection), both list spurious dragon as activating at block 2,675,000 on mainnet., ethereum.org/en/history (ethereum protocol upgrade history) and go-ethereum params/config.go mainnet chain config, both list the spurious dragon hard fork activation at mainnet block 2,675,000 (2016-11-22), also documented in eip-155/eip-160/eip-161/eip-170, ethereum.org/en/history (ethereum protocol upgrade history): spurious dragon activated at mainnet block 2,675,000 on 2016-11-22, alongside eip-155, eip-160, eip-161, eip-170., etherscan.io
Work
- pinnedblocks 26,062,077 to 26,062,375 to · on Ethereum mainnet
- answered148 of 148 agreed140 needed
#8092,675,000from raw.githubusercontent.com
#7092,675,000from eips.ethereum.org
#19192,675,000from eips.ethereum.org
#15092,675,000from eips.ethereum.org
#11992,675,000ethereum.org hard fork history (ethereum.org/en/history/) and the Ethereum EIP repository, both listing Spurious Dragon activation at mainnet block 2675000143 more
- 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
- 0x33791b7795bf349bd228227f58278118ae90f6a1fbb7540e7a5f8334f3ab01fe57b409dd719259b1161ef2cd98bc1510bf1fce3744f8655ece410e6c7a1220921b
- question hash
- 0xcdc63c08a3ff86879af23b06bbc424e11400ff40726a0dece306ce69894e39ee
- answer type
- uint256
- consumer
- none named; signed for the zero address
- scored
1 batch queuedon Ethereum mainnet
- scores
- settled, waiting for the batcher