Skip to content

Bump go-eth2-client to ethpandaops master for v1.7.0-alpha.5#649

Closed
barnabasbusa wants to merge 1 commit intoethpandaops:masterfrom
barnabasbusa:update/go-eth2-client-master
Closed

Bump go-eth2-client to ethpandaops master for v1.7.0-alpha.5#649
barnabasbusa wants to merge 1 commit intoethpandaops:masterfrom
barnabasbusa:update/go-eth2-client-master

Conversation

@barnabasbusa
Copy link
Copy Markdown
Collaborator

Summary

Upgrade `github.com/ethpandaops/go-eth2-client` from `v0.0.1` to master (`v0.0.2-0.20260420095341-76d6596ff4bc` / commit `76d6596`), which carries the consensus-specs v1.7.0-alpha.5 spec updates:

  • `execution_requests_root` added to `ExecutionPayloadBid`.
  • `parent_execution_requests` added to `BeaconBlockBodyGloas`.
  • `state_root` removed from `ExecutionPayloadEnvelope`.
  • Various field-order and naming fixes per consensus-specs #5108, #5113, #5117, etc.

Why

Running dora against a gloas-at-alpha.5 network (geth `glamsterdam-devnet-0` + Prysm `v1.7.0-alpha.5`) currently fails to decode recent beacon state/block SSZ because the struct layouts on `v0.0.1` predate alpha.5.

Changes

  • `go.mod` / `go.sum` — bump `ethpandaops/go-eth2-client` to master.
  • `indexer/beacon/epochstate.go` — derive the post-payload state HTR locally via `parentState.Gloas.HashTreeRoot()` after `ApplyExecutionPayload`, since the envelope no longer carries a `state_root` field in alpha.5. Previously read via `payload.Message.StateRoot`, which no longer exists on the struct.

Test plan

  • `go build ./...`
  • Run against a live alpha.5 devnet and verify epoch replay continues to track post-payload state roots through gloas slots.

- Upgrade github.com/ethpandaops/go-eth2-client from v0.0.1 to the
  current master tip (pseudo-version v0.0.2-0.20260420095341-76d6596ff4bc),
  which carries the alpha.5 spec updates (execution_requests_root on
  ExecutionPayloadBid, parent_execution_requests on BeaconBlockBodyGloas,
  state_root removed from ExecutionPayloadEnvelope, etc).

- epochstate.go: compute the post-payload state HTR locally after
  ApplyExecutionPayload instead of reading it from payload.Message.StateRoot,
  since the envelope no longer carries a state_root field in alpha.5.
@barnabasbusa
Copy link
Copy Markdown
Collaborator Author

closing in favor of #648

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