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

Check why Lighthouse validator exits are failing with Charon #251

Closed
4 tasks
boulder225 opened this issue Jan 30, 2024 · 1 comment
Closed
4 tasks

Check why Lighthouse validator exits are failing with Charon #251

boulder225 opened this issue Jan 30, 2024 · 1 comment
Labels
protocol protocol team tickets V1

Comments

@boulder225
Copy link

🎯 Problem to be solved

Lighthouse validator exits are failing with Charon, showing a "signature not verified" error. This issue persists even though the same keystore works with Teku. The problem might relate to the validator's private key not being recognized by Charon, or it could be due to an undocumented process for Lighthouse exits.

🛠️ Proposed solution

  • Verify if the keystore-1.json used for signing the exit is listed in cluster-lock.json.
  • Cross-check the public key in keystore-1.json against the pubshare in the lock file.
  • Test the Lighthouse validator exit command on a core team node using Docker
  • Check why voluntary exits with Lighthouse are not documented, and update the documentation if necessary.
@github-actions github-actions bot added the protocol protocol team tickets label Jan 30, 2024
@boulder225 boulder225 reopened this Jan 30, 2024
@dB2510
Copy link
Collaborator

dB2510 commented Jan 31, 2024

Hey team! Please add your planning poker estimate with Zenhub @dB2510 @gsora @pinebit @xenowits

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
protocol protocol team tickets V1
Projects
None yet
Development

No branches or pull requests

2 participants