Run a Node (Using Docker)

Ready to join Campfire, our community-run Namada testnet? 🏕️

Here's how to run a node (using Docker):

Note: you can view the general docs for Namada here.

1. Choose a location for the Namada chain data

We'll use this directory in the example below, but you can choose a different location:


2. Set the appropriate directory permissions

Since the namada user inside the Docker container, which has a user-id of 1000, needs to write to the directory we've just created, we need to change the permissions to allow it to do so.

sudo chown 1000:1000 $NAMADA_DIR

3. Download the Docker image from the GitHub container registry

We'll assume you're using the Docker image from here in the following steps. Pull the image for whichever version of Namada is being used for the current testnet (you can find which version you need by checking the Campfire landing page).

NAMADA_VERSION=v0.39.0 # or whichever version you wish to download
docker pull$NAMADA_VERSION

In this case, the full name of the downloaded image is

We can save the image name to a shell variable for convenience:


4. Get the current chain-id

Check the Campfire landing page; you will need the current chain-id in the following steps.


5. Initialize your node (join-network)

This command will run join-network using the data directory we created in the first step:

docker run --rm -P -i -e NAMADA_NETWORK_CONFIGS_SERVER="" -v $NAMADA_DIR:/home/namada/.local/share/namada -t $DOCKER_IMAGE client utils join-network --chain-id $CHAIN_ID --dont-prefetch-wasm

6. Download the chain WASM files

Download and extract the wasm files from the link on the landing page:

wget -O - | tar -xz -C $NAMADA_DIR/$CHAIN_ID/wasm/ --strip-components=1

7. Add persistent_peers

Find the persistent peer address on the landing page and add it to your node's config file: Note: below is an example value; yours will be slightly different

# in file $NAMADA_DIR/$CHAIN_ID/config.toml
persistent_peers = "tcp://af427e348cd45dd7308be4ea58f1492098e057b8@"

8. Start the node

In this command we are naming our container namada for easy reference later, but you can choose a different name.

This command will start the node:

docker run --name namada -d -P -v $NAMADA_DIR:/home/namada/.local/share/namada $DOCKER_IMAGE node ledger run

The node should now be syncing in the background. You can verify its operation by checking the logs:

docker logs -f namada

You should see entries to indicate new blocks are being indexed, similar to:

2024-06-28T13:38:15.442871Z  INFO namada_node::shell: Committed block hash: d958f287c38dbeb94e07dfb8290c9c620753157510ff1d46899925def0df0b99, height: 798

9. (Optional) Use a snapshot for faster syncing

Rather than syncing your node from the first block, you can use a snapshot taken from a recent block height. The landing page will have a download link to a recent snapshot in tar.lz4 format.

To apply the snapshot:

  1. Stop your node:

docker stop namada
  1. Run sudo apt install lz4 if lz4 is not already installed on your system

  2. Download the tar.lz4 snapshot file from the testnet landing page. The filename will look something like luminara-position.5eef10f5ab83_2024-06-28T13.39.tar.lz4, but the actual filename will differ depending on the chain-id and time the snapshot was created.

wget {filename}
  1. Extract the contents to a temp directory of your choice:

mkdir ~/namada-temp
lz4 -c -d {filename}.tar.lz4  | tar -x -C ~/namada-temp
  1. If your node is a validator, back up your priv_validator_state.json file at this point. (This step is not necessary if you are only running a full node.)

  2. Copy the extracted db directory to {namada-dir}/$CHAIN_ID/ (overwrite the existing db directory) and copy the cometbft/data directory to {namada-dir}/$CHAIN_ID/cometbft/ (overwrite the existing data directory):

sudo cp -a namada-temp/db/ $NAMADA_DIR/$CHAIN_ID
sudo cp -a namada-temp/cometbft/data $NAMADA_DIR/$CHAIN_ID/cometbft
  1. If you backed up your priv_validator_state.json file in step 5, move it back to its original location at $NAMADA_DIR/$CHAIN_ID/cometbft/data/priv_validator_state.json.

  2. Since we have modified the contents of the chain-data directory $NAMADA_DIR, ensure that the permissions have once again been set to allow our container write access:

sudo chown -R 1000:1000 $NAMADA_DIR
  1. Restart your node:

docker restart namada

Verify that it is syncing again by checking the logs. It should now be syncing from the height at which the snapshot was taken.

docker logs -f namada
  1. You can safely delete the downloaded tar.lz4 file and the extracted files from step 4.

rm -rf ~/namada-temp
rm {filename}.tar.lz4

10. (Optional) Become a validator

Note: Detailed instructions can be found in the Post Genesis Validators section of the Namada Docs.

  1. Before initializing your validator, you must have a full node that is fully synced to the head of the chain.

  2. Rather than running commands using docker run, it will be easier to perform the validator setup actions using a shell inside the container. Run the following command to start a bash session inside the container; you should see your command prompt change to something like namada@cedf19f0200e:/$:

docker exec -it namada /bin/bash
  1. Create an implicit account, choosing any alias you like:

namadaw gen --alias $IMPLICIT_ALIAS
  1. Get some tokens from the testnet faucet (you will need tokens both to cover transaction gas costs and to stake to your validator). First, find the address of the account you created in the previous step:

namadaw list --addr

Then, proceed to the faucet and request 1000 tokens to that address. You can check that the tokens arrived in your account with:

namadac balance --owner $IMPLICIT_ALIAS --token nam
  1. Create your validator with an on-chain transaction using the below command (the email parameter is required; however, for testnet you can simply provide a made-up email address). As before, we need to choose a wallet alias (`$VALIDATOR_ALIAS) for our newly created account.

namadac init-validator \
  --commission-rate 0.05 \
  --max-commission-rate-change 0.01 \
  --email $EMAIL \
  --alias $VALIDATOR_ALIAS \
  --account-keys $IMPLICIT_ALIAS \
  --signing-keys $IMPLICIT_ALIAS \
  --threshold 1
  1. Optionally, you can also provide other info to identify your validator including a name, logo, website, etc. (this can be done during init-validator or later on with the change-metadata command).

  2. Restart your node (you will be unable to sign blocks until after you do so).

End your container shell session and return to your system command prompt:


Restart the container:

docker restart namada
  1. Bond some tokens to your validator. It will take two epochs (equal to the pipeline_len) after bonding before your validator becomes active.

Re-enter your container shell:

docker exec -it namada /bin/bash

Use this command to bond tokens from your implicit account to your validator:

namadac bond \
  --source $IMPLICIT_ALIAS \
  --validator $VALIDATOR_ALIAS \
  --amount $AMOUNT

Last updated