go-ethereum

This is a quick release that postpones the Amsterdam fork on the Hoodi testnet, previously scheduled for Oct 26, 2026, 17:42:48 UTC. Hoodi node operators running v1.17.9 must upgrade before then. A new date will be set in a…

This release enables the Amsterdam fork 🦩 on the Hoodi testnet at block timestamp 1793036568 (Mon, 26 Oct 2026 17:42:48 UTC).

This is a security-focused release, fixing several DoS risk issues ❤️‍🩹 . Note most of the the fixes related to bugs which only become possible after the activation of the Amsterdam fork. There are also some general…

This is a quick release, cut mainly because publishing v1.17.6 to the Ubuntu PPA failed. It also carries a few fixes merged since then. Both v1.17.6 and v1.17.7 are ready for the Amsterdam fork on Sepolia (Oct 6, 2026), so…

This is a maintenance release with a number of performance improvements to block processing and initial sync, and is recommended for all users.

This is a maintenance release with accumulated bug fixes and improvements, and is recommended for all users. It continues the implementation work for the upcoming Amsterdam hardfork.

This is a maintenance release with accumulated bug fixes and improvements, and is recommended for all users. It also continues the implementation work for the upcoming Amsterdam hardfork.

This is a maintenance release with continued progress on the Amsterdam fork implementation. It also introduces ETH/70, which is now live on the network.

This is a maintenance release with several important bug fixes. Notably, a critical issue in debug_executionWitness could previously corrupt node data, users relying on this RPC endpoint are strongly advised to upgrade.

This is a bug fix release and is recommended for all users. It resolves a regression in snap sync, as well as several security issues.

This is a feature release, with all accumulated development from the last 3 months. See below for the highlights.

This is a security hot-fix release. Specifically, this release fixes CVE-2026-26314, CVE-2026-26315.

在区块链的狂野西部，开发者们常面临一个终极选择题：性能还是安全？效率还是兼容性？ 当多数以太坊客户端在复杂生态中挣扎时，go-ethereum（Geth）用行动证明——鱼与熊掌可以兼得。它是全球超过75%以太坊节点的选择，却因高度优化引发争议：有人质疑其“过度追求性能牺牲了去中心化”，但事实恰恰相反。Geth通过独特的轻节点模式和快速同步技术，让个人用户也能在笔记本电脑上运行全节点，直接击碎了“只有矿池才能玩转以太坊”的傲慢偏见…

在区块链的浩瀚星空中，go-ethereum犹如一颗璀璨的明星，吸引着无数开发者的目光。然而，使用它的理由并不仅仅是因为它的知名度。想象一下，你正在构建一个去中心化的应用程序，面对着性能、可扩展性和安全性等诸多挑战。go-ethereum不仅提供了强大的工具和库，还能让你在这个竞争激烈的领域中脱颖而出。选择go-ethereum，就是选择了一条通往未来的道路，尽管这条路上充满了未知的挑战，但它也蕴藏着无限的可能性。

在这个数字化飞速发展的时代，区块链技术如同一场革命，改变着我们对信任和交易的理解。然而，面对众多的区块链平台，开发者们常常陷入选择的困境。go-ethereum（Geth）作为以太坊的官方实现，凭借其强大的功能和灵活性，成为了开发者的首选。它不仅支持智能合约的创建和执行，还提供了丰富的工具和库，帮助开发者轻松构建去中心化应用（DApps）。然而，使用go-ethereum并非没有挑战，如何在复杂的技术环境中找到最优解，成为了每个开发者必须面对的矛盾。

在区块链开发的世界里，选择节点客户端就像在战场上挑选武器——选错了，可能连对手的衣角都摸不到。