Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Where do you get myvalidatrorkeyname #299

Open
adamb opened this issue Jan 12, 2022 · 5 comments
Open

Where do you get myvalidatrorkeyname #299

adamb opened this issue Jan 12, 2022 · 5 comments

Comments

@adamb
Copy link

adamb commented Jan 12, 2022

https://github.com/Gravity-Bridge/Gravity-Docs/blob/main/docs/setting-up-a-validator.md#send-your-validator-setup-transaction

Has a parameter called myvalidatorkeyname but that's not defined anywhere in the page. Where do we get that from?

@gadost
Copy link
Contributor

gadost commented Jan 12, 2022

myvalidatorkeyname is keyfile name you set on step:
Add your validator key

@adamb
Copy link
Author

adamb commented Jan 12, 2022

myvalidatorkeyname is keyfile name you set on step:
Add your validator key

Thanks for the feedback. In this command?

gravity keys add <my validator key name> --recover <your seed phrase>

Is <my validator key name> a file? I thought it was some hex string key.

@gadost
Copy link
Contributor

gadost commented Jan 12, 2022

<my validator key name> is string key name

Use:   "gravity keys add <name>",
Add an encrypted private key (either newly generated or recovered), encrypt it, and save to <name> file

@adamb
Copy link
Author

adamb commented Jan 13, 2022

You're supposed to encrypt the key and save that to a file?

Can you describe how to encrypt a key? What should the file be named? Where should the file be stored? Seems like that should be added to the documentation too.

@gadost
Copy link
Contributor

gadost commented Jan 13, 2022

you can find out more via
gravity keys add -h

Derive a new private key and encrypt to disk.
Optionally specify a BIP39 mnemonic, a BIP39 passphrase to further secure the mnemonic,
and a bip32 HD path to derive a specific account. The key will be stored under the given name
and encrypted with the given password. The only input that is required is the encryption password.
If run with -i, it will prompt the user for BIP44 path, BIP39 mnemonic, and passphrase.
The flag --recover allows one to recover a key from a seed passphrase.
If run with --dry-run, a key would be generated (or recovered) but not stored to the
local keystore.
Use the --pubkey flag to add arbitrary public keys to the keystore for constructing
multisig transactions.

Also you can read cosmos-sdk basics documentation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants