var img = document.createElement('img'); img.src = "https://terradocs.matomo.cloud//piwik.php?idsite=1&rec=1&url=https://docs.terra.money" + location.pathname; img.style = "border:0"; img.alt = "tracker"; var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(img,s);
Skip to main content

terrad keys export

Export private keys.

Synopsis

Export a private key from the local keyring in ASCII-armored encrypted format.

When both the --unarmored-hex and --unsafe flags are selected, cryptographic private key material is exported in an INSECURE fashion that is designed to allow users to import their keys in hot wallets.

danger

This feature is for advanced users only that are confident about how to handle private keys work and are FULLY AWARE OF THE RISKS. If you are unsure, you may want to do some research and export your keys in ASCII-armored encrypted format.

Usage

Terrad
Copy

_1
terrad keys export <name> [flags]

Options

Terrad
Copy

_3
-h, --help help for export
_3
--unarmored-hex Export unarmored hex privkey. Requires --unsafe.
_3
--unsafe Enable unsafe operations. This flag must be switched on along with all unsafe operation-specific options.

Options inherited from parent commands

Terrad
Copy

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

See also