Skip to content

Latest commit

聽

History

History
108 lines (81 loc) 路 4.7 KB

terrad_keys.mdx

File metadata and controls

108 lines (81 loc) 路 4.7 KB
Raw

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:

    os          Uses the operating system's default credentials store.
    file        Uses encrypted file-based keystore within the app's configuration directory.
                This keyring will request a password each time it is accessed, which may occur
                multiple times in a single command resulting in repeated password prompts.
    kwallet     Uses KDE Wallet Manager as a credentials management application.
    pass        Uses the pass command line utility to store and retrieve keys.
    test        Stores keys insecurely to disk. It does not prompt for a password to be unlocked
                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:

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

Options

  -h, --help                     help for keys
      --home string              The application home directory (default "terra")
      --keyring-backend string   Select keyring's backend (os|file|test) (default "os")
      --keyring-dir string       The client Keyring directory; if omitted, the default 'home' directory will be used
      --output string            Output format (text|json) (default "text")

Subcommands

Keys subcommands

Usage:
  terrad keys [command]

Available Subcommands (click for more info):

  // link[3:138] /develop/terrad/commands/keys/terrad_keys_add
  add         Add an encrypted private key (either newly generated or recovered), encrypt it, and save to <name> file
  // link[3:138] /develop/terrad/commands/keys/terrad_keys_delete
  delete      Delete the given keys
  // link[3:138] /develop/terrad/commands/keys/terrad_keys_export
  export      Export private keys
  // link[3:138] /develop/terrad/commands/keys/terrad_keys_import
  import      Import private keys into the local keybase
  // link[3:138] /develop/terrad/commands/keys/terrad_keys_list
  list        List all keys
  // link[3:138] /develop/terrad/commands/keys/terrad_keys_migrate
  migrate     Migrate keys from the legacy (db-based) Keybase
  // link[3:138] /develop/terrad/commands/keys/terrad_keys_mnemonic
  mnemonic    Compute the bip39 mnemonic for some input entropy
  // link[3:138] /develop/terrad/commands/keys/terrad_keys_parse
  parse       Parse address from hex to bech32 and vice versa
  // link[3:138] /develop/terrad/commands/keys/terrad_keys_show
  show        Retrieve key information by name or address

Flags:
  -h, --help                     help for keys
      --home string              The application home directory (default "/Users/.terra")
      --keyring-backend string   Select keyring's backend (os|file|test) (default "os")
      --keyring-dir string       The client Keyring directory; if omitted, the default 'home' directory will be used
      --output string            Output format (text|json) (default "text")

Global Flags:
      --log_format string   The logging format (json|plain) (default "plain")
      --log_level string    The logging level (trace|debug|info|warn|error|fatal|panic) (default "info")
      --trace               print out full stack trace on errors

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

Options

  -h, --help   help for terrad

See also

See also