Multi Masternode Guide
How to run multiple masternodes on the same system
​
1
To build multiple masternodes on the same host using the same binaries that are in your path
2
​
3
Assuming a 1 Processor VPS at vultr running Ubuntu 16.04
4
​
5
On the VPS create a directory to house the copies of the data folders (lytix.conf, wallet.dat, etc) - assuming you have rights to drop directories in / - /lytix can be whatever you want it to be
6
​
7
mkdir -p /lytix/mndir
8
​
9
​
10
​
11
Create subdirectories for each of the masternode hosts you want to run. We're going to assume 5 in addition to the one you probably already have running
12
​
13
mkdir mndir/mn1
14
mkdir mndir/mn2
15
mkdir mndir/mn3
16
mkdir mndir/mn4
17
mkdir mndir/mn5
18
​
19
​
20
​
21
Create a new lytix.conf in each directory that will have a different rpcport. For this example we will use port 28081 for mn1, 28082 for mn2, 28083 for mn3, 28084 for mn4, and 28085 for mn5
22
---- lytix.conf in mndir/mn1 ----
23
​
24
rpcallowip=127.0.0.1
25
listen=0
26
server=1
27
daemon=1
28
rpcport=28081
29
​
30
---- lytix.conf in mndir/mn2 ----
31
​
32
rpcallowip=127.0.0.1
33
listen=0
34
server=1
35
daemon=1
36
rpcport=28082
37
​
38
---- lytix.conf in mndir/mn3 ----
39
​
40
rpcallowip=127.0.0.1
41
listen=0
42
server=1
43
daemon=1
44
rpcport=28083
45
​
46
---- lytix.conf in mndir/mn4 ----
47
​
48
rpcallowip=127.0.0.1
49
listen=0
50
server=1
51
daemon=1
52
rpcport=28084
53
​
54
---- lytix.conf in mndir/mn5 ----
55
​
56
rpcallowip=127.0.0.1
57
listen=0
58
server=1
59
daemon=1
60
rpcport=28085
61
​
62
I don't recommend starting them all at the same time, because they are all going to jump to about 30% system utilization downloading the chain and updating.
63
Just give each a little time to update. As of this writing the chain was at about 45,000 and it took a few minutes to fully retrieve the chain. Once the daemon has fully synched it will drop down
64
to around 4-8% system utilization.
65
​
66
Start each masternode by doing this:
67
​
68
lytixd -datadir=/lytix/mndir/mn1
69
lytixd -datadir=/lytix/mndir/mn2
70
lytixd -datadir=/lytix/mndir/mn3
71
lytixd -datadir=/lytix/mndir/mn4
72
lytixd -datadir=/lytix/mndir/mn5
73
​
74
On the gui client that you have the masternode.conf configured you will go through the same procedure in creating a regular masternode. Change the alias to something that you can remember:
75
​
76
masternode genkey
77
​
78
​
79
getaccountaddress mn101
80
​
81
​
82
​
83
send the 5000 LYTX to that address
84
​
85
Update the masternode.conf on the client with the same IP as the masternode, but with the alias above "mn101" and the other information like the output of genkey and the tx id that you see after enter the command:
86
​
87
masternode outputs
88
​
89
You will see multiple after it has confirmed, so look in the transactions and find the payment to self you just created to get the txid if you need it. You will now need to update the lytix.conf on the new masternodes with the following information: masternode=1 masternodeprivkey=private_key_from_output_of_masternode_genkey_above Restart the masternode to pick up the new config:
90
​
91
lytix-cli -datadir=/lytix/mndir/mn1 stop
92
lytixd -datadir=/lytix/mndir/mn1
93
​
94
Restart the gui client as well to pick up the new masternode.conf config. After 15 confirmations you can start the new masternode. Special thanks to our resident royalty LordSoylent for spelling this out for us :)
Copied!
Last modified 2yr ago
Copy link