Client Diversity: Prysm VC <> Teku BN + Prysm VC <> Lighthouse BN does not work

[ybstaked]

🐞 Bug Report

Description

Prysm Validator is not able to validate connecting with Teku Beacon. We used flag --enable-beacon-rest-api --beacon-rest-api-provider http://cl-teku-beacon:5051

Has this worked before in a previous version?

I saw this note here: #12320 (comment). I'd like to know when this will be made stable interface in releases, as this is important for client diversity.

🔬 Minimal Reproduction

validator --accept-terms-of-use --attest-timely --wallet-dir=/home/prysm/ --enable-beacon-rest-api --beacon-rest-api-provider http://cl-teku-beacon.eth2-prater:5051 --log-file=/tmp/ethereum2.log --wallet-password-file file.txt --prater --monitoring-host 0.0.0.0 --proposer-settings-file=/home/prysm/remote/new-fee-recipient.json --enable-builder --validators-external-signer-public-keys=\"http://$POD_IP:5050/api/v1/eth2/publicKeys\" --validators-external-signer-url=\"http://$POD_IP:5050\"

🔥 Error

Process fails without any errors.

🌍 Your Environment

Operating System:

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

  
v4.0.5
  

Anything else relevant (validator index / public key)?

[ybstaked]

From discord: https://discord.com/channels/476244492043812875/781210739762397234/1111479814667370496

[nisdas]

cc @rkapka

[rkapka]

Hi @ybstaked , Prysm validator does not work with non-Prysm beacon nodes at the moment. We are currently completing an experimental version of the validator that will allow this.

[ybstaked]

Hi team, any update on this? I also discovered that Prysm VC does not work with Lighthouse BN.

time="2023-07-27 17:54:15" level=warning msg="Could not determine if beacon chain started" error="could not receive ChainStart from stream: rpc error: code = Unimplemented desc = unexpected HTTP status code received from server: 404 (Not Found); transport: received unexpected content-type "application/json": could not connect" prefix=validator
time="2023-07-27 17:54:25" level=info msg="Syncing with beacon node to align on chain genesis info" prefix=validator
time="2023-07-27 17:54:25" level=warning msg="Could not determine if beacon chain started" error="could not receive ChainStart from stream: rpc error: code = Unimplemented desc = unexpected HTTP status code received from server: 404 (Not Found); transport: received unexpected content-type "application/json": could not connect" prefix=validator

Context here: https://discord.com/channels/605577013327167508/605577013331361793/1134182157636612106

• Also relevant: https://github.com/TobiWo/ethereum-consensus-client-cross-connectivity

[nisdas]

Tagging @rkapka as he has been working on this for the last few months.

[prestonvanloon]

The latest compatibility matrix may be found in the ethpandaops/ethereum-package repo https://github.com/ethpandaops/ethereum-package?tab=readme-ov-file#beacon-node--validator-client-compatibility

[saolyn]

Closing this in favor of #13852