FAQ for ALICE
The installation process is currently tested on Linux. Installing a node on other operating systems may be possible but not officially supported yet.
No. It is not possible because a node run on a laptop/PC are likely to have much more downtime than one run on a server.
Although It is technically possible to run numerous nodes on ALICE, it is NOT beneficial and NOT recommended. No matter how many nodes you run on ALICE, you will not be able to run more than one node in the Canary Network. That is because in the Canary network, a mechanism will be applied to verify the uniqueness of each node's operator.
No. Joining ALICE has nothing to do with a Shield Server. A Shield Server is a complementary security measure run by dApps. To get more information about the Shield Server, see here.
The date of node-drop distribution and the Pioneer launch have yet to be announced. The rewards from the ALICE network will be distributed based on the nodes' uptime, so operators should maintain their nodes throughout.
To do so, one should first back up the node. The backed-up config file should then be transferred to a new server and restore the node.
<server-ip>
is actually the public IP of the server that you have used to connect to your server and installed the node on. And if the node is run locally, the <server-ip> is 127.0.0.1
.The node address is the address that your node uses to sign requests with. It is automatically generated by the node and its private key is held in the config file of the node.
The staking address, on the other hand, is the address of the owner of the node which is used to stake tokens when adding the node to the network. It is generated by the owner's wallet (for example MetaMask), and its private key is held inside the wallet.
A "Liveness Monitoring System" will soon be added to the network. When it is run, offline nodes do not collect rewards anymore.
No. The node running rewards shown in the dashboard are just test tokens and have nothing to do with the node-drop incentive; that is, they carry no real value but help developers make sure the system is operating accordingly.
This means that your node is not reachable by the network. This might be because
- The node is down. You can use the
docker ps -a
command in your server to check ifmuon-node
,redis
andmongo
containers are up and running on your server. If they are down, you can start them by running thedocker-compose up -d
inside the folder where thedocker-compose.yml
is placed. - The node has been run on a local computer that does not have a public IP address. To solve the issue, you should backup the node and restore it on a vps.
- The firewall of the server that the node is running on blocked ports
8000
or4000
. You can use services like portchecker.co to check if these ports are open on your server. You can usually open these ports using:
sudo ufw allow 4000/tcp
sudo ufw allow 8000/tcp
Some service providers also enable users to configure the firewall from the dashboard they provide.
If none of the above seems to be your problem, you can join Muon Discord and be in touch with the tech team in the
#dev-help channel
.If the status of your node in the dashboard is OFF and when you run
docker logs -f --tail 50 muon-node
you see the following error,TSError: ⨯ Unable to compile TypeScript:
error TS2307: Cannot find module 'ipfs-core-types/src/utils' or its corresponding type declarations.
You need to run the following commands in
muon-node-js
folder line by line in order to back up your node,
docker cp muon-node:/usr/src/muon-node-js/.env ./backup.env
and rebuild it,
docker-compose down --rmi all
git pull
docker-compose pull
docker-compose up -d
and finally restore it.
docker cp backup.env muon-node:/usr/src/muon-node-js/backup.env
docker exec -it muon-node ./node_modules/.bin/ts-node ./src/cmd keys restore backup.env
docker restart muon-node
If you encounter an error when running any of these commands, you should resolve it before moving to the next one.
This shows your docker is old. To solve this, you need to follow the instruction in install docker engine to install the latest version based on your server's operating system.
NB: Make sure to backup your node before removing it if you are about to transfer it to a different server or install the latest version.
The following commands can be used to remove the Muon node's docker containers and images:
docker stop muon-node redis mongo
docker rm muon-node redis mongo
docker image prune
If you installed the node by cloning the
muon-node-js
repository, you can also remove the folder by: rm muon-node-js -rf
Last modified 26d ago