V1.11.5 Geth v1.11.5 enables the Shanghai upgrade on Wednesday, April 12, 2023 10:27:35 PM UTC The Shanghai upgrade contains the following EIPs: EIP-3651: Warm COINBASE EIP-3855: PUSH0 instruction EIP-3860: Limit and meter initcode EIP-4895: Beacon chain push withdrawals as operations

Goerli TX DOS post-mortem First reported 8:40 CET by @jcksie & Jakub from Status on the ETH R&D discord and subsequently confirmed by Pari from EF devops CPU usage suddenly spiked at 1am CEST on all geth nodes on goerli. Both Disk writes and Reads increased significantly as well as Ingress and Egress for all geth nodes. Unfortunately the geth team does not have goerli nodes within our own grafana instance, so we had to rely on EF devops to look into the issue. EF devops does not support all of the very geth specific metrics, since they are based on influx not prometheus. I had a hunch that it was because of txpool churn. @ding_wanning and I worked on a PR to mitigate some DOS issues during the Protocol Fellowship: https://github.com/ethereum/go-ethereum/pull/26648

Number Reason Accepted Rejected Not seen 1 Basefee Besu, Geth

The following test case was generated by the fuzzer so it looks a bit funky. The genesis block can be created with the following config: { "config": { "chainId":1, "homesteadBlock":0, "eip150Block":0, "eip155Block":0, "eip158Block":0, "byzantiumBlock":0,

Similar doc to the one we had for the merge. Trying to track all initiatives of all clients. Useful Links EL spec: https://eips.ethereum.org/EIPS/eip-4895 CL spec: https://github.com/ethereum/consensus-specs/blob/dev/specs/capella/beacon-chain.md Static EL test vectors: https://hackmd.io/PqZgMpnkSWCWv5joJoFymQ EL engine api fuzzer: https://github.com/MariusVanDerWijden/merge-fuzz/tree/withdrawals Status

Geth v1.10.23 is a hotfix release to patch an issue with v1.10.22. This release enables the Merge for the Ethereum mainnet. Users that have updated their nodes to geth v1.10.22 might need to revert some of their blocks via debug_setHead(blocknumber)in the console or curl -X POST -H "Content-Type: application/json" --data '{"jsonrpc":"2.0","method":"debug_setHead","params":["blocknumber"],"id":67}' localhost:8545 (requires the debug namespace to be exposed via http). The blocknumber should be chosen to be before the update to v.1.10.23 e.g. 0xEAC1A8. Users can also choose to resync their state (while leaving the history intact). Bug fixes This release actually fixes two issue, one has been in the code for a long time. A race condition could leave the database in a weird state where a block was available while it's header was not. The other issue was merged in the recent release while refactoring the trie comitter. The Trie nodes are written into memory in a certain order and they have to be flushed onto disk in the same order. The refactor changed the order of the nodes when flushed to disk resulting in some nodes not being updated. For a full rundown of the changes please consult the Geth 1.10.23 release milestone

Geth v1.10.21 is a maintenance release, adding built-in configuration for the merge fork on the Goerli testnet and the mergeNetsplitBlock for Sepolia Specifically, this release defines a terminal total difficulty for Goerli as 10_790_000 #25324 and defines the mergeNetsplitBlock as 1735371 for Sepolia #25372. Geth command changes Fixes for a few regressions wrt. CLI parameters #25234 Forcefully shutdown the HTTP server after timeout #25258 Remove version field from RPC APIs #25096 Changes to snap sync in preparation for PBSS (Path-based state storage) #24898

Use the following command to override the Terminal Total Difficulty (TTD) in your client. Note: the current value of 50000000000000000 will be changed on June 3, 2022 to a TTD expected to be hit around June 8, 2022. Geth To override TTD in geth we should start the node with: --override.terminaltotaldifficulty 50000000000000000. Nethermind To override TTD in Nethermind we should start the node with:

Hey all, I thought a bit about the structure of the program. Given the number of people who showed interest in helping us test, I tried to define three different tracks. This does not mean that you have to decide for one of them. It's just meant to be an easier way for people to get started. I will not really provide tasks, but I will provide suggestions on what things can be worked on. General Information The program should be pretty self-guided. You decide how much time and effort you want to spend. Every little bit helps! I will try to answer questions as much as possible and try to guide the program a bit. I will also collect important edge cases that we should test. If you think about edge cases to test, send them to me. I will add them to this document. A great writeup with additional ideas for tests is here: https://hackmd.io/@n0ble/merge-test-plan

Tracking for most of the topics listed here: https://github.com/ethereum/eth2.0-devops/milestone/4 Tooling Grafana List Eth1 heads (find unsynced nodes) List nodes that missed proposals Command to find the proposer index for a slot

Note: We've updated this doc to have information for the kintsugi devnet as best we could, please let us know if you find any stale information. Please find the information about the latest branch/image to use here: https://notes.ethereum.org/@ExXcnR0-SJGthjz1dwkA1A/HkJ8Aolct Docker Clone the repository: https://github.com/parithosh/consensus-deployment-ansible Ensure docker and docker-compose is installed: docker-compose --version and `docker --version If your version of docker does not work try with docker-compose 1.25.4 and docker 20.10.12.

Prerequisite: https://hackmd.io/dFzKxB3ISWO8juUqPpJFfw Once you have your node up and running, you can connect metamask to your local node Open metamask and click on add network. Now you can put in the following parameters: Name: kintsugi RPC-URL: http://127.0.0.1:8545 Chain-ID: 1337702

This is a collection of edge cases we should write tests for that I thought about while reviewing our implementation in geth. Static test cases Reject a block with uncles What should happen if we produce a block too far into the future? Test extradata > 32 byte Test ConsensusValidated/ForkChoiceUpdated with block < TTD Test reorging over the TTD boundary when the chain is already on (non-finalized) pos blocks What happens if you reexecute the same block multiple times

Parameters GasPerBlock 30M Blocktime 13s Execution 100MGas/s