--- tags: newineth2 description: The latest update on Ethereum 2.0 development image: https://benjaminion.xyz/f/favicon-96x96.png --- <style> a {text-decoration: underline;} a {color: #0000ee;} a:visited {color: #551a8b;} .ui-infobar {visibility: hidden; padding-top: 0;} .community-button {visibility: hidden;} .markdown-body {padding-top: 0;} </style> # What's New in Eth2 - 11&nbsp;February&nbsp;2022 ![My avatar](https://benjaminion.xyz/f/ms-icon-144x144.png =32x32) Ben Edgington (Eth2 at [ConsenSys](https://consensys.net/) — all views expressed are my own) Edition 87 at [eth2.news](https://eth2.news/) ## Top picks No question - last week SuperPhiz and I recorded ourselves doing a [walk through](https://www.youtube.com/watch?v=Bd3b7PeKEB4) of the last edition of WNIE2. It was great fun just chewing it over together, and hopefully it added a bit of colour and depth. This was Phiz's suggestion; I wish I'd thought of it long ago. Anyway, maybe we'll do it again :slightly_smiling_face: ## The Beacon Chain Nothing to see here :eyes: ### Client diversity The client diversity story continues. SuperPhiz put out [a call](https://www.reddit.com/r/ethstaker/comments/sj7gnh/developing_a_data_driven_approach_to_the_client/) for "critical analyses and data-driven expectations" for how client diversity affects the beacon chain, along with grants and POAPs to encourage submissions. And the first submission [is in](https://twitter.com/superphiz/status/1491540214095003648) - jmcook synthesised a ton of material into [Client diversity on Ethereum’s consensus layer](https://mirror.xyz/jmcook.eth/S7ONEka_0RgtKTZ3-dakPmAHQNPvuj15nh0YGKPFriA). Read it and note it. And, if applicable, send it on over to your staking provider. ## The Merge The [Merge readiness checklist](https://github.com/ethereum/pm/blob/master/Merge/mainnet-readiness.md) is always worth a look. More and more check marks in more and more boxes. I've worked on this thing for so long that it's easy to feel a bit jaded. But looking through this earlier today I had a genuine butterflies-in-my-stomach moment. _<insert "it's happening" GIF here>_ It's all simultaneously slightly terrifying and incredibly exciting. ### Kintsugi Testnet Four hundred thousand slots in, and the Kintsugi Merge testnet continues to run very nicely. There was some trouble on Kintsugi a while back that we [wrote about](https://hackmd.io/@benjaminion/wnie2_220114#Kintsugi-Testnet) at the time. A proper [incident report](https://notes.ethereum.org/@ExXcnR0-SJGthjz1dwkA1A/BkkdHWXTY) was published last week. Don't miss the [important takeaway](https://notes.ethereum.org/@ExXcnR0-SJGthjz1dwkA1A/BkkdHWXTY#Important-takeaways-for-validators-infrastructure-providers-and-tooling-developers) for validators, infrastructure providers and tooling developers. In summary, don't spec your hardware based only on the happy flow; be prepared for increased resource usage in times of non-finality. It's definitely not too late to join Kintsugi, or to deploy and test your application on it. The summary information page remains [here](https://kintsugi.themerge.dev/). EthStaker made [a video](https://www.youtube.com/watch?v=fCyiXQsQqyA) on how to join Kintsugi with a Teku/Besu combo, based on Luis Naranjo's [guide](https://luisnaranjo733.hashnode.dev/want-to-help-test-the-merge-run-a-node-on-kintsugi) . We made [a video](https://www.youtube.com/watch?v=YiXBowFPc5M) on how to join Kintsugi with a Teku/Besu combo from our webinar this week, "On the Verge of the Merge" (with Q&A at the end). We used the excellent [eth-docker repo](https://github.com/eth-educators/eth-docker/blob/merge/KINTSUGI.md) for a quick start. Or you could break out your Raspberry Pi and try out the full current range of client combinations with Ethereum on ARM's incredible [PnP Image](https://twitter.com/EthereumOnARM/status/1490624310792400897). ### Kiln Testnet Kiln is the successor to Kintsugi. Kiln is both a spec version and a set of devnets and testnets we plan to run. [Kiln spec v1](https://hackmd.io/@n0ble/kiln-spec) is out, and we'll be starting up a first Kiln devnet ([merge-devnet-4](https://notes.ethereum.org/D5xK4XrmTb6MKGudf_hcrg)) to this spec shortly. There will be a Kiln v2 spec imminently that adds two things: [authentication](https://github.com/ethereum/execution-apis/pull/167) for the EngineAPI between the consensus and execution sides, and a (temporary) [heartbeat](https://github.com/ethereum/execution-apis/pull/172) method so that users can be alerted if their execution or consensus client is misconfigured relative to the other. In a few weeks we will open up the Kiln testnet to all, and all being well, it will be the last bespoke testnet we'll do before we start forking the existing Eth1 testnets such as Rinkeby. Keep your eyes on the [Kiln progress tracker](https://notes.ethereum.org/@timbeiko/kiln-milestones) to see how far along things are. ## Beyond The Merge On the consensus devs call this week we took a brief look beyond the Merge. The Eth1/execution side is planning an upgrade (currently called Shanghai) for later in the year, and much of the last Eth1 [ACD call](https://www.youtube.com/watch?v=_kt-r4J8PJc) was spent discussing what will go in there. We will very likely do an upgrade on the consensus side at the same time, if only to enable withdrawals which go hand-in-hand with a new Eth1 EIP from Alex Stokes, [Beacon state root in EVM](https://github.com/ethereum/EIPs/pull/4788). In addition to withdrawals we are also looking at throwing in Jacek's [historical batches](https://github.com/ethereum/consensus-specs/pull/2649) clean up, and doing some work to support Vitalik's [blob transactions](https://notes.ethereum.org/@vbuterin/blob_transactions) enhancement. On the topic of withdrawals, there is an [EIP proposal](https://github.com/ethereum/EIPs/pull/4736) with [discussion](https://ethereum-magicians.org/t/consensus-layer-withdrawal-protection/8161) on the Ethereum Magicians' forum that seeks to help anyone who might have had their withdrawal keys compromised. ## Staking Ahead of the Merge, all stakers are being strongly urged to run their own execution clients (Eth1 clients) if they are not already doing so (guilty!). It makes sense to test things out with plenty of time to spare; Eth1 clients are their own special kind of beast. The same client-diversity considerations apply to execution clients as to consensus clients. Bottom line, run something other than Geth. Anyway, that's all by way of introduction to Ladislaus's [article on running execution and consensus clients](https://mirror.xyz/ladislaus.eth/O5bW3rDnKITHlCXE9K_0IwiEwDrc6qw-y3MpX0EUcew) with Ubuntu and Docker, focusing on a Besu and Lighthouse combination. Here's the [latest report](https://twitter.com/EthereumPools/status/1490968631744024580) from the excellent [Ethereum Pools](https://twitter.com/EthereumPools) account on Twitter: "No single #eth2 staking pool will be offline without us noticing". And while we're on staking pools, take a look at [Rated](https://mirror.xyz/ratedw3b.eth/eDj9Fr0LgNWFL71DtyGfXp_ocVVYrCjJlQAGiLHCFWU)[^fn-2] developed by Elias Simos and Aris Koliopoulos. Rated is "an experiment in coordination" around providing transparency on the beacon chain. There is a [front-end](https://www.rated.network/) that groups validators by deposit address and collectively reports their performance, and [documentation](https://rated.gitbook.io/rated-network-v0/getting-started/welcome) with some good info[^fn-1]. This looks very interesting and promising. I firmly believe that only good things can come out of having better, more transparent data available to the community. [^fn-2]: The link was correct worked an hour ago and has now stopped working. Hopefully just a temporary issue with Mirror and it will reappear again by the time you see this. Meanwhile [this thread](https://twitter.com/ratedw3b/status/1492156429448331265) is a good backup. [^fn-1]: Hate to be boring, but [this](https://upgrading-ethereum.info/altair/part2/incentives) could be usefully added to the resources page. ## The Great Explainers SuperPhiz [explores](https://www.reddit.com/r/ethstaker/comments/snrsax/how_dvt_solutions_like_blox_ssv_and_obol_relate/) how distributed validator technology (DVT fka SSV) relates to staking solutions like Rocket Pool and Lido. [The Book](https://upgrading-ethereum.info/altair/) progresses slowly but surely, the latest addition being [Simple Serialize](https://upgrading-ethereum.info/altair/part2/building_blocks/ssz). Magical Merkleization coming at you next. Many thanks to [AtHeartEngineer](https://twitter.com/AtHeartEngineer/status/1491164228270829569) for helping improve readability on mobile! ## Research I noted the [Balancing Attack: LMD Edition](https://ethresear.ch/t/balancing-attack-lmd-edition/11853?u=benjaminion) research post last time, but had not had time to look into it then. Here are some observations: - It is a theoretical way to split the beacon chain and delay finalisation. But it does rely on the attacker having a very high degree of power over the network. (Not inconceivable, but also not very likely.) - All the attacking validators will end up slashed, so it would be very expensive to pull off. - There is a very simple defence that we should probably have put in place previously: if the fork choice sees a validator equivocating then remove all of its votes. - The point is that the LMD fork choice doesn't take account of validator slashings while the chain is not finalising. It bases its decisions on the state at the last justified checkpoint. Discarding equivocations is a workaround for not taking slashings into account. - It is unfortunate that these kinds of issues keep showing up with fork choice. - I am super glad to have researchers like these (Joachim Neu, Ertem Nusret Tas, David Tse) continuing to closely scrutinise the beacon chain and openly share their findings. ## Regular Calls ### Implementers Call #81 took place on the 10th of February. * [Agenda](https://github.com/ethereum/pm/issues/475) * [Video](https://youtu.be/DtwTZWZrZMY?t=54) * My [quick notes](https://hackmd.io/@benjaminion/S1YGF9Gk9). Mostly planning and updates for the Kiln testnets. We also took a brief look [beyond the Merge](#Beyond-The-Merge). All done in a nice tight 35 minutes. ### Merge Community Call [Merge Community Call #3](https://github.com/ethereum/pm/issues/465) took place today. Here's [the video](https://www.youtube.com/watch?v=65Pt6oS3kDM). It was mostly Q&A led, so the info wasn't presented in a very ordered way, and lots of the action was happening in the chat, which is missing from the video. Nevertheless, there was lots of good advice and important info dropped. Worth checking in to test your understanding of how the Merge will affect you as a user or developer on Ethereum (tl;dw: very little indeed). ## Upcoming events - Monday 14th February, 1430 UTC: Danksharding educational workshop. Details TBA, but it will be recorded and live streamed (presumably via the Ethereum Foundation [YouTube channel](https://www.youtube.com/c/EthereumFoundation)). Homework: - [Original Danksharding proposal](https://notes.ethereum.org/@dankrad/new_sharding) - [Explainer](https://polynya.medium.com/danksharding-36dc0c8067fe) from Polynya - 11-20 February, [EthDenver](https://www.ethdenver.com/). The [schedule](https://www.ethdenver.com/schedule) is enormous. I did a very quick scan through, and tbh, I didn't see a lot in there that interests me as a protocol engineer. A few I would make the effort to see were I there (sorry if I missed your thing): - Colfax on [The UX of staking](https://ethdenver.sched.com/event/xTgQ/the-ux-of-staking-on-ethereum-and-why-it-is-critical-to-decentralization) - Aditya on [Distributed Validator Technology](https://ethdenver.sched.com/event/xTj8/distributed-validator-technology) - Carl on [Distributed Validators](https://ethdenver.sched.com/event/xTVa/distributed-validators-improving-staking-no-matter-your-eth-balance) - Danny on [Ethereum Proof-of-Stake and Our Solar Punk Future](https://ethdenver.sched.com/event/xTSv/ethereum-proof-of-stake-and-our-solar-punk-future) - 18-25 April, [DevConnect Amsterdam](https://devconnect.org/). Plenty [going on](https://devconnect.org/schedule). See you there :wink: ## In other news - Danny's [Finalized no. 33](https://blog.ethereum.org/2022/01/31/finalized-no-33/) update: Kiln latest, and client diversity metrics. - EthStaker received a grant from the Ethereum Foundation to [run two validators](https://twitter.com/superphiz/status/1491583471839494153) :tada: - Stereum's first newsletter, [Under the Surface #001](https://stereum.net/under-the-surface-1/): "Update & Upkeep Challenge, our iOS app release and that we’re going to the Devconnect. ## And finally... I got [busted](https://twitter.com/ajsutton/status/1491694664923037700). My rank hypocrisy is exposed. Please don't cancel me 😭 * * * [![[Twitter]](https://benjaminion.xyz/newineth2/img/twitter.svg =40x40)](https://twitter.com/benjaminion_xyz) Follow me on [Twitter](https://twitter.com/benjaminion_xyz) to hear when the next edition is out 🙌. [![[RSS]](https://benjaminion.xyz/newineth2/img/rss.svg =32x32)](https://benjaminion.xyz/newineth2/rss_feed.xml) We also have an [RSS feed](https://benjaminion.xyz/newineth2/rss_feed.xml). [Advertising](https://hackmd.io/@benjaminion/eth2_news/https%3A%2F%2Fhackmd.io%2F%40benjaminion%2Fadvertising) on this newsletter. [Give Feedback](https://docs.google.com/forms/d/e/1FAIpQLSfkESc4CmNfRGHHjWfNeF3ceLwrXDvynetda4sKfJFJ71Oabw/viewform).