Seamlessly transition your node and assets to the mainnet
CAUTION : Updating your node to mainnet will make your chains and supernets created on Socotra inaccessible.
Depending on how you run your instance you should stop it, accordingly.
Access the window where you are running the binary ./juneogo and stop it with Ctrl+c.
As you run your Node as service you need to stop it with systemctl.
sudo systemctl stop juneogoYou can stop your docker with the following:
1) Go to juneogo-docker
2) Run docker-compose down
Carefully backup your Node if you participated to incentivised testnet! Otherwise you can loose your allocation. ( You only need to backup the Node ID )
It's recommended to save your staking files in a different location than juneogo or juneogo-docker directory.
Follow the guide Node Backup and Restore and if you have any issues or question reach us on the Official Discord.
DANGER : Be sure to backup your node BEFORE doing the next steps.
Go to the github juneogo-binaries repository and download the latest version of these files:
Connect to your server through a SFTP agent and copy paste the new files.
To grant execution permissions of the binary files, please execute the following commands:
Use only this command if you have followed our Install Script
Use the following command on your server :
Go to the Juneogo directory: juneogo-docker and run these commands:
If it doesn't work you can try to run git stash or to clone it again by following Set up steps.
By running your node as usual you will now bootsrap the Mainnet.
You can check that your node is bootsrapped through the regular curl request.
Last updated
- juneogo
- jevmchmod +x ~/YOUR-PATH/juneogo
chmod +x ~/YOUR-PATH/plugins/jevmbash <(wget -qO- https://raw.githubusercontent.com/Juneo-io/juneogo-binaries/main/update.sh)git checkout origin/main ./juneogo/juneogo
git checkout origin/main ./juneogo/.juneogo/plugins/jevm