How to setup a Q Fullnode
Setup your Server
You must prepare your server / machine to begin. One possibility is to use a local machine, alternatively you can use a cloud instance on AWS for example. There is a good external tutorial on how to get started with Ethereum on AWS. You can use this tutorial as a basic reference.
Get basic Configuration
Clone the repository
$ git clone https://gitlab.com/q-dev/mainnet-public-tools
and go to the
$ cd mainnet-public-tools/fullnode
This directory contains the
docker-compose.yaml file for quick launching of the full node with preconfigurations on rpc, blockchain explorer using
.env file (which can be created from
Copy the file
.env and configure to your needs.
$ cp .env.example .env $ nano .env
Choose ports (or leave default values) for node rpc api and blockchain explorer by editing the
EXT_PORT=<rpc port> EXPLORER_PORT=<blockchain explorer port>
Launch the node by executing the following command from
$ docker-compose up -d
Verify your Installation
After node is launched, it starts syncing with network.
The setup includes a local blockchain explorer. You can browse blocks, transactions and accounts via your browser by opening the url
PORT is the number you chose above for EXPLORER_PORT, e.g.
You can check your nodes real-time logs with the following command:
$ docker-compose logs -f --tail "100"
Find additional peers
In case your client can't connect with the default configuration, we recommend that you add an additional flag referring to one of our additional peers (
fullnode: image: $QCLIENT_IMAGE entrypoint: ["geth", "--bootnodes=$BOOTNODE1_ADDR,$BOOTNODE2_ADDR,$BOOTNODE3_ADDR", "--datadir=/data", ...]
Updating Q-Client & Docker Images
To upgrade the node follow the instructions Upgrade Node