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

Allow external-signers to be specified #758

Closed
rolfyone opened this issue Sep 9, 2024 · 0 comments · Fixed by #791
Closed

Allow external-signers to be specified #758

rolfyone opened this issue Sep 9, 2024 · 0 comments · Fixed by #791

Comments

@rolfyone
Copy link

rolfyone commented Sep 9, 2024

It would be a great addition to be able to configure external-signers in a kurtosis network then have VC's or BN's configured to call those signers...

@barnabasbusa barnabasbusa linked a pull request Oct 7, 2024 that will close this issue
barnabasbusa added a commit that referenced this issue Oct 7, 2024
Adds the `use_remote_signer` flag, outsourcing validator key management
to a remote signer, which validator clients connect to.

Supported by all VCs except Lighthouse through this PR.

Slashing protection DB is not enabled for web3signer since that would
require adding significantly more complexity - creating a separate
postgres DB and running migrations.

I was thinking a lot what to call the remote signer service, in the end
went with `signer-1-geth-lodestar` (this is the remote signer for
`vc-1-geth-lodestar`).

Addresses #263 / #758 

Prerequisite for adding [Vero](https://github.com/serenita-org/vero) as
a validator client - it exclusively uses a remote signer

---------

Co-authored-by: Barnabas Busa <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant