Nethermind 2.0.0-rc2 Enables Flat DB by Default

Published: 2026-09-14 16:24:08 |

Nethermind has released 2.0.0-rc2, a second release candidate for its Ethereum execution client. The update makes Flat DB the default state backend for new or resyncing nodes, while existing Patricia and Flat databases remain unchanged. No database-format change or resync is required for users already running 2.0.0-rc. The release adds explicit history-retention modes: None, Rolling and SinceBlock. Operators using a window size or since-block setting must now configure the corresponding retention mode, or the node will fail to start. Flat archive nodes can also serve historical eth_getProof requests when archive coverage is available, although the feature is disabled by default. Snap serving is enabled by default for fresh nodes using Flat DB, potentially increasing outbound bandwidth. Operators can disable it with Sync.SnapServingEnabled=false. The release also fixes snap-sync stalls, malformed-header handling, graceful shutdown crashes, snapshot pruning, streamed traces and several JSON-RPC errors, including incorrect eth_maxPriorityFeePerGas responses. For traders, Nethermind 2.0.0-rc2 improves Ethereum node reliability and data-access capabilities. It is primarily an infrastructure upgrade rather than a direct market catalyst. Operators upgrading from version 1.39.x must first complete the 2.0.0-rc migration checklist.

Neutral

The expected market impact is neutral. Nethermind 2.0.0-rc2 is a client-software release, not a protocol upgrade that changes Ethereum issuance, transaction costs or token economics. Its fixes could reduce operational risk for validators, RPC providers and infrastructure operators, particularly by improving snap sync, shutdown safety, historical proofs and JSON-RPC correctness. That may support Ethereum network reliability over the long term. In the short term, however, client releases rarely create sustained ETH price momentum unless they address a major outage, consensus issue or security vulnerability. The upgrade also introduces configuration requirements and higher potential bandwidth usage through default snap serving, creating some implementation risk for node operators. Traders may monitor adoption, upgrade-related incidents and client-diversity data, but the release alone is unlikely to materially change spot demand, derivatives positioning or market volatility. The most likely outcome is limited price reaction, with a mildly positive infrastructure effect over the longer term.