Skip to content

fix: bump go-eth2-client to v0.1.8 for heze state decoding - #198

Merged
barnabasbusa merged 2 commits into
mainfrom
bbusa/bump-go-eth2-client-heze
Oct 2, 2026
Merged

barnabasbusa merged 2 commits into
mainfrom
bbusa/bump-go-eth2-client-heze

Conversation

@barnabasbusa

@barnabasbusa barnabasbusa commented Oct 2, 2026 •

Copy link
Copy Markdown
Contributor

buildoor crash-loops on focil-devnet-0 with failed to decode heze beacon state: the pinned go-eth2-client decodes Heze states with the Gloas types, but Heze adds inclusion_list_bits to ExecutionPayloadBid (EIP-7805), so the offsets are off by two bytes. v0.1.8 has real Heze types and decodes a live lodestar Heze state from focil-devnet-0 cleanly. This bumps it (pulling dynamic-ssz and hashtree-bindings along) and updates TestHandleSubmitBeaconBlock_ProposalVersion to send a real Heze block for the Heze case, since a Gloas-shaped body is now correctly rejected for missing inclusion_list_bits.

@barnabasbusa
barnabasbusa enabled auto-merge October 2, 2026 13:12

@redpandabot redpandabot Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Dependency bump of go-eth2-client to v0.1.8 (with dynamic-ssz and hashtree-bindings pulled along) to fix Heze beacon state decoding. Verified: OSV is clean for all three new versions, the transitive bumps match go-eth2-client v0.1.8's own requirements exactly, the casbin/govaluate removal is the correct graph change (dynamic-ssz dropped it), and v0.1.8 contains real Heze types with ExecutionPayloadBid.InclusionListBits (ssz-size:"2"). No findings.


Reviewed 2 changed file(s) @ c31cdddc — no blocking issues found.
Red pandas are neither bears nor raccoons — they're the sole survivors of their own family, Ailuridae.

@barnabasbusa
barnabasbusa merged commit 0f411c6 into main Oct 2, 2026
6 checks passed
@barnabasbusa
barnabasbusa deleted the bbusa/bump-go-eth2-client-heze branch October 2, 2026 13:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants