[ANN][HLM] HELIUM - page 4. | Bitcointalksearch.org

akaltcoins

newbie

Activity: 18

Merit: 0

Quote from: PowerHemp on October 25, 2018, 06:10:37 PM

what you talking about? i skiped steps because i make it how i learned it from other tuts. my masternodes run without problems Wink

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.

bathrobehero

legendary

Activity: 2002

Merit: 1051

ICO? Not even once.

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?

sirazimuth

legendary

Activity: 3388

Merit: 3514

born once atheist

Quote from: Pon13 on October 26, 2018, 01:30:19 AM

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.

PowerHemp

legendary

Activity: 1386

Merit: 1001

Ganja <3

Quote from: akaltcoins on October 25, 2018, 08:18:35 PM

Quote from: PowerHemp on October 25, 2018, 06:10:37 PM

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 Wink

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.

Pon13

full member

Activity: 670

Merit: 130

Quote from: sirazimuth on October 25, 2018, 06:01:39 PM

Quote from: akaltcoins on October 24, 2018, 05:48:41 PM

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 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 Grin

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

akaltcoins

newbie

Activity: 18

Merit: 0

Actually these links are for updated installation guides that I just released this evening. Hopefully this sorts out a lot of your questions. I already posted it in the new ANN thread but I wanted to get it here in case some of you aren't watching the other one yet.

I am very pleased to release a new start-to-finish masternode installation guide for Vultr. This installation method allows you to install multiple Helium masternodes on the same VPS by using IPv6. The written guides are very helpful for a lot of people, but for others they find it easiest to watch someone else go through the steps so if you happen to be one of the latter, I believe you'll find this very helpful.

You can watch the video on Youtube at https://youtu.be/mj1FyN6Wauk

There is also a written guide which you can review on Medium that contains some more pictures and allows you to copy and paste some of the scripts and commands that are used in the video. https://medium.com/@AKcryptoGUY/securely-install-multiple-helium-masternodes-3ee2e995a5e0

akaltcoins

newbie

Activity: 18

Merit: 0

Quote from: PowerHemp on October 25, 2018, 06:10:37 PM

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

PowerHemp

legendary

Activity: 1386

Merit: 1001

Ganja <3

Quote from: sirazimuth on October 25, 2018, 06:01:39 PM

Quote from: akaltcoins on October 24, 2018, 05:48:41 PM

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

it should look like this:
MNname ip:port MNprivkey txhash output
MN1 00.000.000.000:9009 xxxxxxdrtiuldfkjdfildfliluilu8UIUIDHILcJFUghhgxx f2c5bbbc2f981bb164doifdljifjildluiO576e3JHKKJH455646529fee5f07855f 1

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

sirazimuth

legendary

Activity: 3388

Merit: 3514

born once atheist

Quote from: akaltcoins on October 24, 2018, 05:48:41 PM

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

teela

member

Activity: 116

Merit: 22

We've a new ANN topic here: https://bitcointalk.org/index.php?topic=5056752.new#new

This one will stay online a bit but expect it to be depreciated in the future.

Hulk1997

newbie

Activity: 56

Merit: 0

is bittrex going to credit our accounts if we hold spread on snap shot date?

akaltcoins

newbie

Activity: 18

Merit: 0

Quote from: sirazimuth on October 24, 2018, 04:32:17 PM

Fixed the binding error on the HLMMN wallet. Made all edits for ip and ports etc, listen =1 and it works fine.

After editing the masternode.conf file for the local controller wallet EXACTLY as shown in set-up instructions
The wallet will not launch....I get this pop up error message...

Error reading masternode configuration file: could not parse masternode.conf Line 1 "MN1"

The set-up guide says this is "The name (masternode_alias) you gave your masternode:"
Well I did not name my Masternode anything when I installed the wallet (probably why it won't parse it.)
and cannot for the life of me figure out how or where to set this "masternode_alias" field to "MN1" .

back to staking...derp

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.

sirazimuth

legendary

Activity: 3388

Merit: 3514

born once atheist

Fixed the binding error on the HLMMN wallet. Made all edits for ip and ports etc, listen =1 and it works fine.

After editing the masternode.conf file for the local controller wallet EXACTLY as shown in set-up instructions
The wallet will not launch....I get this pop up error message...

Error reading masternode configuration file: could not parse masternode.conf Line 1 "MN1"

The set-up guide says this is "The name (masternode_alias) you gave your masternode:"
Well I did not name my Masternode anything when I installed the wallet (probably why it won't parse it.)
and cannot for the life of me figure out how or where to set this "masternode_alias" field to "MN1" .

back to staking...derp

Pon13

full member

Activity: 670

Merit: 130

Quote from: sirazimuth on October 23, 2018, 04:31:58 PM

Quote from: Pon13 on October 23, 2018, 04:46:34 AM

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

So followed your configuring steps to the tea,and no go. Here's where I'm at....
I have 2 separate wallets with 2 separate directories.
The HLMMN1 wallet when launched from the startmn1.cmd gives error message...
"unable to bind to on this computer (bind requested address not valid in its content (10049)"...
which goes away if I set listen to 0 and relaunch. Then it shows a zero balance. Basically a virgin wallet.

When I launch controller wallet (loaded with the 1000 coins on one address) it says "cannot parse MN1" ("MN1" being the 1st line of the controler wallet masternode.conf file that I edited with private key, ip, etc.)
Where do I set alias masternode to MN1?
Also are both wallets launched when masternoding? or one or the other? which one? (I actually can't launch both on this pc anyway..error message.)
Still totally confused...but I will get this sussed if it kills me.
back to staking again... lol

MN1 wallet --> Listen=1

Controller Wallet --> Listen=0
and Staking=1 (to have staking enabled)
and check the ports they have to be different in these two wallets

craslovell

legendary

Activity: 1470

Merit: 1021

Cross posting here: https://bitcointalksearch.org/topic/m.47202245

Hello Heliumites!

As a result of the bounty campaign being pre-launch, I'll need to begin verifying your accounts in a somewhat unorthodox way. If you participated in any one of the bounty programs we ran through this campaign please PM me here on the forum from the original account you registered for the bounty campaign with.

I will be providing a spreadsheet to show that your information has been received as entries come in. Please do not include any additional information in your PM other than your Helium address.

I repeat;

To begin the process of claiming your Helium bounty rewards please PM me here on the forum one time only, with only your Helium address in the body of the message.

If you have yet to download your Helium wallet you can find your version here https://github.com/heliumchain/helium/releases

sirazimuth

legendary

Activity: 3388

Merit: 3514

born once atheist

Quote from: Pon13 on October 23, 2018, 04:46:34 AM

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

So followed your configuring steps to the tea,and no go. Here's where I'm at....
I have 2 separate wallets with 2 separate directories.
The HLMMN1 wallet when launched from the startmn1.cmd gives error message...
"unable to bind to on this computer (bind requested address not valid in its content (10049)"...
which goes away if I set listen to 0 and relaunch. Then it shows a zero balance. Basically a virgin wallet.

When I launch controller wallet (loaded with the 1000 coins on one address) it says "cannot parse MN1" ("MN1" being the 1st line of the controler wallet masternode.conf file that I edited with private key, ip, etc.)
Where do I set alias masternode to MN1?
Also are both wallets launched when masternoding? or one or the other? which one? (I actually can't launch both on this pc anyway..error message.)
Still totally confused...but I will get this sussed if it kills me.
back to staking again... lol

teela

member

Activity: 116

Merit: 22

Anyone continuing to struggle with setting up a node locally on a Windows machine. It is common to host Masternodes on an external VPS running Ubuntu. This is safer, easier and cheaper.

We've adapted the Nodemaster script for use with Helium. It takes care of 95% of the set up: https://github.com/trollboxteela/vps

sirazimuth

legendary

Activity: 3388

Merit: 3514

born once atheist

Changed the “listen” parameter back anyway , in case staking broke.
Will try flailing around again tonite. From your reply, I think I’m close and on right track. Thanx .
Tip will follow my 1st reward if / when it occurs.
Confusion around which masternode.conf file to edit as I got one in each
directory (control and mn) ...I edited the control wallet one and left the masternode wallet one as is.

Pon13

full member

Activity: 670

Merit: 130

Quote from: sirazimuth on October 22, 2018, 05:17:03 PM

Quote from: Pon13 on September 19, 2018, 07:38:17 AM

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

teela

member

Activity: 116

Merit: 22

Quote from: CoinBeastie on October 23, 2018, 03:11:54 AM

Hi,

congrats to the helium team. After wating for more than one year I just finished my installation and conf of my MN.

Followed the instructions of
https://www.heliumlabs.org/v1.0/docs/masternode-setup-guide

MN is synced and Local Wallet says MN is "enabled"
helium-cli masternode status returns "successfully started"

helium-cli getinfo returns "Staking Not Active"
Is that normal?
How long does it normally take to switch to "staking"?

If you are running a masternode your wallet will "lock" the 1000 coins collateral and it will not stake with them. Otherwise your masternode would stop working if you were to win a stake. By the looks of it your masternode is working. It can currently take up to 3 days before you get your first Masternode payment but after that they should arrive every 24 hours or so. Good luck!

Topic: [ANN][HLM] HELIUM - page 4. (Read 189467 times)