Skip to content

Missing version in response of Beacon-API method getPendingConsolidations #7440

@Alleysira

Description

@Alleysira

Overview

Hello developers.

I am conducting API testing on a Electra PoS devnet chain and noticed inconsistencies in the JSON-RPC responses among Prysm, Lighthouse(v7.0.1-e42406d/x86_64-linux), Nimbus, and Teku.

In particular, the /eth/v1/beacon/states/{state_id}/pending_consolidations endpoint returns a truncated response from Lighthouse, which includes only the data,execution_optimistic and finalized field, whereas the version field as required in the spec at beacon-api.

Thanks for your time.

Reproduce

  1. Platform details (OS, architecture): Ubuntu 20.04, x86-64
  2. Branch/commit used: v7.0.1-e42406d/x86_64-linux with geth/besu/nethermind/reth.
  3. Commands being executed: I think the minimal repro is
curl -X GET 'http://localhost:4000/eth/v1/beacon/states/head/pending_consolidations' -H 'accept: application/json'

Results

# lighthouse response
{"data": [], "execution_optimistic": false, "finalized": false}
# expected
{"data": [], "execution_optimistic": false, "finalized": false, "version": "electra"}

Metadata

Metadata

Assignees

Labels

HTTP-APIbugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions