# Withdrawal Client Milestone Tracker 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 |M0|M1|M2|M3|M4|M5|Docs| |--|--|--|--|--|--|--| [Geth][Geth-Link] ||||||| [Nethermind][Neth-Link] ||||||| [Besu][Besu-Link] ||||||| [Erigon][Erigon-Link] ||||||| [EthereumJS][EJS-Link] ||||||| |||||||| [Prysm][Prysm-Link]||||||| [Lighthouse][LH-Link]||||||| [Teku][Teku-Link]||||||| [Nimbus][Nimbus-Link]||||||| [Lodestar][Lodestar-Link]||||||| [Geth-Link]: https://github.com/ethereum/go-ethereum/pull/25838 [Neth-Link]: https://github.com/NethermindEth/nethermind/pull/4731 [Besu-Link]: https://github.com/hyperledger/besu/pull/4552 [EJS-Link]: https://github.com/ethereumjs/ethereumjs-monorepo/pull/2353 [Prysm-Link]: https://github.com/prysmaticlabs/prysm/issues/11077 [LH-Link]: https://github.com/sigp/lighthouse/tree/eip4844 [Lodestar-Link]: https://github.com/ChainSafe/lodestar/pull/4679 [Teku-Link]: https://github.com/ConsenSys/teku/issues/5680 [Nimbus-Link]: https://github.com/status-im/nimbus-eth2/pull/4089 ## Milestones - M0: *Implementation started* - Signify that implementation has started by creating a tracking issue and linking in the above table - Docs: *Core Documentation* - EL/CL: detailed documentation on how to run your client with withdrawals enabled - Link under “Docs” in milestone table - M1: *Spec Implemented* - EL/CL passes test vectors - M2: *1-to-1 Interop* - Perform the following with at least two separate teams: - run 1:1 devnet without transition (Capella == 0) - Record teams interop’d with alongside ✅ in milestone table – e.g. “✅ lodestar, teku” - M3: *Join the devnet* - Join the devnet - Instructions and parameters for the devnet will be released in due time - Create a README for the public to join the devnet with your client - Test the withdrawal functionality on the devnet - M4: *Stretch goal tbd* - M5: *Stretch goal tbd*
Last changed by  
 
Marius van der Wijden
148

Read more

Untitled

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

3/20/2023
Untitled

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

3/13/2023
Bad block hashes

Number Reason Accepted Rejected Not seen 1 Basefee Besu, Geth

1/24/2023
Static test case for withdrawals on EL

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,

11/8/2022
Read more from Marius van der Wijden
Published on HackMD