#Hey all, we're trying to vote on the
strange hull
Noticed someone else faced the issue and fixed it by importing the wallet using mnemonic here #archived-dry-run-chatter message
Do we have to import the wallet again using the mnemonic?
Having validator-wallet.toml keys are not enough?
Are separate keys used for voting in governance and participating in consensus?
leaden herald
You may check your $VALIDATOR_ALIAS key which generated validator address.
that should have a little bit of nam gas.
In general it should be there while booting up.
strange hull
Wouldn't $VALIDATOR_ALIAS be chorusone-validator for us?
I'm not sure if it's a separate thing
Also when I check the balance of the validator account, it has some NAM
namadac balance --owner tnam1qxsx2ezu89gx252kwwluqp7hadyp285tkczhaqg0 --token nam
nam: 2.440395
chrome sorrel
The other way around may be more secure than importing your wallet onto the validator node.
strange hull
That make sense, the thing I am confused about is, I have the validator-wallet.toml on the machine, but it's still not able to sign the governance votes
As mentioned in the message you shared above, it doesn't have the private key to sign the txns, I used it to join-network and it worked, but somehow not working for vote-proposal
So is there some other key to sign the votes?
chrome sorrel
That make sense, the thing I am confused about is, I have the `validator-wallet....
join-network worked because it does not interact with the account. It creates the folder structure and downloads the necessary files to connect to the network.
To sign votes, you need the keypair of the implicit address in wallet.toml you used for the creation of the pre-genesis validator established address.
Let us say you created the pre-genesis validator established address on a laptop.
On the laptop there will be a folder ~/.local/share/namada/pre-genesis
In that folder there is wallet.toml, which contains the keypair to sign validator transactions with.
There is also one subfolder that contains validator-wallet.toml. You copied that to a remote machine that runs the validator.
Now there are 2 options:
- Import the keypair into the remote machine.
- Have the pre-genesis account on the laptop join the network.
Option 1 is risky, because the remote machine is probably a server in a data center you do not control. Also, the validator node is a big target for attacks.
Option 2 is safer, because you can only sign validator transactions from the laptop.
strange hull
Thanks for the details, I'll try this out and see if things work