Skip to content
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

Investigate rebroadcast duty error w/ Lighthouse v4.3.0 #231

Closed
3 tasks
boulder225 opened this issue Nov 14, 2023 · 0 comments
Closed
3 tasks

Investigate rebroadcast duty error w/ Lighthouse v4.3.0 #231

boulder225 opened this issue Nov 14, 2023 · 0 comments
Labels
protocol protocol team tickets streamline

Comments

@boulder225
Copy link

🎯 Problem to be solved

  • The node named vast-farm is encountering a rebroadcast duty error during the beacon API's validator registration process.
  • The error message indicates a BAD_REQUEST: Unsupported endpoint version: v1 with a 400 status code.
  • This issue is unique to the 'vast-farm' node running Lighthouse v4.3.0, as other nodes on v4.2.0 do not exhibit this problem.
    ERRO bcast Rebroadcast duty error (will retry next epoch): beacon api submit_validator_registrations: nok http response {"label": "submit_validator_registrations", "status_code": 400, "endpoint": "/eth/v1/validator/register_validator", "method": "POST", "data": "{\"code\":400,\"message\":\"BAD_REQUEST: Unsupported endpoint version: v1\",\"stacktraces\":[]}", "duty": "1/builder_registration"}
  • Additionally, there's a need to investigate aggregator duty failures in the core team cluster.

Private Zenhub Image

🛠️ Proposed solution

  • Investigate the compatibility of Lighthouse v4.3.0 with the current beacon API, focusing on endpoint versioning.
  • Review the change logs or documentation for Lighthouse v4.3.0 to identify any relevant changes in API interactions or known issues.
  • Initiate a separate investigation for the aggregator duty failures in the core team cluster, as this might be a related or distinct issue.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
protocol protocol team tickets streamline
Projects
None yet
Development

No branches or pull requests

2 participants