Create, import, export and delete keys using the CLI keyring.

The keyring holds the private/public keypairs used to interact with the node. An initial validator key needs to be set up before running the node so that blocks can be correctly signed. The private key can be stored as a file in different locations called "backends" for the operating system's own key storage.

To create a new key in the keyring, run the add subcommand with a <key_name> argument. You will have to provide a password for the newly generated key.

This command generates a new 24-word mnemonic phrase, storing it to the relevant backend before it outputs this information about the keypair. If this keypair is to be used to hold value-bearing tokens make sure to write down the mnemonic phrase somewhere safe!

By default, the keyring generates an eth_secp256k1 key. The keyring also supports ed25519 keys, which may be created by passing the --algo flag. A keyring can hold both types of keys simultaneously.

Last updated