 Show Posts
|
|
Pages: « 1 2 [3] 4 5 6 »
|
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/ChGcPtJI 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: 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: 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. |
|
|
|
I haven't seen any "reserved for translation" or "Sir, where is the bounty, sir? " on new topic yet.
Will coins101 start writing his replies in every 6 six months or he will still use other topic? What will happen to heliumpay webpage and social media accounts?
probably one of the many 'self-moderated' posts that have been deleted. all the posts which question the project have been deleted, rather than addressed by one of those non-faces. they even have Idris Elba on the team, under a pseudonym  I'll try to remove spam only, and leave borderline troll posts such as yours, so if you have any questions please ask. |
|
|
|
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 |
|
|
|
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-guideMN 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! |
|
|
|
|
Cryptopia just opened withdrawals and by that marked another milestone. 373 days since our snapshot and now everyone finally has access to their Helium. We made it. And we made it despite everything.
A solid community will always be the backbone of any succesfull crypto project. And the Helium community is particularly strong. The amount of grit, persistance and dedication shown here over the last year is remarkable. If we keep that up there isn't a lot that can go wrong.
The Helium community hereby pats itself on the back.
Furthermore I'd like to thank the Cryptopia team for baring with us for all this time. And for the very professional way in which they handle everything. You guys are ace.
|
|
|
|
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 |
|
|
|
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-localIts 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. |
|
|
|
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-localIts 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. |
|
|
|
I have some spreadcoins and will watch this thread. I just don't quite get it - is Helium designed to be poolmining-resistant ?
The community decided to go with PoS and build on PIVX code rather than Dash as was originally planned, so there is no mining at all. You can read a bit more about why this direction was chosen in the Helium FAQ: https://www.heliumlabs.org/docs/frequently-asked-questions |
|
|
|
Hello
Can you help me with update MN
When I fallow instruction get this error on this step
xxxxxxxx@xxxxxxxxxx:~$ cp -r ~/helium-0.15.2/bin/. /usr/local/bin/
cp: cannot create regular file '/usr/local/bin/./helium-cli': Permission denied
cp: cannot create regular file '/usr/local/bin/./heliumd': Permission denied
cp: cannot create regular file '/usr/local/bin/./helium-qt': Permission denied
cp: cannot create regular file '/usr/local/bin/./helium-tx': Permission denied
cp: cannot create regular file '/usr/local/bin/./test_helium': Permission denied
cp: cannot create regular file '/usr/local/bin/./test_helium-qt': Permission denied
MN is on Ubuntu VPS
tnx
Its a mistake in the instructions. Thank you for posting, its been fixed. Try sudo cp -r ~/helium-0.15.2/bin/. /usr/local/bin/ |
|
|
|
Meanwhile, today Cryptopia completed swap and opened trading for yet another coin. But not for HLM.
And are we the first in the queue for exactly what reason? Are you going to demand absolute priority for your project from a private company among all the jobs they have? Come on. Do you think we can force other companies to do what we wan and when we want? What kind of business relationship do you want to establish if you start like this? Seriously, to be in crypto you need patience because not everything is as simple as it seems. Patience? Lol. More than year I patientlly wait when I can use my coins freezed on Cryptopia. And still waiting patiently, when those who had coins in their wallet skim the cream off. And I still waiting small rewards from bounty campaign. More than year. Patiently. Have to second Rzerod here, Cryptopia have been very helpful through out the process and have been very forthcoming in communications. We added the 28000k reduced reward blocks to take the edge off of things but with hindsight it is good to have gone to full rewards before trading went live. We encountered some issues after the reward increase and had to update the code to stabilize the network. If this had happened with trading already live it would not have been pretty and it would have impacted negatively on the value of the holdings of everyone. So yes the people who are currently staking and running masternodes earn rewards and the rest is waiting for Cryptopia. I have my coins on Cryptopia too but I don't see any skimming of the milk. On the contrary, the community was the MVP in sorting out last weeks issues and coming up with a solution, and by that prevented delays on the Cryptopia listing. In terms of ROI this will be a difference of a few percentage points (if even) in the long run. Everyone on the team and in the community did their very best to make things go as smooth as possible and consider all interests. This is the tx that went out to craslovell from the treasury with the coins for last years BTY campaign: https://heliumchain.info/#/tx/71458c8d208f7c5aca828b8adfee6f6e23cab0c85a81eec0a34250bf1e378f7dHe's on it but he'll need to reach everyone through PM in order to distribute. This is quite a lot of work and it will take some time. |
|
|
|
Almost every crypto wallet nets a false positive with virus scanners. As a rule of thumb: when you're on Windows 10 you don't need an additional virus scanner since Windows Defender kind of takes care of most. And if you have a decent ad blocker in your browser you're not going to pick up anything nasty in the first place anyways. Add uBlock origin and Disconnect to your browser and there are no bad links to click even if you wanted to. For really fishy stuff you can always first check the file with an aggregated antivirus engine such as virustotal.com, with the added benefit that you don't have to actually download and install the files first. https://www.virustotal.com/#/url/8757d74f3c99c82dcc71ed46c74eedfc6ed4f38621e69c4ee2255990f7aa2d68/detectionLooks like the 64bit Windows wallet is clean |
|
|
|
As a heads up: the chain is currently stuck at block 28000. We’re looking at the best way to get things moving again.
Just give it a karate chop and a good kick...that should sort it out.... ...or maybe try turning it off then turning back on again.... The roundhouse kick seems to have solved the issue. By the looks of it the first block with normal rewards proved very difficult to solve. It was solved eventually however so everything seems to be chugging along happily again. |
|
|
|
|
