Closed barnabasbusa closed 2 months ago
Could you please provide more information? There is no reason for VC to request genesis
state from BN. But anyway i do not see from your issue that something requests for genesis
state.
This is likely related to Prysm VC sending an empty statuses array in POST /eth/v1/beacon/states/head/validators
. Have seen the same issue with Lodestar but we now handle it in the same way as omitting the statuses which resolved the issue.
Fixed as of: nimbus - unstable-85c2850
Describe the bug
We are in the process to test cross beacon <> validator client compatibility, and found a bug when testing nimbus CL with prysm VC.
Prysm reports:
Nimbus reports:
Snooper between cl <> vc reports:
It seems like prysm is stuck on requesting genesis state, and stops there.
Expected behavior
I would expect all client combinations would work.
Steps to reproduce
config.yaml:
kurtosis run github.com/kurtosis-tech/ethereum-package --args-file config.yaml
Additional context
Current BN <> VC Compatibility list tracker
Operating system
Linux
Nimbus version or commit hash
statusim/nimbus-eth2:multiarch-latest - sha256:8e79e02b37351bdcf0a4b07c9cb5a8dd23afdf83144a0d948644b72884cdd10d
cc: @pk910