Lighthouse CL < > Prysm VC incompatibility

[barnabasbusa]

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:

time="2024-07-04 11:57:36" level=info msg="Waiting for deposit to be observed by beacon node" prefix=client pubkey=0xb9e03b94bb69 status="UNKNOWN_STATUS

Lighthouse reports:

nothing out of the ordinary

Snooper between cl <> vc reports:

time="2024-07-04T14:12:48Z" level=info msg="REQUEST #11: POST /eth/v1/beacon/states/head/validators" length=6487 type=json
{
  "ids": [
    "0xaaf6c1251e73fb600624937760fef218aace5b253bf068ed45398aeb29d821e4d2899343ddcbbe37cb3f6cf500dff26c",
   ...
"0x8c0d15baa72bfcd317e9b9402ca9bb6e7ae1db35ffce7faccae0bd19b3c8e5de7d5524aef0377770b3a90626627a9304",
    "0xaf61f263addfb41c46d66e60ecfb598a5942f648f58718b6b4e4c92019fdb12328efbff98703134bcf28e9c1fab4bb60"
  ],
  "statuses": []
}

time="2024-07-04T14:12:48Z" level=info msg="RESPONSE #11: POST /eth/v1/beacon/states/head/validators" length=58 status=200 type=json
{
  "data": [],
  "execution_optimistic": false,
  "finalized": false
}

time="2024-07-04T14:12:48Z" level=info msg="REQUEST #12: GET /eth/v1/node/version" length=0 type=json
time="2024-07-04T14:12:48Z" level=info msg="RESPONSE #12: GET /eth/v1/node/version" length=62 status=200 type=json
{
  "data": {
    "version": "Lighthouse/v5.2.1-9e12c21/aarch64-linux"
  }
}

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:

participants:
  - cl_type: lighthouse
    vc_type: prysm
additional_services:
  - dora
snooper_enabled: true
global_log_level: debug

kurtosis run github.com/kurtosis-tech/ethereum-package --args-file config.yaml

Additional context

Current BN <> VC Compatibility list tracker

Has this worked before in a previous version?

No response

🔬 Minimal Reproduction

No response

Error

No response

Platform(s)

No response

What version of Prysm are you running? (Which release)

No response

Anything else relevant (validator index / public key)?

No response

cc: @pk910

[nflaig]

This is likely related to Prysm VC sending an empty statuses array in POST /eth/v1/beacon/states/head/validators