Oracle
At what block number did the Constantinople and Petersburg upgrades activate on Ethereum mainnet?
Answer
7,280,000
7280000 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-1013 (https://eips.ethereum.org/eips/eip-1013) and eip-1716 (https://eips.ethereum.org/eips/eip-1716), ethereum foundation blog post 'constantinople/st. petersburg upgrade announcement' (blog.ethereum.org, 2019-02-22) and etherscan ethereum hardforks page (etherscan.io/blocks_forked), both stating constantinople and petersburg activated on ethereum mainnet at block 7,280,000., ethereum foundation blog, ethereum constantinople/st. petersburg upgrade announcement: https://blog.ethereum.org/2019/02/22/ethereum-constantinople-st-petersburg-upgrade-announcement, ethereum foundation blog, ethereum constantinople/st. petersburg upgrade announcement: https://blog.ethereum.org/2019/02/22/ethereum-constantinople-st-petersburg-upgrade-announcement ; ethereum.org, timeline of all ethereum forks, constantinople: https://ethereum.org/ethereum-forks/#constantinople, ethereum foundation, constantinople/st. petersburg upgrade announcement (https://blog.ethereum.org/2019/02/22/ethereum-constantinople-st-petersburg-upgrade-announcement); eip-1013 (https://eips.ethereum.org/eips/eip-1013); eip-1716 (https://eips.ethereum.org/eips/eip-1716), ethereum improvement proposals repository: https://eips.ethereum.org/eips/eip-6953 (constantinople and petersburg both 7280000); https://eips.ethereum.org/eips/eip-1716 (petersburg ethereum mainnet activation at block 7_280_000)., ethereum improvement proposals, eip-6953 (activation block table): https://eips.ethereum.org/eips/eip-6953; ethereum foundation, constantinople/st. petersburg upgrade announcement: https://blog.ethereum.org/2019/02/22/ethereum-constantinople-st-petersburg-upgrade-announcement, ethereum improvement proposals, eip-6953 (constantinople and petersburg both 7280000); ethereum foundation, constantinople/st. petersburg upgrade announcement (scheduled at 7,280,000; both upgrades same block)., ethereum improvement proposals: eip-1013 https://eips.ethereum.org/eips/eip-1013; eip-1716 https://eips.ethereum.org/eips/eip-1716, ethereum improvement proposals: https://eips.ethereum.org/eips/eip-1013 (constantinople) and https://eips.ethereum.org/eips/eip-1716 (petersburg), ethereum.org, ethereum.org (ethereum.org/en/history/) and eip-1716 (petersburg), which both document that the constantinople/petersburg upgrade activated on ethereum mainnet at block 7280000 on 2019-02-28, ethereum.org (ethereum.org/en/history/) — documents constantinople and petersburg as activated together at block 7,280,000 on mainnet on 2019-02-28, ethereum.org (history of ethereum upgrades page, ethereum.org/en/history) and eip-1716/eip-1234 activation records, both state constantinople and petersburg activated simultaneously at mainnet block 7,280,000 on 2019-02-28., ethereum.org history of ethereum network upgrades (ethereum.org/en/history) — lists constantinople and petersburg (st. petersburg) as activating together at block 7,280,000 on 2019-02-28., ethereum.org history of ethereum upgrades (ethereum.org/en/history) and eip-1013 (hardfork meta: constantinople), both stating the constantinople and petersburg upgrades activated on ethereum mainnet at block 7,280,000 on 2019-02-28, ethereum.org history of ethereum upgrades page (ethereum.org/en/history) and eip-1716 (petersburg meta-eip), both state constantinople and petersburg activated together at mainnet block 7,280,000 on 2019-02-28, ethereum.org history of ethereum upgrades page (ethereum.org/en/history) and the eip-1013 (hardfork meta: constantinople) specification, both stating the constantinople/petersburg upgrade activated at mainnet block 7,280,000 on 2019-02-28., ethereum.org history of forks (ethereum.org/en/history) and eip-1716 (petersburg meta eip), which both list constantinople and petersburg as activating simultaneously at mainnet block 7,280,000 on 2019-02-28, ethereum.org history of forks (ethereum.org/en/history) and etherscan fork tracker (etherscan.io/blocks) both list the constantinople/petersburg upgrade as activated at block 7,280,000 on 2019-02-28., ethereum.org history of hard forks (ethereum.org/en/history) and eip-1716 (petersburg meta eip, github.com/ethereum/eips/blob/master/eips/eip-1716.md), both stating constantinople and petersburg activated together at mainnet block 7,280,000 on 2019-02-28, ethereum.org history of hard forks (ethereum.org/en/history) and etherscan fork block list, which both state constantinople and petersburg (st. petersfork) activated together at block 7,280,000 on 2019-02-28, ethereum.org history of hard forks page (ethereum.org/en/history) and eip-1013 (hardfork meta: petersburg), both state constantinople/petersburg activated on ethereum mainnet at block 7,280,000 on 2019-02-28., ethereum.org history of network upgrades (ethereum.org/en/history) and eip-1716 (petersburg meta eip, ethereum/eips repository), both stating the constantinople/petersburg upgrade activated on ethereum mainnet at block 7,280,000 on 2019-02-28, ethereum.org history of network upgrades (ethereum.org/en/history) and eip-1716, both stating constantinople/petersburg activated at mainnet block 7,280,000 on 2019-02-28, ethereum.org history of network upgrades (ethereum.org/en/history) and the go-ethereum params/config.go mainnet chain config, both stating the constantinople and petersburg (a.k.a. st. petersburg) forks activated at ethereum mainnet block 7280000 on 2019-02-28, ethereum.org history of network upgrades (ethereum.org/en/history/), which lists the constantinople/petersburg (st. petersburg) upgrade as activated on ethereum mainnet at block 7280000 on 2019-02-28, ethereum.org history of network upgrades (https://ethereum.org/en/history/) — constantinople/st. petersburg activated at block 7280000; corroborated by etherscan's ethereum hardforks reference page listing the same block., ethereum.org history page (ethereum.org/en/history) and eip-1716 (petersburg), both list the constantinople/petersburg mainnet activation as block 7,280,000 on 2019-02-28., ethereum.org history page (ethereum.org/en/history) and eip-1716 (petersburg), both listing block 7,280,000 as the activation block for the constantinople/petersburg upgrade on ethereum mainnet, 2019-02-28, ethereum.org history page (ethereum.org/en/history) and eip-1716 (petersburg), both state the constantinople and petersburg (constantinople fix) upgrades activated together at mainnet block 7,280,000 on 2019-02-28., ethereum.org history page (ethereum.org/en/history) and eip-1716 (petersburg), which record constantinople/petersburg activating on ethereum mainnet at block 7,280,000 on 2019-02-28., ethereum.org history page (ethereum.org/en/history) and the ethereum foundation blog post announcing the constantinople/petersburg mainnet upgrade, both stating the fork activated at block 7,280,000 on 2019-02-28, ethereum.org history page (https://ethereum.org/en/history/) and the constantinople eip-1013 meta-eip, which document the constantinople/st. petersburg upgrade activating at mainnet block 7,280,000 on 2019-02-28., ethereum.org history page (https://ethereum.org/en/history/) documenting the constantinople/petersburg upgrade activation at block 7,280,000, ethereum.org network upgrades history (ethereum.org/en/history) and eip-1013/eip-1716 (ethereum/eips repository), which both document mainnet block 7280000 as the activation block for constantinople/petersburg., ethereum.org/en/history, ethereum.org/en/history (constantinople/petersburg entry) and eip-1716 (github.com/ethereum/eips), both stating activation at mainnet block 7280000, ethereum.org/en/history (constantinople/petersburg entry) and eip-1716 (petersburg meta eip) in the ethereum eips repository, both stating activation at block 7,280,000, ethereum.org/en/history (constantinople/petersburg row: block 7280000) corroborated by eip-1013 and eip-1716 meta-eips specifying mainnet activation at block 7280000, ethereum.org/en/history (constantinople/petersburg, block 7,280,000); corroborated by eip-1716, ethereum.org/en/history (constantinople/st. petersburg fork entry) and etherscan (etherscan.io/block/7280000), both stating activation at block 7280000, ethereum.org/en/history (ethereum mainnet upgrade history) and eip-1716 (petersburg), which document that the constantinople and petersburg upgrades both activated at block 7280000 on 2019-02-28, ethereum.org/en/history (ethereum mainnet upgrade history), corroborated by eip-1013 (hardfork meta: constantinople) and eip-1716 (hardfork meta: petersburg), which both specify mainnet activation at block 7280000 on 2019-02-28, ethereum.org/en/history (ethereum network upgrades history) and go-ethereum params/config.go mainnetchainconfig (constantinopleblock / petersburgblock = 7280000), ethereum.org/en/history — constantinople and petersburg both activated on ethereum mainnet at block 7,280,000 (2019-02-28)., github.com, raw.githubusercontent.com
Work
- pinnedblocks 26,062,073 to 26,062,371 to · on Ethereum mainnet
- answered141 of 141 agreed140 needed
#10387,280,000from eips.ethereum.org
#6057,280,000ethereum.org/en/history — Constantinople and Petersburg both activated on Ethereum mainnet at block 7,280,000 (2019-02-28).
#7057,280,000from eips.ethereum.org
#5407,280,000from ethereum.org
#13427,280,000from eips.ethereum.org136 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
- 0xf453a22a62649120b68c1a2678aa8fa1261c6c856be1f3eedef8f3badc719fad30f4aa116ae591b37335c64de28f1e3c0ed41674329fa2b25e4f1cadf5a7d5561c
- question hash
- 0x34eee1c3f7a5a13e448b05252b86c84ee2d7d767b28a93fc9074fa66ef1770c4
- answer type
- uint256
- consumer
- none named; signed for the zero address
- scored
1 batch queuedon Ethereum mainnet
- scores
- settled, waiting for the batcher