• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

Remote MasterNode guide UPDATED

How is the masternodeaddr=IP+port linked to you local wallet?

What's stopping me from running the above command with someone else's MN IP address?

Who would get payed in that situation if two separate wallets use the same remote IP address?
 
I really don't know? Apparently, when you start your local wallet with the masternodeaddr=ip, you are assigning your remote wallet to do the work for your local wallet somehow. Your local wallet is the one you start as a masternode, the remote then handles the work, best way I can say/think it?! It seems once this is done, you don't have to put your local wallet back up to restart your remote node either as I just stopped my darkcoind, switched out to the new version, then started darkcoind with just that command "darkcoind" and my masternode is still up and running several hours later.

I don't think there is anything that would stop you from running that command on someone else's ip address. You would have to know they have a darkcoind instance running though. This may be one of the issues Evan is working on? I would assume that if you managed to do the command before the owner, you could get the payments. And I'm not sure, in fact, the owner may never know you did it! Unless they get an error when trying to start their local wallet up with masternodeaddr=ip and they get an error?

Good questions!

Note, I just looked at my debug.log again, and I noticed an error as the last listing of MN's were listed. Somebody had spent their inputs (probably testing ;) ) and it noticed, and the MN wasn't included in the "election" so that seems to work :)

2014-05-13 03:22:43 GetCurrentMasterNode: 44 : 107.170.229.52:9999 : 3944130609$
2014-05-13 03:22:43 GetCurrentMasterNode: 45 : 54.187.215.234:9999 : 1580887501$
2014-05-13 03:22:43 GetCurrentMasterNode: 46 : 54.72.209.87:9999 : 4078607545 >$
2014-05-13 03:22:43 !coins.IsAvailable COutPoint(394794eb950dadecbc0fb1a9e0b0b5$
2014-05-13 03:22:43 ERROR: CTxMemPool::acceptableInputs() : inputs already spent
2014-05-13 03:22:43 GetCurrentMasterNode: 47 : 191.238.54.222:9999 : 2895596655$
2014-05-13 03:22:43 GetCurrentMasterNode: 48 : 37.59.168.129:9999 : 963765372 >$
 
Last edited by a moderator:
I updated with a sample conf file for 10.8.2 but didn't add instructions that can be found on the update thread.
 
Propulsion said:
How is the masternodeaddr=IP+port linked to you local wallet?

What's stopping me from running the above command with someone else's MN IP address?

Who would get payed in that situation if two separate wallets use the same remote IP address?
Click to expand...
interesting question, but I think that with 10.8.2 it isn't possible to do that anymore because you would need the servers "masternodeprivkey" to start the MN from the local machine
 
Can anyone confirm whether the local wallet / remote master node option works with the latest version which requires the masternodeprivkey ?

Cheers!
 
I can't even start the latest wallet on my remote server. It says permission denied then if I use sudo, it says command not found. So I'm confused... will have to go over how I installed everything step by step I guess :eek:

This is what happens when you've burned yourself out with 2 days of trying to figure something out, LOL.
I forgot to chmod permissions!
 
Last edited by a moderator:
Ok, I now have updated the instructions. I hope it's clear as perfect glass, but if not, please ask questions!
 
Are you sure the cold storage is still possible? Because when I do that my Masternode is removed from the list after a while and I see a lot of masternodes with "0" this morning in masternode list... And my 2 cold storage masternodes disappeared from the list during the night even if the remote is still running.

HTML: 
$ darkcoind masternode list
{
    "54.187.147.18:9999" : 1,
    "184.73.179.187:9999" : 1,
    "91.121.219.246:9999" : 0,
    "54.187.152.9:9999" : 0,
    "54.186.36.157:9999" : 1,
    "54.187.112.94:9999" : 1,
    "54.187.221.4:9999" : 1,
    "54.186.167.254:9999" : 0,
    "54.187.229.145:9999" : 0,
    "54.187.223.100:9999" : 1,
    "54.187.209.106:9999" : 0,
    "192.99.184.43:9999" : 0,
    "192.99.184.45:9999" : 0,
    "192.99.184.46:9999" : 0,
    "192.99.184.47:9999" : 0,
    "192.99.184.49:9999" : 0,
    "192.99.184.51:9999" : 0,
    "192.99.184.52:9999" : 0,
    "192.99.184.53:9999" : 0,
    "192.99.184.54:9999" : 0,
    "192.99.184.55:9999" : 0,
    "192.99.184.56:9999" : 0,
    "192.99.184.57:9999" : 0,
    "192.99.184.58:9999" : 0,
    "192.99.184.59:9999" : 0,
    "54.178.177.122:9999" : 0,
    "192.99.184.60:9999" : 0,
    "192.99.184.61:9999" : 0,
    "192.99.184.62:9999" : 0,
    "107.170.229.52:9999" : 0,
    "188.226.253.176:9999" : 0,
    "128.199.207.141:9999" : 0,
    "162.243.251.154:9999" : 0,
    "54.72.209.87:9999" : 1,
    "192.99.184.42:9999" : 0,
    "192.99.184.44:9999" : 0,
    "192.99.184.48:9999" : 0,
    "192.99.184.50:9999" : 0,
    "192.99.184.63:9999" : 0,
    "54.187.123.156:9999" : 1,
    "54.187.61.169:9999" : 1,
    "188.226.189.50:9999" : 1,
    "107.170.79.105:9999" : 1
}
 
Cheers again for this guide and for updating it TanteStefana

But just to echo above, is this local / remote method working as expected? Also, does the local wallet have to be unix / darkcoind? or can we enter these commands via the windowsqt console? Cheers!
 
Up and running! Thanks for the guide!
Don't put the privkey in the remote darkcoin.conf though. Imho it isn't needed and also kinda defeats the purpose if the priv key is kept on the server.

Do I need to run one node per 1000DRK? Is it possible to run multiple nodes on the same machine using different ports? Haven't managed to do so, yet. But admittedly I haven't tried that hard :oops:
 
Is there any advantage to setting up two ec2 instances and running them like this? So that the 1000drk machines ip isn't displayed?

I thought there was and tried it but having problems

So I set up two ec2 instances
Both with their own private keys added to .conf files
1000drk on machine A
0 on machine B
Started darkcoind on machine A with "darkcoind masternodeaddr=public_ip_of_machineB"
Then "darkcoind masternode start passphrase"
Masternode running

I go to machine B and started darkcoind then
"darkcoind masternode start passphrase"
not capable masternode

What haven't I done here?
I know I've probably missed something due to be so tired :p
 
Last edited by a moderator:
How does this work if I want to run 10 masternodes?

Do I need 10 local machines for 10 remote machines?
 
vertoe said:
How does this work if I want to run 10 masternodes?

Do I need 10 local machines for 10 remote machines?
Click to expand...

I was thinking this, and might be trying if we have tesnet again, still hardening like paranoid...

say 2 MN to make it simple.

2x EC 2 Masternodes
1x central home computer of dedicated server, running 2 VM - configured to be seen by router as independent machines in the DHCP table

Some people reported activating nodes without remote privkey. Having remote/local with privkeys could be confusing the network ?

If confirmed, each VM could call out each masternode identifying itself. Both VM's will have the same external IP, but internal independant IP's, so packets sent through the router would be independently identified. My (probably pure nonsense) reasoning is, since cold storage is not working, VM's need to be online, so that when the EC2 nodes ping the network, there must be a "ping-back-to-local" to verify the 1k deposit is alive.

So in essence, the Masternode would propagate it's IP to the network, but each would call back the same IP, routed via DHCP to each VM running the hot wallets.

What do you think?

I'll attempt that, as soon as I get some answers on some doubts...

- Does the local / remote setup really need privkey on both ends? (will test)
- On the EC2, does daemon really NEED to go in /usr/bin/ - is it better or worse than to home folder?
- Damn it, so many conflicting info! when you wget the RC, is it chmod +x or 755 ?
 
Is there any tutorial about running everything that is needed for masternode but on one machine?
 
This is awesome, TanteStefana! It works within a home network, so I feel it's much safer. I've just tried on testnet using port 19999 and was able to setup this local/remote. Local is my Arch Linux laptop so wallet password was never entered on the remote and this all took place within the safety of being behind my ddwrt router.
Code: 
darkcoind -masternodeaddr=192.168.x.x.:19999
The wallet.dat stayed here on my Arch Linux laptop. Password was entered here. I use this laptop everyday, so I try to keep it light and secure and don't install any unnecessary software.
Thank you for the guide!

Update: It looks like with 10.9.3, and I use the inside IP address, it shows up as inside IP address on the masternode list, so I'll probably have to stop it and use the external IP address. Still a very awesome guide! Thank you!
 
Last edited by a moderator:
You must log in or register to reply here.
Back
Top