Add --val-private-key-file
flag for key assignment tx
#1159
Labels
more-info-needed
Further information is requested
S: ImprovingThings
Improving things: Customer requests, performance improvements, reliability and usability
type: feature-request
New feature or request improvement
Summary
This issue aims to propose adding a flag to key-assignment command in order to make it simpler for validator that are using a remote signer.
Problem Definition
When a validator use a remote signer then the
$HOME/.gaia/config/priv_validator_key.json
file is not / should not be the right private key used to sign blocks.So when doing key-assignment the validator would have to re-initiate a temporary
.gaia
folder, reconfigure the CLI endpoint & chain-id, import a wallet to sign the tx and import the correctpriv_validator_key.json
in order to be able to make his key-assignment tx.This is a bit annoying and I think it could be improve simply by adding a flag to the
gaiad tx provider assign-consensus-key
command.It can also be quite confusing, as shown by the many messages on Discord for the Stride ICS migration.
Proposal
Add a flag to
gaiad tx provider assign-consensus-key
command that allow to point to a specificpriv_validator_key.json
file.If the
--priv-validator-key-file
flag is not specified then use the private key inside the home folderThe text was updated successfully, but these errors were encountered: