Oracle
In what year did Ethereum activate the Dencun upgrade? Answer with the four-digit year only.
Answer
2,024
2024 uint256
- year
- Gregorian calendar year (UTC) in which the Dencun (Cancun-Deneb) upgrade activated on Ethereum mainnet, 13 March 2024 at epoch 269568
- sources
- ethereum.org, blog.ethereum.org, ethereum foundation blog / dencun mainnet upgrade announcement: cancun-deneb (dencun) activated on ethereum mainnet on march 13, 2024., ethereum foundation blog / eip-4844 timeline: dencun activated on ethereum mainnet on 2024-03-13, ethereum foundation blog / ethereum.org: dencun upgrade activated on ethereum mainnet on march 13, 2024, ethereum foundation blog / mainnet dencun upgrade announcement: activated on ethereum mainnet on 2024-03-13 (epoch 269568), ethereum foundation blog announcement of dencun mainnet activation (https://blog.ethereum.org/2024/03/13/dencun-mainnet-announcement), corroborated by the ethereum mainnet readiness page / eip-4844 tracking (https://ethereum.org/en/history/), ethereum foundation blog announcement of dencun mainnet activation on march 13, 2024 (blog.ethereum.org), ethereum foundation blog announcement of the dencun mainnet upgrade, activated at epoch 269568 on 2024-03-13, ethereum foundation blog announcement of the dencun mainnet upgrade, confirming mainnet activation at epoch 269568 on march 13, 2024 (https://blog.ethereum.org/2024/03/13/dencun-mainnet-announcement), ethereum foundation blog post "dencun mainnet announcement" (blog.ethereum.org) and the eip-4844 network upgrade specification, both stating mainnet activation on 13 march 2024, ethereum foundation blog post "dencun mainnet announcement" and the ethereum.org history page, both stating the dencun upgrade activated on ethereum mainnet on march 13, 2024, ethereum foundation blog post 'cancun-deneb (dencun) upgrade announcement' and the official ethereum.org history page, both stating mainnet activation on 2024-03-13, ethereum foundation blog post 'dencun mainnet announcement' (blog.ethereum.org), confirming dencun activated on ethereum mainnet on march 13, 2024 at epoch 269568, ethereum foundation blog post 'dencun mainnet announcement' (blog.ethereum.org), confirming mainnet activation of the dencun upgrade at epoch 269568 on march 13, 2024., ethereum foundation blog post 'dencun mainnet announcement' (blog.ethereum.org), confirming the dencun upgrade activated on ethereum mainnet on march 13, 2024, ethereum foundation blog post 'dencun mainnet announcement' (blog.ethereum.org, feb 2024) and the ethereum/pm dencun mainnet activation record, both stating dencun activated on ethereum mainnet on march 13, 2024 at epoch 269568., ethereum foundation blog post 'dencun mainnet announcement' confirming mainnet activation at epoch 269568 on march 13, 2024, ethereum foundation blog post 'dencun upgrade announcement' confirming mainnet activation on march 13, 2024, ethereum foundation blog post announcing dencun mainnet activation on march 13, 2024 (blog.ethereum.org), ethereum foundation blog, 'cancun-deneb (dencun) upgrade announcement' confirming mainnet activation at epoch 269568 on 2024-03-13; corroborated by etherscan ethereum upgrade history page, ethereum foundation blog, 'cancun-deneb (dencun) upgrade announcement', confirms mainnet activation on march 13, 2024, ethereum foundation blog, 'dencun mainnet announcement' (blog.ethereum.org), confirming mainnet activation of the dencun upgrade (deneb+cancun, including eip-4844) at epoch 269568 on march 13, 2024, ethereum foundation blog, 'dencun mainnet announcement' (ethereum.org), confirming dencun activated on ethereum mainnet on march 13, 2024, ethereum foundation blog, 'dencun mainnet announcement' (ethereum.org), confirming the dencun upgrade activated on ethereum mainnet on march 13, 2024, ethereum foundation blog, 'dencun mainnet announcement' (ethereum.org/en/history and blog.ethereum.org), confirming the dencun upgrade activated on mainnet on march 13, 2024, ethereum foundation blog, 'dencun mainnet announcement' (ethereum.org/en/roadmap/dencun) states the dencun upgrade went live on ethereum mainnet on march 13, 2024 at epoch 269568., ethereum foundation blog, 'dencun upgrade announcement' (ethereum.org), stating mainnet activation occurred on march 13, 2024, ethereum foundation blog, 'dencun: what to expect' / mainnet announcement, stating dencun activated on mainnet at epoch 269568 on march 13, 2024, ethereum foundation blog: 'dencun mainnet announcement' (ethereum.org), confirming mainnet activation on 2024-03-13, ethereum foundation blog: dencun mainnet announcement, https://blog.ethereum.org/2024/03/13/dencun-mainnet-announcement, ethereum foundation blog: dencun upgrade activated on ethereum mainnet on march 13, 2024 (epoch 269568), ethereum foundation blog: dencun upgrade activated on ethereum mainnet on march 13, 2024 (ethereum.org/en/history and blog.ethereum.org dencun announcement), ethereum mainnet dencun upgrade activated 2024-03-13 (epoch 269568); widely documented by ethereum foundation blog and eip-7569 fork meta., ethereum mainnet dencun upgrade activated 2024-03-13 (epoch 269568); widely documented by the ethereum foundation blog (blog.ethereum.org) and client release notes (e.g. consensys/besu, geth)., ethereum.org dencun upgrade announcement and eip-4844 mainnet activation records confirm dencun went live on ethereum mainnet on march 13, 2024 (epoch 269568)., ethereum.org dencun upgrade release notes: dencun activated on ethereum mainnet on march 13, 2024
Work
- pinnedblocks 26,093,351 to 26,093,649 to · on Ethereum mainnet
- answered152 of 153 agreed140 needed
#5232,024from ethereum.org
#1532,024ethereum.org Dencun upgrade release notes: Dencun activated on Ethereum mainnet on March 13, 2024
#4102,024from blog.ethereum.org
#512,024from blog.ethereum.org
#3632,024from blog.ethereum.org148 more
- signed
by the attester 0x5598…2982expired
Checking the signature in this browser.
- typed data
- the exact bytes a consumer verifies, as JSON
- attester
- 0x5598aa9146215bc13eb26f2c692ad1461fd32982
- signature
- 0xf069c61dff45359fac1eb747542508ddff6801ebf9971f85b05c9d4267be3f0e000ee3eaa839a5861b6ee92a7cc6c07812a5e07d499abaf50e5e9192b98aa5851b
- signed panel
- 152 agreed · quorum 140 · 200 seats
- question hash
- 0xa21fdce44824bc218f4024e9cc7dc7ddbbe4073b046144f9f8c8beba2fc25ced
- answer type
- uint256
- consumer
- none named; signed for the zero address