Dashmate on a new host#
Setup a new node#
Download and install the latest dashmate version. For more details, refer to the install instructions.
Sync a full node#
To minimize downtime, sync the Core blockchain without interrupting the existing node. The easiest way to do this is by syncing a full node and then converting it to an evonode.
Set up a dashmate full node to sync Core first:
dashmate setup
Select the network type and then
fullnode
for the node typeEnable the indexes required by Platform and then start dashmate to sync:
dashmate config set core.indexes '["tx"]' dashmate start
Make sure Core is syncing:
dashmate status core
Set up an evonode#
Once Core has finished syncing, reset the configuration and services. Use
--keep-data
so the synced data is retained:dashmate stop dashmate reset --keep-data --hard
Transfer the IP address to the new node. Alternatively, you can use the protx update_service_evo command to set a new IP address for your dashmate-based evonode.
Set up an evonode:
dashmate setup
Select the network type
Select
evolution masternode
when asked for node typeSelect
Yes
when asked if your masternode is already registeredSelect
No
when asked about importing existing data (the data is already present from the “Sync a full node” steps above)Import your existing masternode’s keys
Obtain an SSL certificate. See the SSL certificates section for details.
Shutdown existing masternode#
Shut down your existing server or dashd process
If you keep the existing server running, ensure you do not have any startup schedulers configured (systemd, cron, etc.)
Start dashmate node#
Start the node:
dashmate start
Make sure the node works properly by running the following status commands:
dashmate status dashmate status core dashmate status platform