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

Prysm-web3signer validator process exits if no public keys are provided #10294

Closed
pablomendezroyo opened this issue Mar 1, 2022 · 2 comments
Closed
Assignees
Labels
Tracking Gotta Catch 'Em All

Comments

@pablomendezroyo
Copy link

💎 Issue

The Prysm-web3signer validator process exits if no public keys are provided --validators-external-signer-public-keys.

Background

Context and background information on the discussion...

Not sure if this is an expected behaviour, but ideally it should keep running, specially for the future once the remote api keymanager on the client is implemented so it keeps listening for requests to upload new validators

Description

The error

time="2022-03-01 14:44:49" level=error msg="could not decode public key for web3signer: : empty hex string" prefix=main
@james-prysm
Copy link
Contributor

currently expected behavior, feature request linked here #10293

@james-prysm james-prysm added the Tracking Gotta Catch 'Em All label Mar 1, 2022
@james-prysm james-prysm self-assigned this May 11, 2022
@james-prysm
Copy link
Contributor

I believe this is fixed in the current version in develop. closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Tracking Gotta Catch 'Em All
Projects
None yet
Development

No branches or pull requests

2 participants