1 Choose the place where you will hold you masternodes directories (you need some freespace for every masternode)
2 Create folder HLMMN1 there
3 Copy file helium-qt.exe in folder HLMMN1
4 Create in folder HLMMN1 new folder data
5 Copy file blk0001.dat and folder txleveldb in created folder data (From your master wallet) (derp... I can't figure this out)
6 Rename helium-qt.exe to the Heliummn1.exe
Ok I did all this except step 5 (in red) where I got stumped.
Where is file "blk0001.dat? I found only "blk00000.dat" in the roaming/helium/blocks folder and copied that into my created "data" folder.
I could not find txleveldb anywhere to copy. Do you mean just create a folder named txleveldb?
Could you elaborate on what you mean by "(From your master wallet)" ? I'm probably missing something simple here.
I maybe could flail around with a different set of instructions but I like yours as they seem the most
straight forward. If/when I'm successful I will send tip . Thanx bud.
...........
(2 hours later after flailing around like the blind leading the blind)
ok I think I did everything ,moved coins, created keys etc, but musta forked something up.
I get error message. Told me to change listen parameter to "0". (so I did)
Then it wouldn't parse my public IP or something... (i googled that so it's right, i think...)
So there are 2 wallets, one masternode and one control?
and 2 separate helium folders? I'm all confused...
back to plain old staking for now...
The copy part is just to not wait your mn wallet to sync again.
You did right, meaning just copy the blockchain data (not wallet.dat, etc only blockchain data) to the data directory of your MN Wallet
If you do windows setup on the same machine then yes its two separate wallets meaning two different data directories, meaning one for each wallet. one controller wallet and one mn wallet. you can have the controller wallet closed once you've started your mn from there.
The listen parameter occur to which wallet? you have to check your configuration settings and of course your network settings (port forwarding enabled on correct ports, windows firewall allow incoming connections for specified port, etc.)