You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Validator client: read the keymanager API token from a file #820
The validator client's keymanager API always reads its bearer token from <validators-dir>/api-token.txt, and generates one when that file is missing (load_or_create_token, crates/validator/src/http_api/mod.rs). There is no flag to point it at an existing token file.
Where it shows up
ethereum-package gives every validator client one shared token (static_files/keymanager/keymanager.txt), so its tooling can call any client's keymanager API with the same credential. The other clients take that file by flag:
Client
Flag
Nimbus, Prysm
--keymanager-token-file
Lodestar
--keymanager.tokenFile
Teku
--validator-api-bearer-file
For ethlambda, the launcher in ethpandaops/ethereum-package#1515 copies the shared file into <validators-dir>/api-token.txt before starting the client. That works, but it depends on our internal filename and on a shell wrapper around the binary.
Proposal
--keymanager-token-file <path> on ethlambda validator: read the token from that path instead of <validators-dir>/api-token.txt, with the same checks as today (trimmed, at least 16 characters, refuse an unusable file rather than regenerate it). Never write to that path. Without the flag, nothing changes.
Activity