Run a Baklava Full Node
How to get a full node running on the Baklava Network using a prebuilt Docker image.
What is a Baklava Full Node?
Full nodes play a special purpose in the Celo ecosystem, acting as a bridge between the mobile wallets (running as light clients) and the validator nodes.
If you would like to keep up-to-date with all the news happening in the Celo community, including validation, node operation and governance, please sign up to our Celo Signal mailing list here.
You can add the Celo Signal public calendar as well which has relevant dates.
If you are transitioning from the Baklava network prior to the June 24 reset, you will need to start with a fresh chain database. You can either shut down your existing node, delete the celo folder, and continue by following the guide below or create a new node following these directions.
Key differences are:
- New network ID is
62320 - A new image has been pushed to
us.gcr.io/celo-org/geth:baklava - A new genesis block and bootnode enode are included in the Docker image
ReleaseGoldcontracts are available for all previously faucetted addresses here
Prerequisites
- You have Docker installed. If you don’t have it already, follow the instructions here: Get Started with Docker. It will involve creating or signing in with a Docker account, downloading a desktop app, and then launching the app to be able to use the Docker CLI. If you are running on a Linux server, follow the instructions for your distro here. You may be required to run Docker with
sudodepending on your installation environment.
Code you'll see on this page is bash commands and their output.
When you see text in angle brackets <>, replace them and the text inside with your own value of what it refers to. Don't include the <> in the command.
Celo Networks
First, we are going to setup the environment variables required for Baklava network. Run:
export CELO_IMAGE=us.gcr.io/celo-org/geth:baklava
Pull the Celo Docker image
We're going to use a Docker image containing the Celo node software in this tutorial.
If you are re-running these instructions, the Celo Docker image may have been updated, and it's important to get the latest version.
docker pull $CELO_IMAGE
Set up a data directory
First, create the directory that will store your node's configuration and its copy of the blockchain. This directory can be named anything you'd like, but here's a default you can use. The commands below create a directory and then navigate into it. The rest of the steps assume you are running the commands from inside this directory.
mkdir celo-data-dir
cd celo-data-dir
Create an account and get its address
In this step, you'll create an account on the network. If you've already done this and have an account address, you can skip this and move on to configuring your node.
Run the command to create a new account:
docker run -v $PWD:/root/.celo --rm -it $CELO_IMAGE account new
It will prompt you for a passphrase, ask you to confirm it, and then output your account address: Public address of the key: <YOUR-ACCOUNT-ADDRESS>
Save this address to an environment variable, so that you can reference it below (don't include the braces):
export CELO_ACCOUNT_ADDRESS=<YOUR-ACCOUNT-ADDRESS>
This environment variable will only persist while you have this terminal window open. If you want this environment variable to be available in the future, you can add it to your ~/.bash_profile
Start the node
This command specifies the settings needed to run the node and gets it started.
docker run --name celo-fullnode -d --restart unless-stopped --stop-timeout 300 -p 127.0.0.1:8545:8545 -p 127.0.0.1:8546:8546 -p 30303:30303 -p 30303:30303/udp -v $PWD:/root/.celo $CELO_IMAGE --verbosity 3 --syncmode full --http --http.addr 0.0.0.0 --http.api eth,net,web3,debug,admin,personal --light.serve 90 --light.maxpeers 1000 --maxpeers 1100 --etherbase $CELO_ACCOUNT_ADDRESS --baklava --datadir /root/.celo
You'll start seeing some output. After a few minutes, you should see lines that look like this. This means your node has started syncing with the network and is receiving blocks.
INFO [07-16|14:04:24.924] Imported new chain segment blocks=139 txs=319 mgas=61.987 elapsed=8.085s mgasps=7.666 number=406 hash=9acf16…4fddc8 age=6h58m44s cache=1.51mB
INFO [07-16|14:04:32.928] Imported new chain segment blocks=303 txs=179 mgas=21.837 elapsed=8.004s mgasps=2.728 number=709 hash=8de06a…77bb92 age=6h33m37s cache=1.77mB
INFO [07-16|14:04:40.918] Imported new chain segment blocks=411 txs=0 mgas=0.000 elapsed=8.023s mgasps=0.000 number=1120 hash=3db22a…9fa95a age=5h59m30s cache=1.92mB
INFO [07-16|14:04:48.941] Imported new chain segment blocks=335 txs=0 mgas=0.000 elapsed=8.023s mgasps=0.000 number=1455 hash=7eb3f8…32ebf0 age=5h31m43s cache=2.09mB
INFO [07-16|14:04:56.944] Imported new chain segment blocks=472 txs=0 mgas=0.000 elapsed=8.003s mgasps=0.000 number=1927 hash=4f1010…1414c1 age=4h52m31s cache=2.34mB
You will have fully synced with the network once you have pulled the latest block number, which you can look up by visiting at the Baklava Network Stats or Baklava Block Explorer pages.
Security: The command line above includes the parameter --http.addr 0.0.0.0 which makes the Celo Blockchain software listen for incoming RPC requests on all network adaptors. Exercise extreme caution in doing this when running outside Docker, as it means that any unlocked accounts and their funds may be accessed from other machines on the Internet. In the context of running a Docker container on your local machine, this together with the docker -p flags allows you to make RPC calls from outside the container, i.e., from your local host, but not from outside your machine. Read more about Docker Networking here.
Command Line Interface
Once the full node is running, it can serve the Command Line Interface tool celocli. For example:
$ npm install -g @celo/celocli
...
$ celocli node:synced
true
$ celocli account:new
...