-
Notifications
You must be signed in to change notification settings - Fork 773
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compatibility with Teku VC for voluntary-exit #4711
Comments
Hey @heejin-github thanks for bringing this to our attention. Lighthouse generally updates the You might be able to work around the issue by using an older version of Teku that doesn't expect this field. It's my opinion that Teku shouldn't be so strict here, but we can also fix it on our side for the next release. |
Hey @michaelsproul |
I'll leave it open so we can track it |
Hey, @michaelsproul @paulhauner |
Description
I'm using LightHouse BN, and validator operated with Teku VC client.
If I'm trying to voluntary exit with Teku VC client, it was failed to retrieve network spec constant
MAX_REQUEST_BLOCKS
from beacon node endpoint as below. but, LightHouse BN didn't provide it.Teku seems to check network spec configuration before run voluntary exit.
Version
Present Behaviour
LightHouse BN didn't provide
MAX_REQUEST_BLOCKS
via beacon API./eth/v1/config/spec
Expected Behaviour
Provide
MAX_REQUEST_BLOCKS
constant value through beacon API/eth/v1/config/spec
Steps to resolve
Need to provide
MAX_REQUEST_BLOCKS
constant value for voluntary-exit with Teku VC Client.The text was updated successfully, but these errors were encountered: