MaWo
|
|
May 19, 2015, 12:59:27 AM |
|
I've seen alot about running a hallmark node on linux however I'm going on two days now waiting for my Windows-based node to be seen on the network and I'm now wondering if that's supported. As posted to the Horizon forum I successfully followed the "how-to setup a node.." video on my Windows 7 Pro workstation with Symantec Endpoint firewall and a rule added to allow Port 7774-TCP inbound. https://horizonplatform.io/topic/running-horizon-hallmark-node/If Windows is supported is there any way beyond the Horizon Node Checker to know if my node is visible on the network? https://explorer.horizonplatform.io/?page=nodecheckAny advise would be greatly appreciated as I'm excited about being an active participant however am not versed in linux. Do you have a public ip? Do you use UPnP? Could you please send me your IP?
|
|
|
|
boomboom
|
|
May 19, 2015, 02:32:41 AM |
|
When Horizon team decides to gracefully shut down on the NXT asset exchange, please post notification and redemption process: * in this thread * on asx.nhzcrypto.org website * and, on https://nxtforum.org/assets-board/(ann)-nhz-asset/Simply stating 'it's been shut down' with no notice or warning is a terrible disservice to your users. Please come up with a better plan. The dacx was shut down by us and the asx just stopped working because the previous owner and developer, SilverNXT abandoned the project and vanished last October. We know there's about 2.5M HZ left on the account, but currently have no idea how many transactions have been missed. We will port it over to HZx as soon as that's done and see if we can catch up on what was missed in the meantime. Okay. Thank you! Has there been any progress on this? I sent my nhz-assets to the redemption address in early march but still haven't received my NHZ yet. thanks hey, are nhz-asset redemptions going to be honored or not? If yes, please do it soon. If not, why not? I bought nhz-asset in could faith, and I'm missing out on 10% interest for over 8 weeks now.
|
|
|
|
mavigro
Newbie
Offline
Activity: 44
Merit: 0
|
|
May 19, 2015, 06:40:50 AM |
|
I've seen alot about running a hallmark node on linux however I'm going on two days now waiting for my Windows-based node to be seen on the network and I'm now wondering if that's supported. As posted to the Horizon forum I successfully followed the "how-to setup a node.." video on my Windows 7 Pro workstation with Symantec Endpoint firewall and a rule added to allow Port 7774-TCP inbound. https://horizonplatform.io/topic/running-horizon-hallmark-node/If Windows is supported is there any way beyond the Horizon Node Checker to know if my node is visible on the network? https://explorer.horizonplatform.io/?page=nodecheckAny advise would be greatly appreciated as I'm excited about being an active participant however am not versed in linux. Do you have a public ip? Do you use UPnP? Could you please send me your IP? I hadn't considered UPnP as a requirement for this to work and I see "UPnP Discovery" and "SSDP" Blocked in the Symantec Firewall with an option to allow both from private IP addresses. I can PM you my public IP however would like to understand the scope of what workstation service(s) will need to be exposed in order for this to work and if deemed too risky I would consider another adoption to running a hallmark node. Perhaps this is why I'm not reading about Windows hallmark nodes?
|
|
|
|
MaWo
|
|
May 19, 2015, 09:01:47 AM |
|
I've seen alot about running a hallmark node on linux however I'm going on two days now waiting for my Windows-based node to be seen on the network and I'm now wondering if that's supported. As posted to the Horizon forum I successfully followed the "how-to setup a node.." video on my Windows 7 Pro workstation with Symantec Endpoint firewall and a rule added to allow Port 7774-TCP inbound. https://horizonplatform.io/topic/running-horizon-hallmark-node/If Windows is supported is there any way beyond the Horizon Node Checker to know if my node is visible on the network? https://explorer.horizonplatform.io/?page=nodecheckAny advise would be greatly appreciated as I'm excited about being an active participant however am not versed in linux. Do you have a public ip? Do you use UPnP? Could you please send me your IP? I hadn't considered UPnP as a requirement for this to work and I see "UPnP Discovery" and "SSDP" Blocked in the Symantec Firewall with an option to allow both from private IP addresses. I can PM you my public IP however would like to understand the scope of what workstation service(s) will need to be exposed in order for this to work and if deemed too risky I would consider another adoption to running a hallmark node. Perhaps this is why I'm not reading about Windows hallmark nodes? UPnP is not required. The requirements for a public hallmarked node are a public accessible IP, an open port 7774, a hz wallet with a configured hallmark and an activated peer server listen on port 7774.The peer server is already enabled with the default settings. If your PC is behind a router in a private network then you have to add a NAT rule for port 7774 manually or you enable UPnP.
|
|
|
|
BDCoinMiner
Member
Offline
Activity: 111
Merit: 10
The Future is Here; Grab it Fast Before Past
|
|
May 19, 2015, 05:50:51 PM |
|
I've seen alot about running a hallmark node on linux however I'm going on two days now waiting for my Windows-based node to be seen on the network and I'm now wondering if that's supported. As posted to the Horizon forum I successfully followed the "how-to setup a node.." video on my Windows 7 Pro workstation with Symantec Endpoint firewall and a rule added to allow Port 7774-TCP inbound. https://horizonplatform.io/topic/running-horizon-hallmark-node/If Windows is supported is there any way beyond the Horizon Node Checker to know if my node is visible on the network? https://explorer.horizonplatform.io/?page=nodecheckAny advise would be greatly appreciated as I'm excited about being an active participant however am not versed in linux. Do you have a public ip? Do you use UPnP? Could you please send me your IP? I hadn't considered UPnP as a requirement for this to work and I see "UPnP Discovery" and "SSDP" Blocked in the Symantec Firewall with an option to allow both from private IP addresses. I can PM you my public IP however would like to understand the scope of what workstation service(s) will need to be exposed in order for this to work and if deemed too risky I would consider another adoption to running a hallmark node. Perhaps this is why I'm not reading about Windows hallmark nodes? UPnP is not required. The requirements for a public hallmarked node are a public accessible IP, an open port 7774, a hz wallet with a configured hallmark and an activated peer server listen on port 7774.The peer server is already enabled with the default settings. If your PC is behind a router in a private network then you have to add a NAT rule for port 7774 manually or you enable UPnP. The main requirement of running any node is 'accessibility' from outside world. It doesn't count how this 'accessibility' configured like UPnP or Port forward or with dynamic DNS service or even it has attach with any 'Content delivery network service (CDN)). Running node is something like running your own 'webserver'. If you run any web server behind your private network and block any incoming request from world network, it is useless even your LAN/Office/Home/Internal network can access it. To qualify as node bounty payee, your node must have a fixed public IP address and port 7774 open to serve request from outside network. You don't need to give your public IP address to anyone you think risky; if you inside any NAT/Firewall findout what is your IP address from http://ifconfig.me/ip or https://www.whatismyip.com/ and try checking your 7774 TCP port open from http://www.adminkit.net/telnet.aspxAs soon you get 'Connection to <your ip address> on port 7774 was successful' from above telnet tool then you try next to see if it is get listed on official 'nodechecker' on https://explorer.horizonplatform.io/?page=nodecheck
|
|
|
|
Yaremi
Legendary
Offline
Activity: 1960
Merit: 1156
|
|
May 19, 2015, 06:40:01 PM Last edit: May 19, 2015, 07:03:12 PM by Yaremi |
|
How to setup HZ-node in linux or linux-VPS.Ubuntu/Debian.1. In your local PC go to http://localhost:7776/admin.html2. below "Generate Hallmark:" write: Public IP: "your IP" Secret Phrase: "you password from your hz account." After this press submit3. after step 2 you will see your Hallmark below. Save it. Now connect to your VPS if you use VPS or open terminal. ( all command from root) Installation tools.apt-get install unzip apt-get install openjdk-7-jre apt-get install nano apt-get install wget installation client.wget https://github.com/NeXTHorizon/hz-source/releases/download/hz-v3.9.1/hz-v3.9.1.zip unzip hz-v3.9.1.zip Configuration.cd hz nano conf/nhz-default.properties And write: nhz.myAddress=your ip nhz.myHallmark=your Hallmark (look step 3) Then save and exit. Open port.iptables -A INPUT -p tcp -d 0/0 -s 0/0 --dport 7774 -j ACCEPT Starting. Done.For tips: NHZ-WWMB-6BNJ-VNG7-3SQDJ 1aTiFrshYYPYmBAU7tMsZoDkz3ya9kBTc Thanks!
|
|
|
|
pharesim
|
|
May 19, 2015, 07:58:42 PM |
|
HZxchange has its own thread now https://bitcointalk.org/index.php?topic=1065680.0Sorry about the node check api. The sarcastic comment surprisingly was correct, I forgot about it over all the other stuff. Put it back on the to-do-list, thanks for bringing it up again.
|
|
|
|
GoldenEye
|
|
May 19, 2015, 08:07:44 PM |
|
Sorry about the node check api. The sarcastic comment surprisingly was correct, I forgot about it over all the other stuff. Put it back on the to-do-list, thanks for bringing it up again.
Fine, thank you
|
|
|
|
BDCoinMiner
Member
Offline
Activity: 111
Merit: 10
The Future is Here; Grab it Fast Before Past
|
|
May 19, 2015, 10:56:57 PM |
|
HZxchange has its own thread now https://bitcointalk.org/index.php?topic=1065680.0Sorry about the node check api. The sarcastic comment surprisingly was correct, I forgot about it over all the other stuff. Put it back on the to-do-list, thanks for bringing it up again. We really appreciate HZ devs development works and positive looks towards communities remarks. Keep the good work running:) Edit: Typo (s)
|
|
|
|
mavigro
Newbie
Offline
Activity: 44
Merit: 0
|
|
May 20, 2015, 01:23:57 AM |
|
I've seen alot about running a hallmark node on linux however I'm going on two days now waiting for my Windows-based node to be seen on the network and I'm now wondering if that's supported. As posted to the Horizon forum I successfully followed the "how-to setup a node.." video on my Windows 7 Pro workstation with Symantec Endpoint firewall and a rule added to allow Port 7774-TCP inbound. https://horizonplatform.io/topic/running-horizon-hallmark-node/If Windows is supported is there any way beyond the Horizon Node Checker to know if my node is visible on the network? https://explorer.horizonplatform.io/?page=nodecheckAny advise would be greatly appreciated as I'm excited about being an active participant however am not versed in linux. Do you have a public ip? Do you use UPnP? Could you please send me your IP? I hadn't considered UPnP as a requirement for this to work and I see "UPnP Discovery" and "SSDP" Blocked in the Symantec Firewall with an option to allow both from private IP addresses. I can PM you my public IP however would like to understand the scope of what workstation service(s) will need to be exposed in order for this to work and if deemed too risky I would consider another adoption to running a hallmark node. Perhaps this is why I'm not reading about Windows hallmark nodes? UPnP is not required. The requirements for a public hallmarked node are a public accessible IP, an open port 7774, a hz wallet with a configured hallmark and an activated peer server listen on port 7774.The peer server is already enabled with the default settings. If your PC is behind a router in a private network then you have to add a NAT rule for port 7774 manually or you enable UPnP. Thanks MaWo for the explanation. I see in my firewall log at 7:44AM EST the first allowed inbound on port 7774-TCP w/regular inbound thereafter and now see the node checker confirming my node approx 2 days after setting that up. So I can talk intelligently with my network admin about this could you provide a quick explanation about what the hallmark node actually does? Would that be a similar function as an active bitcoin node, presumeably to share in distribution of blockchain and whatever else a node does? Thanks again for helping me understand this.
|
|
|
|
BDCoinMiner
Member
Offline
Activity: 111
Merit: 10
The Future is Here; Grab it Fast Before Past
|
|
May 20, 2015, 01:32:34 AM |
|
Thanks MaWo for the explanation. I see in my firewall log at 7:44AM EST the first allowed inbound on port 7774-TCP w/regular inbound thereafter and now see the node checker confirming my node approx 2 days after setting that up.
So I can talk intelligently with my network admin about this could you provide a quick explanation about what the hallmark node actually does? Would that be a similar function as an active bitcoin node, presumeably to share in distribution of blockchain and whatever else a node does? Thanks again for helping me understand this.
Hallmarked node do the same things of an active bitcoin node. As bitcoin node share bitcoin's blockchain, HZ hallmark node share it's own blockchain. With very low traffic then any bitcoin node. Even for security reson your network admin wants to check source code of node, here you will find it: https://github.com/NeXTHorizon/hz-source
|
|
|
|
altsheets
Legendary
Offline
Activity: 902
Merit: 1001
Free trial of #AltFolio = save time, react faster
|
|
May 20, 2015, 03:27:46 PM Last edit: May 20, 2015, 04:06:03 PM by altsheets |
|
... and ... we are getting close to "dry" again ... --> BAMM: balance(NHZ-A9WQ-PC3J-B3SN-DHQSM) = 14191380.31418673 HZ = GOOD. Balance is high enough at the moment.Time now: 2015-05-06 03:32:29 ... checking again in 8.00 hours. BAMM: balance(NHZ-A9WQ-PC3J-B3SN-DHQSM) = 13356916.53585099 HZ = GOOD. Balance is high enough at the moment.Time now: 2015-05-06 11:32:29 ... checking again in 8.00 hours. ... BAMM: balance(NHZ-A9WQ-PC3J-B3SN-DHQSM) = 2250419.12560447 HZ = GOOD. Balance is high enough at the moment.Time now: 2015-05-18 19:32:37 ... checking again in 8.00 hours. BAMM: balance(NHZ-A9WQ-PC3J-B3SN-DHQSM) = 1651791.30438591 HZ = GOOD. Balance is high enough at the moment.Time now: 2015-05-19 03:32:37 ... checking again in 8.00 hours. BAMM: balance(NHZ-A9WQ-PC3J-B3SN-DHQSM) = 1248920.12559708 HZ = GOOD. Balance is high enough at the moment.Time now: 2015-05-19 11:32:37 ... checking again in 8.00 hours. BAMM: balance(NHZ-A9WQ-PC3J-B3SN-DHQSM) = 1248920.12559708 HZ = GOOD. Balance is high enough at the moment.Time now: 2015-05-19 19:32:37 ... checking again in 8.00 hours. BAMM: balance(NHZ-A9WQ-PC3J-B3SN-DHQSM) = 623877.32638512 HZ = is NOT enough. Alarming the guy ...successfully sent email.Time now: 2015-05-20 03:32:40 ... checking again in 8.00 hours. BAMM: balance(NHZ-A9WQ-PC3J-B3SN-DHQSM) = 210478.76614683 HZ = is NOT enough. Alarming the guy ...successfully sent email.Time now: 2015-05-20 11:32:42 ... checking again in 8.00 hours.
explanations --> I did it - again!I identified a problem - and solved it. And now I am coming back to you, to ask for a (crowdfunded) reward I have done this for you, hallmarked node owners. And for us all, a technical solution for an often recurring communication.... what about programming a little script that emails ... when the bounty address is empty again? ... anyone who wants to pledge some HZ for this cause? ... Then I'll program that for you, and the nodebountygiveraddress will never be empty again. *lol*
Done:programm output ("BAMM" = BalanceAlarmMailMailer.py ): BAMM: balance(NHZ-VJ23-6K9N-33Z2-4DHQV) = 43.0071 HZ = is NOT enough. Alarming the guy ... successfully sent email. Time now: 2015-05-01 02:31:49 ... checking again in 0.01 hours. BAMM: balance(NHZ-VJ23-6K9N-33Z2-4DHQV) = 43.0071 HZ = is NOT enough. Alarming the guy ... successfully sent email. Time now: 2015-05-01 02:32:22 ... checking again in 0.01 hours. BAMM: balance(NHZ-VJ23-6K9N-33Z2-4DHQV) = 43.0071 HZ = is NOT enough. Alarming the guy ... successfully sent email. Time now: 2015-05-01 02:32:54 ... checking again in 0.01 hours. BAMM: balance(NHZ-VJ23-6K9N-33Z2-4DHQV) = 43.0071 HZ = is NOT enough. Alarming the guy ... successfully sent email. Time now: 2015-05-01 02:33:26 ... checking again in 0.01 hours. BAMM: balance(NHZ-VJ23-6K9N-33Z2-4DHQV) = 43.0071 HZ = is NOT enough. Alarming the guy ... successfully sent email. Time now: 2015-05-01 02:33:58 ... checking again in 0.01 hours. BAMM: balance(NHZ-VJ23-6K9N-33Z2-4DHQV) = 43.0071 HZ = is NOT enough. Alarming the guy ... successfully sent email. Time now: 2015-05-01 02:34:30 ... checking again in 0.01 hours. Something failed, sorry. Ignoring it ... Time now: 2015-05-01 02:35:00 ... checking again in 0.01 hours. Something failed, sorry. Ignoring it ... Time now: 2015-05-01 02:35:30 ... checking again in 0.01 hours. BAMM: balance(NHZ-VJ23-6K9N-33Z2-4DHQV) = 43.0071 HZ = is NOT enough. Alarming the guy ... successfully sent email. Time now: 2015-05-01 02:36:02 ... checking again in 0.01 hours. BAMM: balance(NHZ-VJ23-6K9N-33Z2-4DHQV) = 43.0071 HZ = is NOT enough. Alarming the guy ... successfully sent email. Time now: 2015-05-01 02:36:34 ... checking again in 0.01 hours. BAMM: balance(NHZ-VJ23-6K9N-33Z2-4DHQV) = 43.0071 HZ = is NOT enough. Alarming the guy ... successfully sent email. Time now: 2015-05-01 02:37:06 ... checking again in 0.01 hours. BAMM: balance(NHZ-VJ23-6K9N-33Z2-4DHQV) = 43.0071 HZ = is NOT enough. Alarming the guy ... successfully sent email. Time now: 2015-05-01 02:37:39 ... checking again in 0.01 hours. BAMM: balance(NHZ-VJ23-6K9N-33Z2-4DHQV) = 43.0071 HZ = is NOT enough. Alarming the guy ... successfully sent email. Time now: 2015-05-01 02:38:11 ... checking again in 0.01 hours. BAMM: balance(NHZ-VJ23-6K9N-33Z2-4DHQV) = 51.0071 HZ = GOOD. Balance is high enough at the moment. Time now: 2015-05-01 02:38:41 ... checking again in 0.01 hours. BAMM: balance(NHZ-VJ23-6K9N-33Z2-4DHQV) = 51.0071 HZ = GOOD. Balance is high enough at the moment. Time now: 2015-05-01 02:39:11 ... checking again in 0.01 hours. BAMM: balance(NHZ-VJ23-6K9N-33Z2-4DHQV) = 51.0071 HZ = GOOD. Balance is high enough at the moment. Time now: 2015-05-01 02:39:41 ... checking again in 0.01 hours. BAMM: balance(NHZ-VJ23-6K9N-33Z2-4DHQV) = 51.0071 HZ = GOOD. Balance is high enough at the moment. Time now: 2015-05-01 02:40:11 ... checking again in 0.01 hours. BAMM: balance(NHZ-VJ23-6K9N-33Z2-4DHQV) = 51.0071 HZ = GOOD. Balance is high enough at the moment. Time now: 2015-05-01 02:40:41 ... checking again in 0.01 hours. BAMM: balance(NHZ-VJ23-6K9N-33Z2-4DHQV) = 51.0071 HZ = GOOD. Balance is high enough at the moment. Time now: 2015-05-01 02:41:11 ... checking again in 0.01 hours. BAMM: balance(NHZ-VJ23-6K9N-33Z2-4DHQV) = 51.0071 HZ = GOOD. Balance is high enough at the moment. Time now: 2015-05-01 02:41:41 ... checking again in 0.01 hours. BAMM: balance(NHZ-VJ23-6K9N-33Z2-4DHQV) = 51.0071 HZ = GOOD. Balance is high enough at the moment. Time now: 2015-05-01 02:42:11 ... checking again in 0.01 hours. Something failed, sorry. Ignoring it ... Time now: 2015-05-01 02:42:41 ... checking again in 0.01 hours. BAMM: balance(NHZ-VJ23-6K9N-33Z2-4DHQV) = 51.0071 HZ = GOOD. Balance is high enough at the moment. Time now: 2015-05-01 02:43:11 ... checking again in 0.01 hours. BAMM: balance(NHZ-VJ23-6K9N-33Z2-4DHQV) = 51.0071 HZ = GOOD. Balance is high enough at the moment. Time now: 2015-05-01 02:43:41 ... checking again in 0.01 hours. BAMM: balance(NHZ-VJ23-6K9N-33Z2-4DHQV) = 51.0071 HZ = GOOD. Balance is high enough at the moment. Time now: 2015-05-01 02:44:12 ... checking again in 0.01 hours. BAMM: balance(NHZ-VJ23-6K9N-33Z2-4DHQV) = 51.0071 HZ = GOOD. Balance is high enough at the moment. Time now: 2015-05-01 02:44:42 ... checking again in 0.01 hours. BAMM: balance(NHZ-VJ23-6K9N-33Z2-4DHQV) = 51.0071 HZ = GOOD. Balance is high enough at the moment. Time now: 2015-05-01 02:45:12 ... checking again in 0.01 hours. BAMM: balance(NHZ-VJ23-6K9N-33Z2-4DHQV) = 51.0071 HZ = GOOD. Balance is high enough at the moment. Time now: 2015-05-01 02:45:42 ... checking again in 0.01 hours. BAMM: balance(NHZ-VJ23-6K9N-33Z2-4DHQV) = 51.0071 HZ = GOOD. Balance is high enough at the moment. Time now: 2015-05-01 02:46:12 ... checking again in 0.01 hours. BAMM: balance(NHZ-VJ23-6K9N-33Z2-4DHQV) = 45.0071 HZ = is NOT enough. Alarming the guy ... successfully sent email. Time now: 2015-05-01 02:46:44 ... checking again in 0.01 hours. BAMM: balance(NHZ-VJ23-6K9N-33Z2-4DHQV) = 45.0071 HZ = is NOT enough. Alarming the guy ... successfully sent email. Time now: 2015-05-01 02:47:16 ... checking again in 0.01 hours. BAMM: balance(NHZ-VJ23-6K9N-33Z2-4DHQV) = 45.0071 HZ = is NOT enough. Alarming the guy ... successfully sent email. Time now: 2015-05-01 02:47:48 ... checking again in 0.01 hours. Explanations: In the beginning, the balance was 43 HZ which was decided to be too low, because I set the BAMM threshold to 50 HZ. Whenever that was detected, an email was sent (*). Then suddenly, the internet connection went bad - which did not kill my script, because I caught the exception. Then I have up'ped the balance to above 50 HZ with this transaction. So now, at balance 51 HZ, there was no problem anymore - no email was sent. All cool ... For a while, until: Eventually, I withdrew some 5 HZ in this transaction to fall below the threshold again. At the end, that is why it keeps on sending emails. Three. Until I stopped it, manually . (*) This is the email that was automatically sent 14 times in the above case, whenever the balance was too low: Date: Thu, 30 Apr 2015 17:31:47 -0700 (PDT) From: BAMM automailer <##hidden##@gmail.com> To: ##NodeRewardGiverEmail##@gmail.com Subject: The balance 43.0 HZ < 50.0 HZ threshold on address NHZ-VJ23-6K9N-33Z2-4DHQV
Attention, NodeRewardGiver:
The balance 43.0 HZ < 50.0 HZ threshold on address NHZ-VJ23-6K9N-33Z2-4DHQV
If you want me to change the threshold or frequency of this checking routine, answer to this email.
The script is running already, on my server:
I have configured the threshold to be 1,000,001 HZ. Any balance below that will trigger an email every 8 hours. The receiving email address is my own at the moment ... ... but I want to set it to a HZ team member address. PM me. The output right now is: BAMM: balance(NHZ-A9WQ-PC3J-B3SN-DHQSM) = 280620.11695920 HZ = is NOT enough. Alarming the guy ...successfully sent email. Time now: 2015-05-05 00:06:19 ... checking again later ... BAMM: balance(NHZ-A9WQ-PC3J-B3SN-DHQSM) = 120920.36487088 HZ = is NOT enough. Alarming the guy ...successfully sent email. Time now: 2015-05-05 01:09:24 ... checking again later ...
BAMM: balance(NHZ-A9WQ-PC3J-B3SN-DHQSM) = 273.82726704 HZ = is NOT enough. Alarming the guy ...successfully sent email.Time now: 2015-05-05 03:32:23 ... checking again in 8.00 hours. BAMM: balance(NHZ-A9WQ-PC3J-B3SN-DHQSM) = 273.82726704 HZ = is NOT enough. Alarming the guy ...successfully sent email.Time now: 2015-05-05 11:32:26 ... checking again in 8.00 hours. BAMM: balance(NHZ-A9WQ-PC3J-B3SN-DHQSM) = 273.82726704 HZ = is NOT enough. Alarming the guy ...successfully sent email.Time now: 2015-05-05 19:32:28 ... checking again in 8.00 hours. BAMM: balance(NHZ-A9WQ-PC3J-B3SN-DHQSM) = 14191380.31418673 HZ = GOOD. Balance is high enough at the moment.Time now: 2015-05-06 03:32:29 ... checking again in 8.00 hours. BAMM: balance(NHZ-A9WQ-PC3J-B3SN-DHQSM) = 13356916.53585099 HZ = GOOD. Balance is high enough at the moment.Time now: 2015-05-06 11:32:29 ... checking again in 8.00 hours.
(which caused me to post this now, even though I had not perfected my script yet, but because --- it is almost empty! EDIT: Now it is empty... EDIT2: Now it is refilled.) Good? How many times did the bounty address run dry in the past? How much communication, sadness, tragedy and despair was caused by that? ;-) I have solved that, in the interest of everyone. Please now everyone who is reading this (yes, you *lol*), please consider to send a small/large/mediocre amount of coins to my address --> NHZ-Q675-SGBG-LQ43-D38L6 or BTC 1Ek9McNmXwQgDnkzE9J6pjCPWEiihhL83n (or buy my asset 8101260088962758269 AAssetHZ, or try my AltFolio software)to say Thx!
|
|
|
|
pharesim
|
|
May 20, 2015, 03:31:04 PM |
|
very nice initiative! you can send the mail to <me>@nhzcrypto.org
|
|
|
|
altsheets
Legendary
Offline
Activity: 902
Merit: 1001
Free trial of #AltFolio = save time, react faster
|
|
May 20, 2015, 04:00:37 PM |
|
very nice initiative!
glad you like it. you can send the mail to <me>@nhzcrypto.org
done. Please PM with any problems / suggestions / improvements / changes. related: looks like a complicated thread here (-: good summary :-) the Horizon team have noticed that this thread is being overrun by people complaining of node issues and any new development announcements that we make are quickly lost in a sea of these complaints. ... As this thread was supposed to be for the announcement of new developments, I'm proposing that we start a new support thread ... and leave this thread clear for what it's supposed to do. ... My suggestion is to move them to a new support thread. ... What do people think? Yay or nay?
YAY. I already suggested the same thing a while ago: Wouldn't it make sense to create an extra thread for the thousands of node owners who are running HZ nodes? Their questions are always the same.
My node bounty giver address checker and automailer script above was intended to solve the most frequent recurring question: "dry". I like technical solutions for social problems *lol* But the other three questions that are repeatedly asked ... could really end up in a dedicated thread, either here in BCT or on the HZforum. That new thread would also have to be announced in prominent places, so people really do know about it. . In the OP here - and perhaps also announce it on the node checker page itself. Don't get me wrong: Those questions are important, and need their space, and I am totally against hiding them. But they are simply ... repetitive.
|
|
|
|
BDCoinMiner
Member
Offline
Activity: 111
Merit: 10
The Future is Here; Grab it Fast Before Past
|
|
May 20, 2015, 10:54:42 PM |
|
"Proposal for modification of HZ Official Faucet Options" Hello Devs, As currently HZ still under development and distributional stage, I am proposing increase some rewards on HZ Official faucet. Currently it pays out between 2 and 2 Horizon each time in every 48 hours which is oke if faucet target is to allow 'new user' to activate their 'brand new' account if user is experienced and used to with HZ wallet. I know there is potential hazard of spammers, automated collectors or even some clever dude sitting behind to game the system but still 48 hours for IP address seem too low. Country like my one, where having hundreds of user sharing same 'NAT' network face tremendous problem with it. Faucet was previously announced notice "The Horizon Platform team are committed to maintaining fairness of distribution, and having an official faucet allows us to ensure that coins continue to be distributed in as fair a manner as possible. We have allocated 250,000 Horizon per day to be sent out via the faucet, and will continue to support it until distribution is complete." Even there was allocation '250k HZ/day' and 'distributed in as fair a manner as possible' if people get few more HZ out of visiting faucet page, entering captcha worth it. Also using faucet help forger to get some extra as we can see lots of 0fee block in network. Don't get me wrong, I just thinking of distribute few more hundred HZ to new user to play around. If there is not that much problem, devs may consider it....2HZ/48Hours seem real low, really I mean it
|
|
|
|
BDCoinMiner
Member
Offline
Activity: 111
Merit: 10
The Future is Here; Grab it Fast Before Past
|
|
May 21, 2015, 05:02:59 AM |
|
very nice initiative!
glad you like it. you can send the mail to <me>@nhzcrypto.org
done. Please PM with any problems / suggestions / improvements / changes. related: looks like a complicated thread here (-: good summary :-) the Horizon team have noticed that this thread is being overrun by people complaining of node issues and any new development announcements that we make are quickly lost in a sea of these complaints. ... As this thread was supposed to be for the announcement of new developments, I'm proposing that we start a new support thread ... and leave this thread clear for what it's supposed to do. ... My suggestion is to move them to a new support thread. ... What do people think? Yay or nay?
YAY. I already suggested the same thing a while ago: Wouldn't it make sense to create an extra thread for the thousands of node owners who are running HZ nodes? Their questions are always the same.
My node bounty giver address checker and automailer script above was intended to solve the most frequent recurring question: "dry". I like technical solutions for social problems *lol* But the other three questions that are repeatedly asked ... could really end up in a dedicated thread, either here in BCT or on the HZforum. That new thread would also have to be announced in prominent places, so people really do know about it. . In the OP here - and perhaps also announce it on the node checker page itself. Don't get me wrong: Those questions are important, and need their space, and I am totally against hiding them. But they are simply ... repetitive. Out of all your effort (and all our discussion & hope) node bounty account is dry again! If node owner flood with complain posting dry-dry-dry; who to blame
|
|
|
|
GoldenEye
|
|
May 21, 2015, 05:19:24 AM |
|
Node bounty account dry again, as predicted yesterday
|
|
|
|
sirnoah
Newbie
Offline
Activity: 55
Merit: 0
|
|
May 21, 2015, 05:38:28 AM |
|
Hey fellas.....stopped at step one in setting up the node. Link to wallet is no good, where can I download the wallet?
Thanks!
yes please wheres the wallet?
|
|
|
|
sirnoah
Newbie
Offline
Activity: 55
Merit: 0
|
|
May 21, 2015, 05:39:24 AM |
|
is the faucet done? where is the link plz "Proposal for modification of HZ Official Faucet Options" Hello Devs, As currently HZ still under development and distributional stage, I am proposing increase some rewards on HZ Official faucet. Currently it pays out between 2 and 2 Horizon each time in every 48 hours which is oke if faucet target is to allow 'new user' to activate their 'brand new' account if user is experienced and used to with HZ wallet. I know there is potential hazard of spammers, automated collectors or even some clever dude sitting behind to game the system but still 48 hours for IP address seem too low. Country like my one, where having hundreds of user sharing same 'NAT' network face tremendous problem with it. Faucet was previously announced notice "The Horizon Platform team are committed to maintaining fairness of distribution, and having an official faucet allows us to ensure that coins continue to be distributed in as fair a manner as possible. We have allocated 250,000 Horizon per day to be sent out via the faucet, and will continue to support it until distribution is complete." Even there was allocation '250k HZ/day' and 'distributed in as fair a manner as possible' if people get few more HZ out of visiting faucet page, entering captcha worth it. Also using faucet help forger to get some extra as we can see lots of 0fee block in network. Don't get me wrong, I just thinking of distribute few more hundred HZ to new user to play around. If there is not that much problem, devs may consider it....2HZ/48Hours seem real low, really I mean it
|
|
|
|
BDCoinMiner
Member
Offline
Activity: 111
Merit: 10
The Future is Here; Grab it Fast Before Past
|
|
May 21, 2015, 06:08:57 AM |
|
is the faucet done? where is the link plz
you will find current Horizon faucet at : https://faucet.horizonplatform.io/Thanks for asking.
|
|
|
|
|