[ANN][HLM] HELIUM

[drays]

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

[teela]

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.

[drays]

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.

[RzeroD]

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?

[MadaraAvenger]

More and more decentralized projects are coming into cryptos but it's good to see that the Helium made it with no obstacles and the work for the wallet is really amazing, you have good designers for sure.

[drays]

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).

[DuzyGej]

currency without exchange
When Cryptopia ?

[RzeroD]

currency without exchange
When Cryptopia ?

I didn't know that CREX24 was not considered an exchange: https://crex24.com/exchange/HLM-BTC

[teela]

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.

[drays]

How about you you write the fucking guide yourself instead of asking.

Not sure I get what you mean. And looks like you didn't understand what I was telling. I am asking neither for a guide, nor for a help. Neither a new guide for running a single hot wallet is needed (or possible) for me to write, as it doesn't seem to work currently (unless someone re-tests this and reports to be working somehow).
I just reported a possible issue with the MN implementation, which I found while trying to setup a hot MN wallet - just in case if this indeed a bug to be fixed, and just in case if it is interesting for developers and/or community. I do not insist on fixing this, neither am asking for your help or valuable advice, dear Mr. Mrrr (I am still a fan of your brilliant Haiku collection post, regardless of this particular outburst ).

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.

So better to tell - nothing but possible bugs
Regarding the reason for running a hot node... well, that is one of the possible ways to run it, and it is the most resource-friendly way if you run just one node (as you keep just one copy of blockchain + save CPU some power), so I assume there could be users willing to run that way. As to me, I am currently running the controller wallet separately on different PC, as this is the working way.

[sud]

@drays @teela

Also doesn't running a cold wallet on VPS require another PC with hot wallet? Some people are unanble to run masternode in cold/hot wallet setup. It would be great if anyone can check if this problem is problem is common.

[teela]

How about you you write the fucking guide yourself instead of asking.

Not sure I get what you mean. And looks like you didn't understand what I was telling. I am asking neither for a guide, nor for a help. Neither a new guide for running a single hot wallet is needed (or possible) for me to write, as it doesn't seem to work currently (unless someone re-tests this and reports to be working somehow).
I just reported a possible issue with the MN implementation, which I found while trying to setup a hot MN wallet - just in case if this indeed a bug to be fixed, and just in case if it is interesting for developers and/or community. I do not insist on fixing this, neither am asking for your help or valuable advice, dear Mr. Mrrr (I am still a fan of your brilliant Haiku collection post, regardless of this particular outburst ).

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.

So better to tell - nothing but possible bugs
Regarding the reason for running a hot node... well, that is one of the possible ways to run it, and it is the most resource-friendly way if you run just one node (as you keep just one copy of blockchain + save CPU some power), so I assume there could be users willing to run that way. As to me, I am currently running the controller wallet separately on different PC, as this is the working way.

I've my coins on Cryptopia Soon as I can I'll test it. As said afaik there is nothing that prevents this set up. But there is only one way to find out

[DuzyGej]

currency without exchange
When Cryptopia ?

I didn't know that CREX24 was not considered an exchange: https://crex24.com/exchange/HLM-BTC

I have 7834HLM stuck on Cryptopia.
When Cryptopia start?

[RzeroD]

currency without exchange
When Cryptopia ?

I didn't know that CREX24 was not considered an exchange: https://crex24.com/exchange/HLM-BTC

I have 7834HLM stuck on Cryptopia.
When Cryptopia start?

When Cryptopia can, we can't do more

[PowerHemp]

currency without exchange
When Cryptopia ?

I didn't know that CREX24 was not considered an exchange: https://crex24.com/exchange/HLM-BTC

I have 7834HLM stuck on Cryptopia.
When Cryptopia start?

When Cryptopia can, we can't do more

until cryptopia staked enough with our coins 

[RzeroD]

until cryptopia staked enough with our coins 

Check it out for yourself: https://heliumchain.info/#/address/SQTstaCXN3vNjSCjJbVA9Z7ecrsYcTjYKn

[faetos]

currency without exchange
When Cryptopia ?

tomorrow, trollface - https://twitter.com/cryptopia_nz/status/1052378849017716736?s=21

[Zero1One0]

FINALLY!!! I'm excited to fire up my HLM masternode. Hopefully no withdrawal issues with Cryptopia. 

KUDOS to the HELIUM team! 

[drays]

@drays @teela

Also doesn't running a cold wallet on VPS require another PC with hot wallet? Some people are unanble to run masternode in cold/hot wallet setup. It would be great if anyone can check if this problem is problem is common.

Well, yes, but I would say a bit differently - running a hot wallet on VPS requires another PC with cold wallet
And actually you don't necessarily need another PC, as you can run the second wallet on the same PC, just with different datadir, as described in Pon13 guide few pages back: https://bitcointalk.org/index.php?topic=1809278.msg45902537#msg45902537
The cold/hot wallet setup definitely works, so people who were unable to run it, probably did something wrong.

[Pon13]

@drays @teela

Also doesn't running a cold wallet on VPS require another PC with hot wallet? Some people are unanble to run masternode in cold/hot wallet setup. It would be great if anyone can check if this problem is problem is common.

Well, yes, but I would say a bit differently - running a hot wallet on VPS requires another PC with cold wallet
And actually you don't necessarily need another PC, as you can run the second wallet on the same PC, just with different datadir, as described in Pon13 guide few pages back: https://bitcointalk.org/index.php?topic=1809278.msg45902537#msg45902537
The cold/hot wallet setup definitely works, so people who were unable to run it, probably did something wrong.

Well, personally and so far, i have found only one coin where the hot/cold wallet setup in the same machine in windows didn't work while i had other MNs of different coins working like that on the same machine. and believe me i tried and triple checked everything (port forwarding, windows firewall, specific port for controller wallet and mn, etc.)

and for what you state drays on your above post i have seen it work only in one coin running in linux (one wallet for both controller and mn)...actually i realized it when i read your post.

So i guess every coin has its flaws