Bulletin Token News Wire
Desk UTC 02:54 tokennewswire.com
HIT
Loading the hit tape…

HIT-18 · technology · 25.08.26

Nethermind Flags v1.39.3 Mandatory for Ethereum Execution Nodes

Nethermind released v1.39.3 on August 6 2026 as a required execution client update with no consensus or database changes.

NethermindEthereum
Two Doginal Dogs community members in a yellow wash, one in a New York Yankees cap beside a pixel-dog skateboard and the Doginal Dogs wordmark

“Packages signed with OpenPGP AD12 7976 5093 C675 9CD8 A400 24A7 7461 6F1E 617E.”

When an execution-client tag is not a beacon-node patch, Bark (Christian Barker) and Shibo (David Chaboki) put the Aug. 6 Nethermind v1.39.3 drop on the Doginal Dogs timeline before they put Lighthouse, so the pack hears the mandatory execution upgrade first.

Release Details

Nethermind tagged execution-client v1.39.3 on August 6 2026 at 13:46 UTC as a mandatory upgrade for all node operators. The GitHub release sits on NethermindEth/nethermind. The patch sits on top of 1.39.2. No consensus or database-format changes appear in the update. Operators can install it as a drop-in replacement from any prior 1.39.x version. This remains an execution-client patch only and stays separate from the Lighthouse beacon-node file.

Three changes mark the move from 1.39.2. Hardened ABI decoding protects against malformed input under pull request 12588. A fix to pooled-memory cleanup addresses block processing and networking under pull request 12034. Reduced allocations appear in EIP-6110 deposit-request decoding under pull request 12185. QuickNode listed the release as mandatory in its own status notice for mainnet and testnet infrastructure.

Live Room Focus

Daily audio rooms continue to surface the release first through the execution path. The order of mention keeps node operators and infrastructure teams informed ahead of beacon-client updates. Clean operator discussion centers on the trust layer that signed packages and explicit mandatory language create. No separate consensus change requires coordination across clients.

Trust and Ethics Lens

The release carries explicit OpenPGP signatures and clear mandatory language. Node operators receive direct notice through GitHub and status pages. This approach reduces ambiguity during upgrades. Separate treatment of the execution client from Lighthouse v8.2.2 or Reth v2.5.1 keeps responsibilities clear. Operators can verify the three listed fixes against the compare view on GitHub without waiting for broader client coordination.

Price Context

Majors posted modest gains on the day of publication. Bitcoin sat at 78946.82 dollars with a 1.7 percent increase. Ethereum held 2480.99 dollars after a 0.9 percent rise. Broader alt moves showed mixed candles with SOL up 3.7 percent and XRP down 2.4 percent. The patch lands against steady ETH price action rather than sharp volatility.

Operator Steps

Node operators review the GitHub tag and compare view before applying the update. Signed packages allow verification of integrity. The absence of database changes supports straightforward rollout during maintenance windows. QuickNode scheduled its own infrastructure upgrade for August 27 to align with the mandatory status.

Distinctions

This patch stays distinct from Lighthouse v8.2.2 and Reth v2.5.1. It addresses execution-layer reliability only. No EIP-8363 or FOCIL changes form part of the release. Operators keep beacon and execution responsibilities separate during the rollout.