Skip to main content

Create A Wallet with Celestia Node

This tutorial will go over using the cel-key utility to generate a wallet on Celestia Node.

While this tutorial will go over installation process of cel-key, it is recommended that you complete the following prerequisites first:

Once you completed the prerequisite, you can proceed with this tutorial.

Using the cel-key utility

Inside the celestia-node repository is a utility called cel-key that uses the key utility provided by Cosmos-SDK under the hood. The utility can be used to add, delete, and manage keys for any DA node type (bridge || full || light), or just keys in general.


You need to first pull down the celestia-node repository:

git clone
cd celestia-node/

It can be built using either of the following commands:

# dumps binary in current working directory, accessible via `./cel-key`
make cel-key


# installs binary in GOBIN path, accessible via `cel-key`
make install-key

For the purpose of this guide, we will use the make cel-key command.

Steps for generating node keys

To generate a key for a Celestia bridge node, do the following:

./cel-key add <key-name> --keyring-backend test --node.type bridge

This will load the key <key-name> into the directory of the bridge node.

Steps for exporting node keys

You can export a private key from the local keyring in encrypted and ASCII-armored format.

./cel-key export <key-name> --keyring-backend test --node.type bridge

You can then import your key with celestia-appd:

celestia-appd keys import <new-key-name> 

Steps for importing node keys

Importing from a mnemonic:

./cel-key add <key-name> --recover --keyring-backend test --node.type bridge

You will then be prompted to enter your bip39 mnemonic.


./cel-key add alice --recover --keyring-backend test --node.type bridge

View all options for cel-key

$ ./cel-key --help
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 use only for testing purposes.
kwallet and pass backends depend on external tools. Refer to their respective documentation for more
The pass backend requires GnuPG:
keys [command]
Available Commands:
add Add an encrypted private key (either newly generated or recovered), encrypt it, and save to <name> file
completion Generate the autocompletion script for the specified shell
delete Delete the given keys
export Export private keys
help Help about any command
import Import private keys into the local keybase
list List all keys
migrate Migrate keys from amino to proto serialization format
mnemonic Compute the bip39 mnemonic for some input entropy
parse Parse address from hex to bech32 and vice versa
rename Rename an existing key
show Retrieve key information by name or address
-h, --help help for keys
--home string The application home directory (default "~")
--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 string Sets key utility to use the node network's directory (e.g. ~/.celestia-light-mynetwork if MyNetwork is passed). (default "arabica-1")
--node.type string Sets key utility to use the node type's directory (e.g. ~/.celestia-light-arabica-1 if --node.type light is passed).
--output string Output format (text|json) (default "text")
Use "keys [command] --help" for more information about a command.