terrad keys

Manage your application's keys.

Synopsis

The keys command contains the Terrad keyring management commands. These keys may be in any format supported by the Tendermint crypto library and can be used by light-clients, full nodes, or any other application that needs to sign with a private key.

The keyring supports the following backends:

Terrad

_8

os Uses the operating system's default credentials store.

_8

file Uses encrypted file-based keystore within the app's configuration directory.

_8

This keyring will request a password each time it is accessed, which may occur

_8

multiple times in a single command resulting in repeated password prompts.

_8

kwallet Uses KDE Wallet Manager as a credentials management application.

_8

pass Uses the pass command line utility to store and retrieve keys.

_8

test Stores keys insecurely to disk. It does not prompt for a password to be unlocked

_8

and it should be used only for testing purposes.

KWallet and pass backends depend on external tools. Refer to their respective documentation for more information:

• KWallet https://github.com/KDE/kwallet
• pass https://www.passwordstore.org/

The pass backend requires GnuPG: https://gnupg.org/

Options

Terrad

_5

-h, --help help for keys

_5

--home string The application home directory (default "terra")

_5

--keyring-backend string Select keyring's backend (os|file|test) (default "os")

_5

--keyring-dir string The client Keyring directory; if omitted, the default 'home' directory will be used

_5

--output string Output format (text|json) (default "text")

Subcommands

Terrad

_30

Keys subcommands

_30

_30

Usage:

_30

terrad keys [command]

_30

_30

Available Subcommands (click for more info):

_30

_30

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

_30

delete Delete the given keys

_30

export Export private keys

_30

import Import private keys into the local keybase

_30

list List all keys

_30

migrate Migrate keys from the legacy (db-based) Keybase

_30

mnemonic Compute the bip39 mnemonic for some input entropy

_30

parse Parse address from hex to bech32 and vice versa

_30

show Retrieve key information by name or address

_30

_30

Flags:

_30

-h, --help help for keys

_30

--home string The application home directory (default "/Users/.terra")

_30

--keyring-backend string Select keyring's backend (os|file|test) (default "os")

_30

--keyring-dir string The client Keyring directory; if omitted, the default 'home' directory will be used

_30

--output string Output format (text|json) (default "text")

_30

_30

Global Flags:

_30

--log_format string The logging format (json|plain) (default "plain")

_30

--log_level string The logging level (trace|debug|info|warn|error|fatal|panic) (default "info")

_30

--trace print out full stack trace on errors

_30

_30

Use "terrad keys [command] --help" for more information about a command.

Options

Terrad

_1

-h, --help help for terrad

See also

• Terrad commands

See also

• terrad - The Terra Blockchain's CLI and node daemon.
• terrad keys add - Add an encrypted private key (either newly generated or recovered), encrypt it, and save to <name> file.
• terrad keys delete - Delete the given keys
• terrad keys export - Export private keys
• terrad keys import - Import private keys into the local keybase
• terrad keys list - List all keys
• terrad keys migrate - Migrate keys from the legacy (db-based) Keybase
• terrad keys mnemonic - Compute the bip39 mnemonic for some input entropy
• terrad keys parse - Parse address from hex to bech32 and vice versa
• terrad keys show - Retrieve key information by name or address