Skip to content

fix: decode heze-devnet-3 blocks and states with go-eth2-client v0.1.11 - #268

Merged
barnabasbusa merged 1 commit into
release/hezefrom
bbusa/heze-go-eth2-client-bump
Oct 22, 2026
Merged

barnabasbusa merged 1 commit into
release/hezefrom
bbusa/heze-go-eth2-client-bump

Conversation

@barnabasbusa

Copy link
Copy Markdown
Contributor

Checkpointz on heze-devnet-3 has been stuck serving the last pre-Heze bundle (epoch 4) since the fork, because every Heze block fails with failed to decode heze signed beacon block: Message.Body.ProposerSlashings: incorrect offset: the pinned go-eth2-client predates EIP-8015 dropping eth1 data and deposits from the Heze containers. Bumping to v0.1.11 decodes the devnet's finalized Heze block and state (slot 10752), which the old pin rejects; build, vet, tests and lint pass. Slot timing after the 12s → 9s change still needs ethpandaops/ethwallclock#11.

@barnabasbusa
barnabasbusa requested a review from samcm as a code owner October 22, 2026 13:30
@barnabasbusa
barnabasbusa merged commit 64a9083 into release/heze Oct 22, 2026
12 checks passed
@barnabasbusa
barnabasbusa deleted the bbusa/heze-go-eth2-client-bump branch October 22, 2026 13:30

@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.

Minimal dependency bump of ethpandaops/go-eth2-client from a v0.1.8 pseudo-version to tagged v0.1.11, solely to decode heze-devnet-3 blocks/states after EIP-8015 container changes. Only go.mod and the two corresponding go.sum lines change; OSV reports no vulnerabilities for v0.1.11 and it is a tagged release of the same module/organization. Clean bump, nothing to report.


Reviewed 2 changed file(s) @ cab51fbe — no blocking issues found.
"Make it work, make it right, make it fast." — Kent Beck

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.

1 participant