Multiple Masternode setup on one VPS v2
Last updated
Was this helpful?
Last updated
Was this helpful?
This method will make use of the NEO's script located here:
Why NEO's script?
Adaptable easily to any coin or project
It can do IPv4 or IPv6
It makes use of bootstrap to speed up the synching of the MN wallet to the blockchain -> Instant synch
extremely customisable and development ongoing
This tutorial will show you step by step how to setup multiple FIX Masternodes on single VPS server by means of the NEO's script.
The concept behind NEO's script
Install the FIX masternode as you usually do. This node will be the Main or the reference node of all other nodes.
Install the NEO's script
Create the .dmn profile file specific to FIX
Add the profile based on the .dmn settings
Install as many duplicates (masternodes) as you want with the command "dupmn install fix <params_optional>
Install the Main FIX masternode
I will not spend much time on this part as this has been covered extensively in other docs. You can use this one as reference:
The only important thing is that you don't need to have the Main MN talk to your local QT wallet. i.e not entry needed in the masternode.conf file, no MN collateral needed, no Txid. You'ill just need to key in a Private key when requested. That's it. So the status of that Main MN will always be: status : Not capable masternode: Hot node, waiting for remote activation.
2. Create duplicates of the Main FIX Masternode
2.1 Download and install the NEO script
2.2 Create the fix.dmn file
In the root folder, type:
nano fix.dmn, paste the following in it and save the file with ctrl+x
2.3 add the profile for dupmn to use
type the command :
dupmn profadd fix.dmn fix
If your command is successful (if your fix.dmn is correct), you should get this output:
2.4 Create the Masternode instances/duplicates
Use the command dupmn install fix , it should give you the following output:
That output already suggests a number of things like "fix-cli-x masternode status", x being your masternode instance, to verify the status of the masternode. It generates itself a Private Key as well. You can use that one to add to your local wallet's masternode.conf file or enforce a privkey with the --privkey param.
You can also enable the utilization of a bootstrap to have a instantly synched new MN as follows, combined with the privkey enforced:
Once your local QT wallet has been properly setup (collateral sent to MN addresses, masternode.conf file populated, Aliases started, etc...)
You can check the status of your MNs with the command fix-cli-all masternode status
The "all" keyword means a summary of all MNs will be displayed, you can use your MN instance number there to look at a specific MN. As you can see the Main instance is the instance 0 or MN0:
For details on the other params of dupmn for a better customization, you can have a look at neo's github page (see link above) or simply run the dupmn help command and a list of available dupmn commands will appear.
That was it. Thanks for reading.
The first MN reward The average time it takes to receive the first reward is calculated in hours with the formula millions_locked_before_your_MN_is_enabled*2.6/60. At the time of writing the total number of millions that are locked in MNs is 2,500 million, so 2500*2.6/60=108.33 hours or approximately 4 days, 12 hours and 20 minutes.
If you should have questions, feel free to ask in the New-Capital discord server
There's also a video tutorial at my youtube channel for those interested:
