Over the past few months, the @Nethermind Client team has been focusing on almost everything BUT performance - authoring, supporting and reviewing EIPs for Glamsterdam, championing Hegota headliner - Frame Transactions, researching state bloat, and much more. That's not changing - we are still being heavily involved in Ethereum roadmap. But AI has unlocked a whole new level of productivity for us, and we're now pushing hard on several fronts: 1. zk guest program - coming soon to @eth_proofs. Very promising, very performant. 2. RPC refresh - Geth compatibility, major performance improvements, and more. Few projects already got a feeling of what we are shipping - and it is looking very good. 3. Client hardening with AI - Node MCP for users and our custom CoreMCP for developers, helping us ship faster and build a much more stable client. 4. Innovative node optimizations and advanced plugins - unlocking capabilities that could be extremely useful for many projects across the ecosystem, including support for new chains. And that's just the beginning. As a "side effect," we've also significantly improved the node's performance at the tip of the chain - before even getting into the Glamsterdam hard fork, which should unlock a whole new level of throughput. Nethermind is the fastest #Ethereum# execution client, and the only one pushing beyond 1.5 GGas/s in p50 block throughput at the tip of the chain. With the next fork, we expect that ceiling to go even higher - based on Sepolia data, potentially around 3x higher. And we're definitely not done. We want to change the rules of the game. The AI-powered tools we've built in-house are giving us enormous leverage, and we're confident this advantage will only grow over time. Performance is good. 🚀

Already 55% of @Nethermind nodes on #Ethereum# mainnet migrated to v2 version! 11% of nodes are on new FlatDb design and number keeps growing! Consider migration - FlatDb gives a lot of great improvements. ⚠️HalfPath will be deprecated once adoption of Flat will be big enough.

These are BENCHMARKS - which means we are not testing something random. Worst cases for each compute scenario - so pushing clients limits. Average block post-Glamsterdam with the 200MGas will be likely still processed in ~20ms = 10 GGas/s. A lot of room left for next bumps.

The work behind @Nethermind Client is kind of wild. 1.39.3 HalfPath→master FlatDB eth_call performance: • suite 1: 155.0 → 34.4 ms — 4.50× • suite 2: 69.4 → 16.1 ms — 4.31× • suite 3: 648.5 → 192.0 ms — 3.38× Part of that lands in 2.0.0, rest will be shipped in 2.1.0.