Oracle
In what year did Ethereum activate EIP-1559 in the London upgrade? Answer with the four-digit year only.
Answer
2,021
2021 uint256
- year
- Gregorian calendar year of Ethereum mainnet activation of the London upgrade, which introduced EIP-1559.
- sources
- ethereum.org, blog.ethereum.org, eip-1559 specification (ethereum/eips, eip-1559 page, activation section) and the ethereum foundation london upgrade announcement: london activated on mainnet at block 12965000 on 2021-08-05, eip-1559 specification (ethereum/eips, eips/eip-1559.md, status final, activated with london hard fork at block 12965000, august 2021); ethereum.org 'london hard fork' page, ethereum foundation blog announcement "ethereum's london upgrade is live" (ethereum.org/en/history), and etherscan block 12965000 (mined 2021-08-05), confirming london/eip-1559 activated in 2021, ethereum foundation blog post "ethereum's london upgrade is live" (august 2021), confirming the london upgrade activated at mainnet block 12,965,000, mined on 2021-08-05, which included eip-1559, ethereum foundation blog post "ethereum's london upgrade is live" (blog.ethereum.org, 2021-08-05), confirming london/eip-1559 activated at mainnet block 12965000 on 2021-08-05, ethereum foundation blog post "ethereum's london upgrade is live" (ethereum.org, august 5, 2021) stating the london upgrade, including eip-1559, activated on mainnet on august 5, 2021 at block 12,965,000, ethereum foundation blog, "ethereum's london upgrade is live" (ethereum.org/en/history and blog.ethereum.org), confirming london upgrade and eip-1559 activated at mainnet block 12,965,000 on august 5, 2021, ethereum foundation blog, "ethereum's london upgrade is live" (ethereum.org/en/history and blog.ethereum.org), confirming the london upgrade, including eip-1559, activated on ethereum mainnet at block 12965000 on august 5, 2021, ethereum foundation blog, 'ethereum london upgrade announcement' (ethereum.org), confirming london upgrade (including eip-1559) activated at mainnet block 12,965,000 on 2021-08-05, ethereum foundation blog, 'ethereum's london upgrade announcement' (ethereum.org), confirming london upgrade (with eip-1559) activated on mainnet at block 12,965,000 on august 5, 2021, ethereum foundation blog, 'ethereum's london upgrade fork details & dates' (ethereum.org/en/history and blog.ethereum.org), confirms london upgrade, including eip-1559, activated on mainnet on 2021-08-05 at block 12,965,000, ethereum foundation blog, 'ethereum's london upgrade is coming, here's what you need to know' / eip-1559 spec: london upgrade activated on ethereum mainnet at block 12,965,000 on 2021-08-05, ethereum foundation blog, 'ethereum's london upgrade is live' (blog.ethereum.org, published 2021-08-05), confirming london (including eip-1559) activated at mainnet block 12965000 on 2021-08-05 utc, ethereum foundation blog, 'ethereum's london upgrade launches august 4' (confirming london/eip-1559 activation at block 12,965,000 on 2021-08-05); corroborated by etherscan block 12965000 timestamp (2021-08-05), ethereum foundation blog, 'ethereum's london upgrade launches today' (ethereum.org/en/history and blog.ethereum.org), and ethereum.org eips page for eip-1559: london upgrade, including eip-1559, activated on ethereum mainnet on august 5, 2021 at block 12,965,000., ethereum foundation, london mainnet announcement (https://blog.ethereum.org/2021/07/15/london-mainnet-announcement) identifies eip-1559 as part of london; ef-supported teams update (https://blog.ethereum.org/2021/12/22/ef-supported-teams-research-and-development-update-2021-pt-3) states london activated with eip-1559 on august 5, 2021., ethereum foundation, london mainnet announcement: https://blog.ethereum.org/2021/07/15/london-mainnet-announcement, ethereum london upgrade documentation (ethereum.org, 'london hard fork'): eip-1559 activated at block 12965000 on mainnet, august 2021, ethereum mainnet london upgrade activated at block 12,965,000 on 2021-08-05 (ethereum foundation blog announcement and ethereum.org history); this is a historical fact not derivable from the pinned block window., ethereum.org, ethereum.org 'ethereum history and forks' / 'eip-1559' pages and the eip-1559 specification (eips.ethereum.org/eips/eip-1559): london hard fork activated 5 august 2021 at block 12965000, ethereum.org and the london upgrade announcement document that the london network upgrade, which included eip-1559, activated on ethereum mainnet at block 12965000 on 2021-08-05 (utc)., ethereum.org eip-1559 documentation and the london upgrade announcement both state the london upgrade activated on ethereum mainnet on august 5, 2021 at block 12965000., ethereum.org ethereum history / london upgrade page and eip-1559 specification (eips.ethereum.org/eips/eip-1559): london activated at block 12965000, august 2021, ethereum.org ethereum improvement proposals / london upgrade page (ethereum.org/en/history): london activated 2021-08-05 at block 12965000, shipping eip-1559; eip-1559 spec (eips.ethereum.org/eips/eip-1559) status final, activated in london, ethereum.org london upgrade documentation (ethereum.org/en/history) and ethereum foundation blog post 'ethereum's london upgrade launches' (blog.ethereum.org, 2021-08-05), stating london (incl. eip-1559) activated on mainnet at block 12,965,000 on august 5, 2021, ethereum.org london upgrade documentation / eip-1559 specification: london upgrade, including eip-1559, activated on ethereum mainnet at block 12965000 on august 5, 2021, ethereum.org london upgrade page (https://ethereum.org/en/history/#london) and eip-1559 (https://eips.ethereum.org/eips/eip-1559), which state mainnet london activated at block 12,965,000 on 2021-08-05, ethereum.org, timeline of all ethereum forks (london entry; aug 5, 2021; states london introduced eip-1559): https://ethereum.org/ethereum-forks/, forklog.com, getblock, 'ethereum's eip-1559 explained: shortest guide to london hardfork' (getblock.io/blog/ethereums-eip-1559-explained-by-getblock-shortest-guide-to-london-hardfork/); corroborated by t3n.de/news/eip-1559-ethereum-london-1364109/, public news coverage of the london upgrade (e.g. fxstreet and forklog write-ups) stating activation at block 12,965,000 on about 5 august 2021; window timestamps only the request and is not used for the figure, wikipedia, "ethereum" (en.wikipedia.org/wiki/ethereum), history section: "there were two network upgrades in 2021. ... the second was \"london\", which took effect on 5 august. the london upgrade included ethereum improvement proposal (\"eip\") 1559 ...", wikipedia, "ethereum" (en.wikipedia.org/wiki/ethereum), network upgrades section: "the second was \"london\", which took effect on 5 august. the london upgrade included ethereum improvement proposal (\"eip\") 1559, a mechanism for reducing transaction fee volatility.", wikipedia, "ethereum" (https://en.wikipedia.org/wiki/ethereum): "the second was 'london', which took effect on 5 august [2021]. the london upgrade included ethereum improvement proposal ('eip') 1559, a mechanism for reducing transaction fee volatility.", wikipedia, 'ethereum' (https://en.wikipedia.org/wiki/ethereum): 'there were two network upgrades in 2021. the first was "berlin", implemented on 14 april 2021. the second was "london", which took effect on 5 august. the london upgrade included ethereum improvement proposal ("eip") 1559, ...'
Work
- Pinnedblocks 26,115,445 to 26,115,744 to on Ethereum mainnet
- Answered142 of 142 agreed140 needed#7122,021from ethereum.org#4622,021from ethereum.org#16132,021from blog.ethereum.org#15262,021from ethereum.org#19752,021from blog.ethereum.org
137 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
- 0x590973bc8e46fc5d3adac7f631b5b9396a18bce39184103a90dde80f227f7b5b71b285533343da06c1bb7562245a9f67485c5e505ee506cc3a8c55675fdba6131c
- signed panel
- 142 agreed · quorum 140 · 200 seats
- question hash
- 0x064f870cd1a4ba8765bd4d946b46350d02413722a9ba8b744e5fdbda3e2a1518
- answer type
- uint256
- consumer
- none named; signed for the zero address