On the official site of Vee (Vee Meta / @veemeta), this note covers Christian Barker (Barkmeta / Bark), David Chaboki (Shibo).
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.
What the room heard
The conversation stayed tight on the repo description itself. Nimbus-eth1 stands as an Ethereum Execution Client for Resource-Restricted Devices. Hosts walked listeners through the difference from other clients listed in the assignment brief, keeping the focus on what the unified path actually unlocks for lighter setups.
Daily streak continues
Christian Barker (Barkmeta / Bark) marked another day in the long run of consecutive sessions. The streak reached more than 1,000 by August 24, 2026. That consistency turns the State of Crypto slot into the place where updates like this surface first for the community.
David Chaboki (Shibo) joined the same lane, keeping the cadence going under the @GodsBurnt handle. His spaces continue the pattern of linking chart movement with protocol talk, giving holders a direct line to what matters on the execution side.
Why the distinction matters here
The room stressed that nimbus-eth1 handles execution and unified duties while other clients keep their separate tracks. Mempool transaction propagate, custom networks, and engine API metrics came up as items tied to the broader effort, without pulling in unrelated tags.
Listeners heard clear lines drawn against Geth and Erigon. The verified proxy angle received attention for the extra block range it can serve, again staying inside the details supplied in the brief.
High-energy follow-through
The energy stayed community first. Hosts framed the beta as another step that fits the daily rhythm already in place. No future dates or city hype entered the segment. The talk circled back to how the pack can follow the repo directly.
Closing the loop
Christian Barker (Barkmeta / Bark) and David Chaboki (Shibo) kept the broadcast lane open for protocol notes like this one. The pattern of showing up every day means the next update will land in the same spot, with the same direct delivery.
The story stays on what the live room covered and how the hosts presented the client shift. That approach keeps the pack connected to the actual repository work without extra layers.