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 migrate

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

Synopsis​

Migrate key information from the legacy (db-based) Keybase to the new keyring-based Keyring. The legacy Keybase used to persist keys in a LevelDB database stored in a 'keys' sub-directory of the old client application's home directory, e.g. $HOME/.gaiacli/keys/. For each key material entry, the command will prompt if the key should be skipped or not. If the key is not to be skipped, the passphrase must be entered. The key will only be migrated if the passphrase is correct. Otherwise, the command will exit and migration must be repeated.

caution

It is recommended to run in 'dry-run' mode first to verify all key migration material.

Usage​

Terrad
Copy

_1
terrad keys migrate <old_home_dir> [flags]

Options​

Terrad
Copy

_2
--dry-run Run migration without actually persisting any changes to the new Keybase
_2
-h, --help help for migrate

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​