[ANN][HLM] HELIUM

[Pon13]

When you create your masternode, you enter a command "getaccountaddress MN1" (or you replace MN1 with anything you want, call yours DERP1 if you want to).  That getaccountaddress command gives you the address you send your collateral to, but it also tells your wallet the name of your masternode.  That is how you name your masternode.  Then the masternode.conf file references that same name.  Your masternode.conf file will then have a line that says "MN1 129.125.72.152:9009 YOURPRIVATEKEY MASTERNODEOUTPUT TXID" only those last three variables are replaced by whatever your values are.  That's it.  You might be making it harder than it actually needs to be.

Moved 1000 helium to 1 address
I've done all config file edits on both controller wallet and masternode wallet.
Ran that command <getaccountaddress MN1> in both wallets.
still get... "Error reading masternode configuration file: could not parse masternode.conf Line 1  "MN1"  "
(or whatever I call it. It won't parse 1st line. I have to un-edit file back to launch wallet)

So I guess I'm missing something fundamental here.
derp derp derp...  I give up.  
I will tip any masternode geniuses who can figure out wtf I'm doing wrong.

yesterday i helped someone on slack to setup his MN. By the end of the process everything was running smoothly. i hope it was you and you got your mn running  
https://imgur.com/a/ChGcPtJ

I wrote the guide (https://www.heliumlabs.org/v1.0/docs/masternode-setup-guide-windows-local) on the fly while trying to help someone in here without running a mn that time cause i had my coins in cryptopia.

If you run the controller/mn, 2 different wallets but same machine setup you have to add to the configs  (helium.conf) the rpcport command and specify different rpcports for two wallets (controller/mn) else you get an error that the rpc could not be binded.

For example on Controller Wallet:

Code:

rpcuser=long random username
rpcpassword=longer random password
rpcallowip=127.0.0.1
rpcport=xxxx (a port number different from MN port and MN rpcport) --> for example rpcport=2222
listen=0 --> this line is not mandatory
server=1 --> this line is not mandatory
daemon=1 --> this line is not mandatory
logtimestamps=1 --> this line is not mandatory
maxconnections=256 --> this line is not mandatory

While on MN Wallet:

Code:

rpcuser=long random username
rpcpassword=long random password
rpcallowip=127.0.0.1
rpcport=2223
listen=1
server=1
daemon=1
logtimestamps=1
maxconnections=256
masternode=1
externalip=Your_PUBLIC_IP
masternodeaddr=Your_PUBLIC_IP:9009
masternodeprivkey=YOUR_MN_PRIV_KEY

[1713882529]

1713882529

[1713882529]

1713882529

[1713882529]

1713882529

[1713882529]

1713882529

[1713882529]

1713882529

[PowerHemp]

i made with accept payment a address and sent there the 1000 helium i never used the getacccountaddress in the debugconsole..

Yeah that's probably the problem.  You can't just skip steps.  You need to use getaccountaddress in the debug console.

I show you how to do it all right here: https://youtu.be/XOgi2Fkrn08

what you talking about? i skiped steps because i make it how i learned it from other tuts. my masternodes run without problems and no you dont need the command getaccountaddress.. if you make just a address with name MN1 in accepting payment and sent there 1000 helium its enough. getaccountaddress is like doing this.

[sirazimuth]

If you run the controller/mn, 2 different wallets but same machine setup you have to add to the configs  (helium.conf) the rpcport command and specify different rpcports for two wallets (controller/mn) else you get an error that the rpc could not be binded.

For example on Controller Wallet:

Code:

rpcuser=long random username
rpcpassword=longer random password
rpcallowip=127.0.0.1
rpcport=xxxx (a port number different from MN port and MN rpcport) --> for example rpcport=2222
listen=0 --> this line is not mandatory
server=1 --> this line is not mandatory
daemon=1 --> this line is not mandatory
logtimestamps=1 --> this line is not mandatory
maxconnections=256 --> this line is not mandatory

While on MN Wallet:

Code:

rpcuser=long random username
rpcpassword=long random password
rpcallowip=127.0.0.1
rpcport=2223
listen=1
server=1
daemon=1
logtimestamps=1
maxconnections=256
masternode=1
externalip=Your_PUBLIC_IP
bind=Your_INTERNAL_IP
masternodeaddr=Your_PUBLIC_IP:9009
masternodeprivkey=YOUR_MN_PRIV_KEY

No,wasn’t me on slack unfortunately.
This possible solution looks promising though not holding breath.I actually did have a binding error
(See earlier reply) that I fixed.
Anyway will try this when home tonite. Thanx for all your replies mate.
I’ll let you know result.

(later...)

RESULT...
exactly what I expected, lol...ie... can now open both wallets with added rpcport setting edits. (at least I made progress)
BUT same thing...error cannot parse  'MN1"  when trying to launch controller wallet (with edited masternode.conf file.)
more derps...

 Do the 1000 coins reside in the controller wallet or masternode wallet..or does it matter? I know... I'm just like shooting in the dark here.
 If (and at this point.... a mighty big "if") I ever get this sussed, I'll throw a huge block party with free beer, fireworks
and of course Helium balloons to make our voices  squeaky while watching the fireworks show.

[bathrobehero]

Hey, heliumchain.info's staking reward estimates seem to be way off. Like in reality I get half to 1/3rd as much rewards as it suggests.
A user (unobt) told me he's using 50*staking_amount/difficulty for estimating HLM rewards per day which seems spot on to me. I think that should be the correct equation on heliumchain.info.

I don't have masternodes so I'm wondering, does the sites masternode reward estimates correct?

[akaltcoins]

what you talking about? i skiped steps because i make it how i learned it from other tuts. my masternodes run without problems and no you dont need the command getaccountaddress.. if you make just a address with name MN1 in accepting payment and sent there 1000 helium its enough. getaccountaddress is like doing this.

In that case it might seem weird but be worth trying.  I did encounter a can not parse error the first time I set up my masternode.conf file on a Mac because the default text editor had introduced some weird formatting which caused it to not read the file correctly.  I had to clean up the text with a text cleaner and then paste it back into the file to clear the error.  I used http://www.textcleanr.com/ this site to do it and it solved my problem.  It might be worth a try.

[Bjorn_Blockchain]

https://coinhub.news has just published an article regarding Helium and our plans for the future:

https://coinhub.news/cs/article/helium-decentralized-currency-and-service-platform-for-enterprise-business

On behalf of the Helium community I'd like to thank the Kreds project for making this possible. They've been following Helium closely and were kind enough to give us this exposure.

Excellent article looking good Helium!

[Amph]

shitty value, if i had sold spreadcoin at the peak would have been a better choice..

seems there is a good staking here what the %?

[kraterion]

shitty value, if i had sold spreadcoin at the peak would have been a better choice..

seems there is a good staking here what the %?

You're still holding spread coins ? I know that a lot of people just bought at the top and probably now they have an useless bag (because that's a useless coin, so to speak)

[RzeroD]

Hey, heliumchain.info's staking reward estimates seem to be way off. Like in reality I get half to 1/3rd as much rewards as it suggests.
A user (unobt) told me he's using 50*staking_amount/difficulty for estimating HLM rewards per day which seems spot on to me. I think that should be the correct equation on heliumchain.info.

I don't have masternodes so I'm wondering, does the sites masternode reward estimates correct?

Yes, I have already changed the way to calculate the reward for PoS at heliumchain.info, so the estimates should be quite correct right now.
If anyone has any more suggestions for the page, tell me.

[teela]

When you create your masternode, you enter a command "getaccountaddress MN1" (or you replace MN1 with anything you want, call yours DERP1 if you want to).  That getaccountaddress command gives you the address you send your collateral to, but it also tells your wallet the name of your masternode.  That is how you name your masternode.  Then the masternode.conf file references that same name.  Your masternode.conf file will then have a line that says "MN1 129.125.72.152:9009 YOURPRIVATEKEY MASTERNODEOUTPUT TXID" only those last three variables are replaced by whatever your values are.  That's it.  You might be making it harder than it actually needs to be.

Moved 1000 helium to 1 address
I've done all config file edits on both controller wallet and masternode wallet.
Ran that command <getaccountaddress MN1> in both wallets.
still get... "Error reading masternode configuration file: could not parse masternode.conf Line 1  "MN1"  "
(or whatever I call it. It won't parse 1st line. I have to un-edit file back to launch wallet)

So I guess I'm missing something fundamental here.
derp derp derp...  I give up.  
I will tip any masternode geniuses who can figure out wtf I'm doing wrong.

yesterday i helped someone on slack to setup his MN. By the end of the process everything was running smoothly. i hope it was you and you got your mn running  
https://imgur.com/a/ChGcPtJ

I wrote the guide (https://www.heliumlabs.org/v1.0/docs/masternode-setup-guide-windows-local) on the fly while trying to help someone in here without running a mn that time cause i had my coins in cryptopia.

If you run the controller/mn, 2 different wallets but same machine setup you have to add to the configs  (helium.conf) the rpcport command and specify different rpcports for two wallets (controller/mn) else you get an error that the rpc could not be binded.

For example on Controller Wallet:

Code:

rpcuser=long random username
rpcpassword=longer random password
rpcallowip=127.0.0.1
rpcport=xxxx (a port number different from MN port and MN rpcport) --> for example rpcport=2222
listen=0 --> this line is not mandatory
server=1 --> this line is not mandatory
daemon=1 --> this line is not mandatory
logtimestamps=1 --> this line is not mandatory
maxconnections=256 --> this line is not mandatory

While on MN Wallet:

Code:

rpcuser=long random username
rpcpassword=long random password
rpcallowip=127.0.0.1
rpcport=2223
listen=1
server=1
daemon=1
logtimestamps=1
maxconnections=256
masternode=1
externalip=Your_PUBLIC_IP
bind=Your_INTERNAL_IP
masternodeaddr=Your_PUBLIC_IP:9009
masternodeprivkey=YOUR_MN_PRIV_KEY

If you'd edit all of this into the OP where you posted the initial guide this would be very helpful. We had quite a lot of users asking for support with this set up and I could update the guide I copy pasted.

[Pon13]

aaaaaaaaaaaaaaaaaaaaaaaaaaand its done 

[Amph]

shitty value, if i had sold spreadcoin at the peak would have been a better choice..

seems there is a good staking here what the %?

You're still holding spread coins ? I know that a lot of people just bought at the top and probably now they have an useless bag (because that's a useless coin, so to speak)

no you did not read correctly, i sold them long time ago, but it was a mistake seen the value of helium...

[sirazimuth]

Hey, heliumchain.info's staking reward estimates seem to be way off. Like in reality I get half to 1/3rd as much rewards as it suggests.
A user (unobt) told me he's using 50*staking_amount/difficulty for estimating HLM rewards per day which seems spot on to me. I think that should be the correct equation on heliumchain.info.

I don't have masternodes so I'm wondering, does the sites masternode reward estimates correct?

Yes, I have already changed the way to calculate the reward for PoS at heliumchain.info, so the estimates should be quite correct right now.
If anyone has any more suggestions for the page, tell me.

Well if I'm reading this right and it is indeed accurate, staking 1000 HLM is currently more profitable than masternoding.
Fine by me.

(DING... speak of the devil... 2.5 HLM incoming)

[teela]

aaaaaaaaaaaaaaaaaaaaaaaaaaand its done 

appreciated!

Now if you all please continue conversation in the new ANN topic

https://bitcointalk.org/index.php?topic=5056752

[margana]

Where are these support channels found that are referenced in the masternode setup guide?

"Helium community on Discord: TBA (#help for technical support)"?  "#masternodes and we will help you fix it."  Where does one find the "Helium community on Discord"?  Is #masternodes also on discord?

These instructions are not working for me: https://www.heliumlabs.org/v1.0/docs/masternode-setup-guide

The 'masternode outputs' command yields only this:

"11:23:01 [
]"

[Pon13]

aaaaaaaaaaaaaaaaaaaaaaaaaaand its done 

appreciated!

Now if you all please continue conversation in the new ANN topic

https://bitcointalk.org/index.php?topic=5056752

fixed everything in one post and posted it to the new ANN topic.
Update the guide in the website if you want as well.

[sirazimuth]

The 'masternode outputs' command yields only this:

"11:23:01 [
]"

FWIW...during my failed endeavors to set up a Masternode , I had exact same thing happen to me.
So started again and I made another transaction of 1000 HLM  to a new address,
then after 1 confirm I tried the "masternode outputs" command again and voila, it worked and spat out a tx id ...go figure...
(too bad that wasn't my only issue....)

[Amph]

what is the % return per year with the pos?

[teela]

aaaaaaaaaaaaaaaaaaaaaaaaaaand its done 

appreciated!

Now if you all please continue conversation in the new ANN topic

https://bitcointalk.org/index.php?topic=5056752

fixed everything in one post and posted it to the new ANN topic.
Update the guide in the website if you want as well.

Will do!

[sud]

@cradox

Nice site, they plan to implement a lot of features for sure. But I like masternodes.online service more, it's simple and has almost all MN coins out there. Helium was also added there recently, so to can check what will be your daily rewards.

https://masternodes.online/currencies/HLM/