The command for running a node comes with a few settings: it includes mappings for cryptographic keys, data directories and logs, as well as network ports, the application that will run when the docker image is executed and the file of node validators signature.
Import genesis config and the generated .pem file (BLS Key).
Select the destination DB folder.
Save log files and set the log folders
If one wants to monitor the node using log files, the flag --use-log-view must be passed. Otherwise, the standard view is a visual interface as seen below.
When you are done setting up and running your node, you are expected to see information about your node, the blockchain itself, as well as data from your own computer, just like the example below:
A node running, showing how many blocks were proposed and accepted, current blocks, slots and connected nodes, last generated hash, computational information, epoch and network processes and a basic log info segment.
Run node in the background the first time
When running in the background, add parameter --use-log-view and replace --rm for -d
curl -k https://backup.testnet.klever.finance/kleverchain.testnet.latest.tar.gz | tar -xz -C ./node
You can also opt for using fast sync with --start-from-epoch flag. This will indicate node to download last epoch only and start sync from there.
After the first node run, the subsequent commands must remove the flag --start-in-epoch.
This flag is only for node initialization without a db, if the node already has a db, you just need to sync from the last block saved or delete the database and start from the last epoch info.