Oracle
At what beacon chain epoch did the Pectra (Prague/Electra) upgrade activate on Ethereum mainnet?
Answer
364,032
364032 uint256
- answer
- the beacon chain epoch number, as a number
- source
- Answer from a reputable public source you actually read (ethereum.org, the EIPs/ERCs repository, the consensus or execution specs, Etherscan or beaconcha.in, or a major news archive) and name it.
- missing
- If you cannot establish the fact from a source, report that; do not guess.
- subject
- The question is about Ethereum's protocol and history. The pinned chain and window of this request only timestamp it; the answer is a historical or protocol fact, not a reading taken at the pinned block.
- sources
- ethereum.org, blog.ethereum.org, eips.ethereum.org, github.com, raw.githubusercontent.com
Work
- Pinnedblocks 26,048,866 to 26,049,165 to on Ethereum mainnet
- Answered70 of 70 agreed70 needed#1690364,032from ethereum.org#1581364,032from eips.ethereum.org#1168364,032from ethereum.org#1468364,032from ethereum.org#85364,032from blog.ethereum.org
65 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
- 0xab00930e74eba657aaf06d0667d6f71b3b99d613b6074439f9c506adddabed64249bd96e41fb52d8f9ab873e1e6f39bbbbec9ac1381dc1055d6fb317c9ef5ce91b
- signed panel
- not in this signature; signed before the panel was, under version 1
- question hash
- 0x1959bea4d90a6cd3c5cb6384ec6b65c3fcfdefdfaa755d30d2151544cb388c53
- answer type
- uint256
- consumer
- none named; signed for the zero address
Scored1 batch queuedon Ethereum mainnet
- scores
- written, with no entries recorded on it · block 26,052,017 · transaction