The Erigon development team has released v3.4.4 of its Ethereum execution client, a bugfix update aimed at improving node stability and specification compliance. The release, named “Splashing Saga,” is recommended for users running Erigon nodes on Ethereum mainnet.
The update focuses on client reliability rather than a broader Ethereum protocol change. It does not introduce a network-wide upgrade, but it addresses issues that matter for node operators maintaining synchronization during normal mainnet activity.
Release Fixes Gas Mismatch After Reorgs
The primary fix targets a gas used mismatch that could occur after a chain reorganization. Reorgs happen when a node must switch from one competing chain branch to another, requiring the client to recalculate state and block-related data correctly.
Erigon mitigated the issue by pruning the in-RAM overlay. That technical adjustment helps ensure the client calculates gas consumption properly when handling a reorg.
The fix is operationally important because gas accounting must remain consistent during volatile network conditions. Even isolated mismatches can create synchronization problems for node operators if left unresolved.
The available documentation does not indicate a widespread Ethereum mainnet disruption before the release. Still, the Erigon team’s recommendation signals that operators should treat the update as part of routine client maintenance.
Caplin API Update Aligns With Ethereum Specs
Erigon v3.4.4 also updates the Caplin Beacon API. The release changes uint64 and Gwei field serialization so those values are returned as JSON strings.
That change is not a user-facing feature, but a specification compliance adjustment. For infrastructure providers, APIs that follow expected Ethereum formats reduce integration friction across monitoring tools, staking systems and backend services.
The release also underscores the importance of execution-client diversity in Ethereum’s infrastructure stack. Ethereum relies on multiple clients, including Geth, Nethermind, Besu and Erigon, to reduce dependence on a single implementation.
In this case, however, the update is specific to Erigon’s internal reliability and API behavior. It does not require coordinated action from all Ethereum clients or from regular ETH holders.
Node operators can access the update through Erigon’s official repository. No major changes to hardware requirements or resource consumption were noted alongside these bugfixes, making v3.4.4 a targeted maintenance release for mainnet stability.
