Quote from: drays on October 15, 2018, 06:46:29 PM

Quote from: RzeroD on October 15, 2018, 06:21:00 PM

Quote from: drays on October 15, 2018, 06:02:08 PM

Quote from: teela on October 15, 2018, 04:41:14 PM

Quote from: drays on October 15, 2018, 12:40:49 PM

Did anyone try a one wallet MN setup, instead of Hot-cold (local-remote) wallet setup as described in the tutorial?

I mean - try to run a masternode and control it using the one single hot wallet. That is a standard setup, which should be the simplest one... and it works on all other MN coins I have setup before.
Yesterday I spent hours trying to make it work - to no avail. It just throws stupid errors, like "Not capable masternode: cannot connect to x.x.x.x:9009", or just "Not capable masternode: " - without error description.
Gave up yesterday. Today moved the controlling part to the remote wallet - boom, it worked immediately.

So I suppose there is either a bug in HLM MN implementation (as the single hot wallet setup works for other MN coins); or an intended security limitation - it this case it should be documented, and the daemon should throw some meaningful error message - like "Not capable masternode: only local-remote setup is supported." or something better...

Just wanted to report this, in case if it's not widely known and discussed in slack/telegram/discord already

I think this guide does that for windows machines: https://www.heliumlabs.org/v1.0/docs/masternode-setup-guide-windows-local

Its a setup up for running multiple MNs on one local machine (afaict, never used this set up). I don't think there is anything that prevents you from running a hot node. Haven't been able to test it yet though.

That setup uses dedicated controller wallet (albeit local), so it is different. I was using Linux, and. most importantly, I was trying to use a single wallet (single datadir etc) both as MN itself, and as controller. That setup could be interesting for smaller holders only, but well... smaller holders are the most important user category for real decentralization, so having this setup working is important too, IMHO.

Do you have a static public IP?

Yes, sure, I was doing that on a Linux VPS on Vultr. The "Not capable masternode: cannot connect to x.x.x.x:9009" statement made me wonder the most, as I checked and was able to telnet to that port ("telnet x.x.x.x 9009" on my machine).

As said: nothing keeps you from running a hot node. And I haven't been able to check it. Soon as I can I'll tell you but then again: why run a hot node in the first place.