Add validator config file

[yorickdowne]

We'd like to start using Vero with our Stakewise setup. This has "many" keys, all running in a single Web3signer, with multiple VCs.

To be able to use Vero here, we'd need it to have a configuration file that tells it which validators to handle. Right now, it will load all keys that Web3signer has, and that's too broad for this use case.

For ease, this could be patterned after either the Lighthouse file format or the Teku/Prysm file format.

[eth2353]

I'll give this some thought, especially when it comes to how this would work together (and potentially clash) with the Keymanager API. I suppose the Keymanager API would solve for this usecase too, right?

Is there a good reason to run all keys on a single signer? ( We ourselves run many keys across multiple signers, each connected to "its own" Vero VC )

[yorickdowne]

The way this works right now is that the keys are loaded on startup from this file, and then in running state keymanager API is used to add additional keys. The file is recreated on every startup with the full list of keys. This is the Stakewise helm chart and another helm chart derived from it. It has the keys in a PostgreSQL DB and dynamically assigns them to N VCs, depending on how many VCs are running. To clarify, Stakewise charts don’t use keymanager at all. The derived charts do, just for hot-adding keys. I don’t see these charts being adjusted to run a separate Web3signer for each VC. There are actually 3 Web3signer all taking care of the same keys, for resilience, which is something it supports. Not least the design fits well with how EKS works: AWS has a pod limit, no matter how light weight the pod. 3 Web3signer plus N VCs plus a handful of supporting pods makes good use of the available resource, here, the pod limit. Kind Regards, Thorsten Behrens +1-401-275-3204

…

________________________________ From: 'Luca | Serenita' via Engineering ***@***.***> Sent: Saturday, September 21, 2024 4:28:34 PM To: serenita-org/vero ***@***.***> Cc: yorickdowne ***@***.***>; Author ***@***.***> Subject: Re: [serenita-org/vero] Add validator config file (Issue #14) I'll give this some thought, especially when it comes to how this would work together (and potentially clash) with the Keymanager API. I suppose the Keymanager API would solve for this usecase too, right? Is there a good reason to run all keys on a single signer? ( We ourselves run many keys across multiple signers, each connected to "its own" Vero VC ) — Reply to this email directly, view it on GitHub<#14 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ARAII2VSK42ZHBNZHZH6NT3ZXWGCFAVCNFSM6AAAAABOQJJJQCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRVGIZDONJXGU>. You are receiving this because you authored the thread.Message ID: ***@***.***>