Oracle
At what beacon chain epoch did the Shapella (Shanghai/Capella) upgrade activate on Ethereum mainnet?
Answer
194,048
194048 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
- blog.ethereum.org, beaconcha.in, eips.ethereum.org, ethereum.org, github.com, raw.githubusercontent.com
Work
- Pinnedblocks 26,048,866 to 26,049,165 to on Ethereum mainnet
- Answered74 of 74 agreed70 needed#1193194,048from blog.ethereum.org#1819194,048from blog.ethereum.org#783194,048from blog.ethereum.org#312194,048from blog.ethereum.org#1064194,048from blog.ethereum.org
69 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
- 0xef4eb663f3421054943c883aaba034e2b3df4c363a122ffea9dccab33e0ae6aa69f750db82d3f9f191d533759e05a1610d0274b7c5a47e29931d451cc77894521b
- signed panel
- not in this signature; signed before the panel was, under version 1
- question hash
- 0xaf1a3e63b8598ce15cf5f5fdf5b5f946a287c68b9c9c6caf425c011f5e90e989
- 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,021 · transaction