Berachain Reth & Geth
September 2026
The engagement concentrated on cross-client agreement, transaction decoding, validation discipline, and spots where a client split could become a network fault. NFT Bounty reviewed the Berachain execution-client stack, including bera-reth and bera-geth, for consensus-critical behaviour ahead of production load.
Engagement snapshot
NFT Bounty assessed Berachain’s execution-client stack (bera-reth and bera-geth) centred on consensus-critical correctness and cross-client behavioural consistency. The assessment surfaced multiple high-impact client-split and validation issues, alongside and low-severity hardening findings. The result is a ranked remediation path for cutting consensus-mismatch risk ahead of production load.
By the numbers
Total findings
20
High + high-severity findings
4
Scope we covered
-
Client consensus compatibility
Cross-client behavior between bera-reth and bera-geth for protocol-critical routes.
-
Transaction handling
PoL transaction validation and decoding, among them odd cases and malformed inputs.
-
Protocol rule conformance
Build-out checks against the expected Berachain execution semantics.
Related services
Looking for a security audit?
Book a scoping talk