Better options for managing large numbers of keys

Description

From @protolambda

Hey, is there some better way to run multiple validators with Teku. Instead of passing a huge list to --validators-key-files in the CLI? Lighthouse does something neat where you specify just a secrets dir, and each password file is named by pubkey, so the client can find them.

Or maybe use a csv or json of account -> password mappings? If a directory is too complicated to implement on what’s already there?

I’ll try generating the CLI argument, but it would be neat to just have Teku resolve where to find the passphrases for the key files

[ajsutton]

@protolambda For the record any command line option in Teku can also be put in a YAML config file. But it’s still annoying to have to list every key individually.

[rolfyone]

to flatten the folder structure, we’ll change:

├── validator_814a1a6
│   ├── validator_814a1a6.json
│   └── withdrawal_8b3ad4d.json
├── validator_81ee3ca
│   ├── validator_81ee3ca.json
│   └── withdrawal_8077d79.json

for validator 814a1a6 (pubkey), we will generate

key/814a1a6_validator.json
key/814a1a6_withdrawal.json

and its password would be in

secrets/814a1a6_validator
secrets/814a1a6_withdrawal

then part 2 is specifying the key folder and secrets folder to make this all work… they could easily be broken into separate concerns and worked on independent of each other at this point.