On January 31st, according to The Block, the developer of the ETH client Geth released version 1.14.13, code-named 'Schwarzschild', which specifically addresses a vulnerability affecting the Geth peer-to-peer (p2p) layer that could lead to denial-of-service attacks on nodes running this version, and potentially affect Layer 2 clients.

Jinse Caijing reported that ETHGlobal member Josh Stark wrote that the recent spending of the ETH Foundation has been a topic of discussion, and here are some thoughts and answers to some big questions. Firstly, we are writing a new report for the Ethereum Foundation, covering 2022 and 2023. We aim to release it before Devcon SEA. Here is a preview of the expenditure information in the upcoming report (specific numbers to be determined). These charts document both internal and external expenses. For example, "L1 R&D" includes funding for external customer teams as well as internal EF researchers. In the past two years, internal spending accounted for about 38% and external spending accounted for about 62%. Internal expenses include EF team, such as: - Geth； - Privacy and Scalability Exploration (PSE); -Solidity; - Cryptography research； -Stable Incentive Team; - Devcon, etc.; All of these teams work openly and share their activity information on their websites, Github, and social channels.

PANews reported on May 25 that according to Unchained, Ethereum liquid staking protocol Lido has significantly improved the long of its execution client. According to a report released by Lido on Wednesday, the usage of Go Ethereum (Geth), the most popular execution client, among validators running by Lido node operators, fell from 67.1% in the previous quarter to 46.6% at the end of the first quarter of 2024. Geth's alternative execution clients, Besu and Nethermind, have both risen since last quarter. More than one-third of validators run by Lido Node operators use Nethermind as an execution client, up from 23.2% in Q4 2023, while Besu's share long rise from 6.9% in the previous quarter to 14.6% in Q1 2024. Lido's use of Geth has been declining every quarter since the third quarter of 2022. At the time, almost all validators run by Lido node operators were using Geth, which posed a risk to the security of Ethereum itself, especially if a vulnerability was found in the super longest client.

Odaily Planet Daily News Lido released the VaNOM (Validator and Node Operator Metrics) report for the first quarter of 2024. The report shows an increase in client diversity, especially at the execution layer; the usage rate of the majority of clients (Geth) has dropped to 46% (96% in 2022 and 67% in the fourth quarter of 2023). The usage rate of public cloud has decreased from 46% to 40%.

Gold Finance reported that Geth developer Péter Szilágyi on the X platform stated that they will soon release a patch for the network vulnerabilities found in previous versions of Geth (v1.13.14 and earlier). Therefore, please make sure you are using the patched version before we provide detailed information on reproducing the attack.

According to a report by Golden Finance, Geth developer Péter Szilágyi claimed on the X platform that in terms of block processing, Geth 1.14.1 seems to be about 5-7% faster than Gethv1.14, while Geth v1.14.2 seems to be 5-7% faster than Geth v1.14.1.

On January 24, the Ethereum client Geth has released v1.13.11 version. This release fixes some bugs and enables Cancun upgrades for Sepolia and Holesky networks, in addition to upgrades to support EIP-4844 transactions in API methods, etc. Sepolia will be upgraded on January 31 and Holesky will be upgraded on February 7.

PANews reported on January 23 that in response to the previous Nethermind execution client problem, Figment, a staking infrastructure service platform, said on its official website that Figment does not run Nethermind as an execution client, but runs Geth as its main execution client. Nethermind's vulnerability has led some to question what would happen if the same problem appeared on most clients like Geth. In this case, any validator connected to Geth may not be able to verify and Ethereum will enter an inactive leak state; these penalties are small but increase over time. If Geth encounters a similar error, Figment is able to switch execution clients within a few hours, and if the losses associated with such events result in negative days of gains, i.e. the penalties imposed are greater than the rewards earned, Figment will pay those losses (Figment will pay up to 6 months of negative days of earnings earnings). It is reported that on January 21, the execution client Nethermind began to encounter some problems in the Block19056922. Nethermind versions 1.23 to 1.25 seem to start rejecting invalid blocks. Between the 257,908 and 257,923 periods inclusive, the participation rate is less than 95%, which is about 2 hours). Previously, yesterday's news, Nethermindv released experimental version v1.26.0-exp.2 to fix the Consensus issue introduced in v1.23.0.

Earlier, a bug in Ethereum's Nethermind client software paralyzed most of the chain's key operators, and Nethermind's developers released patches to fix the problem within hours, Gold Finance reported. But the vulnerability has sparked a discussion of the "client diversity" risk, and some experts believe that most of Ethereum's validators rely on the same software to support their operations, which could be a big risk. Crypto educator Cygaar noted in the X post that "Ethereum's customer diversity is terrible, and a key issue in Geth could cause validators running Geth to burn millions of ETH." DCinvestor, an anonymous Crypto Assets investor, said: "At the moment I can't ignore the risk of a single client staking setup (relying on Geth) and if something goes wrong, I could lose a significant portion of my deposit."

Development company Nethermind has fixed a critical bug in Ethereum's execution client that caused the validator's block processing to fail, Gold Finance reported. According to Daniel Cadela, the company's co-director of technology, the Consensus bug affected software versions from 1.23 to 1.25. All Node Operators need to update to version 1.25.2. The bug was first reported by GitHub user wga22. He stated that there was an error in Nethermind's execution client while validating the transaction. Although the incident affected a small percentage of EthereumNode, it sparked new discussions about the network's reliance on large clients such as Geth.

PANews reported on November 15 that Linea, ConsenSys' Layer2 network, said on the X platform that it is preparing the next major version of Alpha v2, which has lower transaction costs, faster transactions, and 100% EVM coverage, and will also open source the Linea Stack. With Ethereum's Dencon upgrade (EIP-4844), Linea will soon use blobs to store call data on L1 to significantly reduce rollup costs. In addition, the team is working to reduce the cost of fixed transactions by compressing the data sent to L1 and aggregating proofs. Linea's block time is reduced to 4 seconds, which is 3x faster, and there is a mechanism to easily reduce the block time even further in the future. Peak capacity and throughput have also been added to prepare the system for continued network growth. For client diversity, both Besu and geth are supported, and the new Linea sequencer will replace Linea-geth with Linea-Besu.

On November 15, ConsenSys' Layer2 network Linea said that it is preparing the next major version of Alpha v2, the new version has lower transaction costs, faster transactions, and 100% EVM coverage, and will also open source Linea Stack. With Ethereum's Dencon upgrade (EIP-4844), Alpha v2 will soon use blobs to store call data on L1 to significantly reduce rollup costs. In addition, the team is working to reduce the cost of fixed transactions by compressing the data sent to L1 and aggregating proofs. Linea will reduce Linea's block time to 4 seconds, which is 3x faster, and release a mechanism that can easily reduce block time even further in the future. For client diversity, both Besu and geth are already supported, and the new Linea sequencer will replace Linea-geth with Linea-Besu.

On November 9th, Bob Summerwill, executive director of ETCCooperative, tweeted that there was a mistake in the Geth v1.12.15 version, and Spiral was not properly activated on the Mordor testnet.

On November 9th, Bob Summerwill, executive director of ETCCooperative, tweeted that there was a mistake in the Geth v1.12.15 version, and Spiral was not properly activated on the Mordor testnet.

PANews news on October 23, in response to EIP-7542 submitted by Ethereum core developer smartprogrammer.eth to "introduce a new version of the Ethereum peer-to-peer network handshake protocol", Ethereum developer Péter Szilágyi (karalabe.eth) commented: "Obviously, Nethermind and Besu have stopped storing historical data on Ethereum (while Geth still provides services). They want to standardize it so that it doesn't violate the protocol, but becomes a viable way? This is an extremely irresponsible idea, and pruning past data is a very hypocritical marketing ploy to get people to turn to their respective clients. This is absolutely very bad for the network, it violates the protocol, it goes against the entire design of Ethereum. ” In addition, Ethereum developer Matt commented: "This proposal is problematic because it allows for heterogeneous distribution of block data across clients. Rational node operators only maintain a minimum amount of historical data. Therefore, it can be expected that the vast majority of networks will not provide any substantial history. To find a node that does exist, it will take a long time to search the discovery network, and then the node serving most or all of the history will be completely saturated with those looking for it. ”

Péter Szilágyi, Ethereum core developer and Ethereum client Geth developer, said in a post on the X platform that Ethereum clients Nethermind and Besu have stopped storing Ethereum's historical data, and they also want to standardize it so that it does not violate the protocol, but becomes a viable way. And this is a very irresponsible idea. Szilágyi explains that allowing users not to store historical chains is a very hypocritical marketing trick: - The user switches to some other client because it is smaller; - They can still access old data because Geth provides the service; - Users (and Geth developers) don't know anything about it. If balance is considered, they "could" work together on EIP-4444, "first" to help archive historical blocks, "and then "all clients can delete it immediately, but they feel that this won't have any impact on market share, so leave the thorny issue to Geth and keep YOLO (live in the moment) until then. Szilágyi said: "Sometimes I really want to quit Ethereum and try to sit on the sidelines. When core developers are competing for interests, why bother to improve Ethereum? I am deeply disappointed in all involved. ”

PANews reported on October 5 that Immutable released the mainnet launch roadmap. In November, there are plans to rebuild the Immutable zkEVM testnet and upgrade its first EVM client from Polygon Edge to Geth, ensuring that Immutable zKEVM is as close to Ethereum as possible while being fully compatible with the entire Ethereum tool ecosystem. The zkEVM mainnet will be launched from December to January next year, and developers will be invited to join in groups before being opened to the public. In 2024 Immutable will offer a dedicated application chain with the same technology stack and functionality as Immutable zkEVM, but with a unique level of customization. Finally, zk-prover will be introduced and provide a trustless cross-chain bridge between Ethereum and Immutable zkEVM.

According to news on October 5, Immutable released a mainnet launch roadmap, in which it plans to rebuild the Immutable zkEVM test network in November and upgrade its first EVM client from Polygon Edge to Geth to ensure that Immutable zKEVM is as close to Ethereum as possible. Fully compatible with the entire Ethereum tool ecosystem; the zkEVM mainnet will be launched from December to January next year, and developers will be invited to join in groups before being opened to the public; In 2024, Immutable will provide a dedicated application chain with the same technology stack and functionality as Immutable zkEVM is the same, but with a unique level of customization; finally zk-prover will be introduced and provide a trustless Ethereum and Immutable zkEVM cross-chain bridge.

Odaily Planet Daily News EthStorage teamed up with Hyper Oracle and Delphinus Lab to release the zkGo compiler. According to reports, zkGo is based on the latest Go 1.21.0 and is the first to compile regular Go code into ZK protocol-compatible Wasm code. The generated Wasm code execution can already be zero-knowledge proof and on-chain verified by Delphinus Lab’s zkWasm tool. As an important application of zkGo, zkGo has successfully compiled Optimism's Fraud Proof's L2 Geth (also known as op-program-client) to generate Wasm code compatible with the ZK protocol. The current Wasm code has passed the zkWWasm dry run and will help implement ZK Fraud Proof technology in the future.

PANews reported on September 19 that the research company Rated posted on the The percentage of blocks is double the average over the past 30 days. This impact can be traced back to the Geth version, which introduced block production issues that were exacerbated by the way Prysm handles block production logic (prioritizing local blocks over boosted blocks). Given that GETH and Prysm are the most popular EL and CL clients respectively, the combined impact is a 2 sigma decrease in network-wide effectiveness. However, in the approximately 3 years that the Beacon Chain has been running, the 2 sigma drop in effectiveness has not really had an impact on the overall good functioning of Ethereum. In addition, Ethereum community developer terence.eth said on the The chain is still running smoothly. While Geth's bug interfered with block production, Prysm prioritizes security, it checks local blocks first and if that fails, it stops block production even if a builder block is specified. We're lucky : 1. Prysm is not a super dominant client. 2. Not all upgraded to Geth v1.13.0 at the same time. 3. The Geth team responded and fixed quickly." According to yesterday’s news, the Ethereum client Geth released a hotfix version v1.13.1 to fix issues such as invalid block generation.

PANews reported on September 18 that the Ethereum Go language client Go Ethereum released the Ethereum client Geth v1.13.1. This is a hotfix version of v1.13.0, which fixes issues such as engine API fork detection that results in invalid block generation and database corruption caused by abnormal restart of snapshot synchronization in the path scheme. According to previous news, the Ethereum client Prysm posted on Twitter that a bug was found in Geth that interferes with Prysm's block production, and reminded users not to update Geth to version V1.13.0 for the time being.

Golden Finance reported that the Ethereum Go language client Go Ethereum released the Ethereum client GethV1.13.1. Geth v1.13.1 is a patch version of v1.13.0. The new version fixes the following issues: Fix active fork detection on the engine API, causing signers to create invalid blocks (#28135). Path fixes database corruption caused by strangely restarting snapshot sync (#28124, #28126). Fix geth db inspect command to run against old hash scheme databases (#28108). Fix valid Gas price calculation regression on RPC API (#28130). In addition to fixes, v1.13.1 also introduces support for configuring Geth via environment variables.

Odaily Planet Daily reported that the Ethereum client Prysm issued a reminder on the X platform: Do not update Geth to version V1.13.0 for the time being, because a bug was found in Geth that interferes with Prysm's block production. Note: Although most clients do not need to use mev-boost for local block generation, Prysm always verifies against local blocks; Prysm will release more updates later. According to previous news on September 12, the Ethereum Go language client Go Ethereum released the Ethereum client GethV1.13. This version provides a new database model for storing Ethereum state, which is faster than the previous solution and Appropriate pruning is also performed.