Nodle Chain Wiki
Running a Full Node

What is a Full Node

A full node is a node that keeps most of the blockchain's state on the server's disk and makes it available to its clients. For the Nodle Chain, it may also "prune" some of its saved data to save some disk space.

Get Started

We will assume you have a server running and installed the required dependencies. The following instructions will help you start a full node, you will then have to wait for it to sync with the Blockchain.

With Docker

Our preferred way to setup and manage nodes is with docker, indeed you can start your node now with only one command:
docker run -v $(pwd)/nodle:/data -p 9944:9944 -p 30333:30333 -t -i ghcr.io/nodlecode/chain:master --ws-external --rpc-cors all --chain main
You can even use the flag --restart always -d instead of -i to make sure your node restart when docker is started (i.e. when your server boots).
Explaining how docker works is outside of this wiki's scope but please let us explain a few flags;
  • We have the node use the nodle folder that you must have previously created according to our instructions via -v $(pwd)/nodle:/data in order to persist the chain's data on your server even between restarts and thus make sure you do not have to resync the whole blockchain every time your container restart.
  • We expose some ports to let you interact with your node and the traditional tools without any hassle via -p 9944:9944 -p 30333:30333.
  • We use --ws-external --rpc-cors all in order to make sure you can query your node as intended. Indeed, because we run inside a docker container some basic sanity checks won't work and need to be disabled.
  • We specify which chain to sync with via --chain main, if you wanted to sync with our test network you could replace it with --chain arcadia.
If you would like to run a specific version of the container, you can view the available tags on the Github Container Registry.

With a Compiled Binary

You can start a node quickly via the following command:
$ nodle-chain --chain main
This will start the node and persist its data on your filesystem. You can switch between chains via the --chain flag, for instance, to sync with our test network you could use --chain arcadia.
Configuring your server to have the node start every time the server boots is outside of the scope of this wiki, however you could do so via systemd.

Expert Commands

Starting the Node in Archive Mode

By default, the full node will prune some of its data to save space on the disk. If you would like to keep this data (maybe you are hosting a public node and want to keep the complete data) you can add the flag --pruning=archive, we typically use it on our own public nodes.

Syncing Faster

On some machines, you can use the flag --wasm-execution compiled to synchronize with the chain networks faster (we often have a 10x boost when using it). This is typically available and well supported on machines with a x86_64 architecture. We didn't include it in the previously listed commands to avoid any potential bugs or crashes as it may not work as well with less traditional servers; but if you can use it you definitely should!

Choosing a Name for your Node

You can view the currently running nodes and their names on the Polkadot Telemetry Portal.
By default, a name for your node is chosen randomly, if you'd like to personalize it you can use the --name flag. For instance you could use --name "This is my first Nodle Chain full node".
Last modified 4mo ago