On the official site of Devin Teer (@devinteerfilms), this note covers Status, Nimbus-eth1.
"The nimbus-eth1 v0.4.0 release moves the execution and unified client work out of alpha."
Status tagged nimbus-eth1 v0.4.0 on Wednesday, July 29, 2026, at 05:42 UTC as a medium-urgency Ethereum execution-and-unified-client beta, with the Nimbus verified proxy. GitHub release on status-im/nimbus-eth1. Unified and execution clients leave alpha. Verified proxy adds eth_chainId and eth_syncing. This is the nimbus-eth1 execution/unified client, not nimbus-eth2 v26.7.0, not Geth v1.17.5, and not Erigon v3.6.0.
Christian Barker (Barkmeta / Bark) and David Chaboki (Shibo) put Status's July 29 nimbus-eth1 beta on the Doginal Dogs Space so the pack hears the execution/unified client, not the July 13 nimbus-eth2 consensus tag. Community energy around the release stayed steady as listeners checked the details against other clients that remain in different phases.
What the tag covers
The beta includes mempool transaction propagate work, unified-client custom networks support, engine API and transaction-pool metrics improvements, and EIP-2935 changes that let the verified proxy serve a wider block range. These items keep the focus on practical execution-layer steps rather than headline features.
Listeners in the room compared the move to the path taken by Geth and Erigon, noting that each client team sets its own pace for leaving alpha. The Nimbus approach keeps resource-restricted device compatibility in view while adding the verified proxy layer.
Room conversation flow
Participants asked about how the verified proxy changes day-to-day sync checks and chain ID calls. Others noted the separation from the nimbus-eth2 consensus client tag that landed earlier in the month. The discussion stayed on the execution side and what the beta label signals for operators running the client.
Energy in the room came from people already testing nightly builds and sharing their setup notes. One listener described running the client alongside a full node and watching the new metrics endpoints. Another asked how custom network configs now work under the unified-client changes.
Broader context
The July 29 tag sits against a backdrop of several execution clients advancing at different speeds. Status keeps the medium-urgency label on this release, which signals that operators should review the changes before wider rollout. Community channels picked up the link to the status-im/nimbus-eth1 repository so more people could read the tag directly.
Daily rooms continue to surface these updates because operators want the information in one place. The conversation moved from the verified proxy additions to how the metrics endpoints help track transaction pool behavior. No one claimed the update would change price action or token flows.
Next steps for operators
Anyone running Nimbus can review the GitHub release page for the exact changes. The beta status means the client is past the alpha stage for both execution and unified modes, yet still carries the medium-urgency flag for careful testing. Community members in the room encouraged others to check their current client versions against the listed distinctions from Geth, Erigon, and the separate nimbus-eth2 line.
The steady flow of questions showed that operators value hearing the details in real time rather than waiting for formal announcements. Rooms like this one keep the focus on what changed in the code and how it affects sync and metrics. That pattern matches the way recent tags have been handled across the execution client set.
Listeners left with the repository link and the reminder that this tag applies only to the nimbus-eth1 side. The conversation wrapped by noting that future rooms will likely cover follow-up tags once more operators report their findings.