You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
time="2024-04-05 12:15:11" level=info msg="Waiting for deposit to be observed by beacon node" prefix=client pubkey=0xa2e2d8384fc8 status="UNKNOWN_STATUS"
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.
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
The text was updated successfully, but these errors were encountered: