lighthouse icon indicating copy to clipboard operation
lighthouse copied to clipboard

No Bellatrix preset in `/eth/v1/config/spec`

Open michaelsproul opened this issue 2 years ago • 4 comments

Description

There's a TODO(merge) here which prevents Lighthouse from serving the Bellatrix presets on /eth/v1/config/spec:

https://github.com/sigp/lighthouse/blob/21dec6f603edd53ad8d2372941c77ab8098d3b5a/consensus/types/src/config_and_preset.rs#L18-L20

We should try re-enabling that preset and possibly removing all of the other defaults added in https://github.com/sigp/lighthouse/pull/2934.

We should be careful not to break compatibility with any recent versions of Lighthouse or the other clients. I think the VC has become more liberal in what it will accept since that old compat PR was made, but we need to check.

Having dynamic logic to only serve the Bellatrix preset if the Bellatrix epoch is set is another (potentially higher effort) option

michaelsproul avatar Jul 29 '22 07:07 michaelsproul

Hi @michaelsproul, while connecting the teku vc to the lighthouse bn I'm receiving the following error:

failed to retrieve network spec from beacon node endpoint 'http://lighthouse-beacon-prater:5052/'.
Details: Missing value for spec constant 'INACTIVITY_PENALTY_QUOTIENT_BELLATRIX'

This only happens when teku is running with --network=auto. So is this issue here the reason for the error I receive? If it is not I would open a new issue.

TobiWo avatar Aug 02 '22 11:08 TobiWo

@tobisako Yeah this issue is the cause of that. So Teku is usable if you specify the network manually?

michaelsproul avatar Aug 02 '22 12:08 michaelsproul

@TobiWo teku should work if you specify for example: --network=goerli

dB2510 avatar Aug 02 '22 12:08 dB2510

@michaelsproul Yes, if I specify the network manually, as stated by @dB2510, everything works fine.

TobiWo avatar Aug 02 '22 13:08 TobiWo

Resolved via #3425 :tada:

paulhauner avatar Aug 12 '22 00:08 paulhauner