Running a main network node

1/ Initialize your node

Replace <moniker> by the node name of your choice

$ lumd init <moniker> --chain-id lum-network-1

2/ Edit the config files

$ nano ~/.lumd/config/config.toml

Search for "seed_peers" and replace the value as following:

seeds = "19ad16527c98b782ee35df56b65a3a251bd99971@peer-1.mainnet.lum.network:26656"

Once opened, search for "persistent_peers" and replace the value as following:

persistent_peers = "b47626b9d78ed7ed3c413304387026f907c70cbe@peer-0.mainnet.lum.network:26656,[email protected]:26656,[email protected]:26656,[email protected]:26656,[email protected]:26656,[email protected]:36656,[email protected]:46656,[email protected]:26656,[email protected]:26656,[email protected]:26656"

Get the genesis file and put it in ~/.lumd/config/genesis.json (you can replace it if one was generated automatically) and double check the sha256sum.

$ curl -s  https://raw.githubusercontent.com/lum-network/mainnet/master/genesis.json > ~/.lumd/config/genesis.json

$ sha256sum ~/.lumd/config/genesis.json
3bbbd7aff6c545126d869fc683f6344e65ae71b048b25540826cd2f3be91a24c

2-bis/ Synchronize from latest up-to-date state machine

You are offered a possibility to avoid syncing every single code / state machine upgrade by using ChainLayer's QuickSync service.

You can find relevant URLs and hashes here: https://quicksync.io/networks/lum.html

Different versions are available:

  • Pruned: lightweight version of the state machine, only contains recent blocks / transactions in full

  • Default: standard version of the state machine

When using the commands provided by QuickSync, please make sure that you edit the relevant paths and other configuration according to your setup.

3/ Start your node

You will now notice that the node starts to sync the blockchain history.

But, as soon as you quit the SSH screen or close the window, you will kill it. To avoid doing this launch it in a daemon process:

Copy and paste the following and update <YOUR_HOME_PATH>:

Enable and start the new service:

Check your node status:

Check your node logs:

Last updated

Was this helpful?