Topic: . - page 81. (Read 491736 times)
I'm Trying to complete a Forging Pool list of main website, If they made one.
Any help would be greatly appreciated.
1. Horizon Forging Pool http://nhzforgingpool.redirectme.net NHZ-3R7E-HK6Z-9AM8-BUP9L
2. BlockNET ? NHZ-PC95-K8VS-MEX5-7Z5K7
3. CryptoCCForgePool ? NHZ-SZMU-VE38-JJAW-GN8CT
4. Maulesel ? NHZ-MAUL-ESEL-RRAW-EDVS3
5. Scarepool ? NHZ-JNLH-JVAY-55EZ-EHFZ6
6. NHznode ? NHZ-U37X-FVKU-4ARG-FR29F
Remember, nodes need to to be updated to V 3.9.1 by tomorrow to continue receiving your node bounty payment. 
Since May 3 only payments for current software versions?
I would expect a significantly higher payout...
About half of my peers use an old version.
But unfortunately I can see it is not that much higher in number. Bounty giver wallet showing despatching only 696HZ today!
Seem bounty expected admins of node did the update job currently! All red color backdated nodes are all those with dinamic ip non hallmarked node:)
Couldn't happy that much
And again bounty node running dry!!!!
Polo has been slow on the trigger to send over the next batch of bounty funds.
Bounty funds keeping in Poloniex??? WTF??
Poloniex is escrowing HZ funds. It used to say so right in the thread title
EDIT: Ye what ^^ BDCoin said
Remember, nodes need to to be updated to V 3.9.1 by tomorrow to continue receiving your node bounty payment.
Since May 3 only payments for current software versions?
I would expect a significantly higher payout...
About half of my peers use an old version.
But unfortunately I can see it is not that much higher in number. Bounty giver wallet showing despatching only 696HZ today!
Seem bounty expected admins of node did the update job currently! All red color backdated nodes are all those with dinamic ip non hallmarked node:)
Couldn't happy that much
And again bounty node running dry!!!!
Polo has been slow on the trigger to send over the next batch of bounty funds.
Bounty funds keeping in Poloniex??? WTF??
Yes! POLO is official partner of HZ distribution. They keep the undistributed balance and act as trusted 3rd party. Read distribution method of HZ at their website.
Remember, nodes need to to be updated to V 3.9.1 by tomorrow to continue receiving your node bounty payment.
Since May 3 only payments for current software versions?
I would expect a significantly higher payout...
About half of my peers use an old version.
But unfortunately I can see it is not that much higher in number. Bounty giver wallet showing despatching only 696HZ today!
Seem bounty expected admins of node did the update job currently! All red color backdated nodes are all those with dinamic ip non hallmarked node:)
Couldn't happy that much
And again bounty node running dry!!!!
Polo has been slow on the trigger to send over the next batch of bounty funds.
Bounty funds keeping in Poloniex??? WTF??
Remember, nodes need to to be updated to V 3.9.1 by tomorrow to continue receiving your node bounty payment.
Since May 3 only payments for current software versions?
I would expect a significantly higher payout...
About half of my peers use an old version.
But unfortunately I can see it is not that much higher in number. Bounty giver wallet showing despatching only 696HZ today!
Seem bounty expected admins of node did the update job currently! All red color backdated nodes are all those with dinamic ip non hallmarked node:)
Couldn't happy that much
And again bounty node running dry!!!!
Polo has been slow on the trigger to send over the next batch of bounty funds.
Remember, nodes need to to be updated to V 3.9.1 by tomorrow to continue receiving your node bounty payment.
Since May 3 only payments for current software versions?
I would expect a significantly higher payout...
About half of my peers use an old version.
But unfortunately I can see it is not that much higher in number. Bounty giver wallet showing despatching only 696HZ today!
Seem bounty expected admins of node did the update job currently! All red color backdated nodes are all those with dinamic ip non hallmarked node:)
Couldn't happy that much
Two examples from my peers list:
130.211.147.62: NRS NHZ V3.9; Last Payout: 2015-05-05 00:54:21 (today)
155.254.36.212: NRS NHZ V3.9; Last Payout: 2015-05-04 04:41:06 (yesterday, because bounty account is dry again)
Remember, nodes need to to be updated to V 3.9.1 by tomorrow to continue receiving your node bounty payment.
Since May 3 only payments for current software versions?
I would expect a significantly higher payout...
About half of my peers use an old version.
But unfortunately I can see it is not that much higher in number. Bounty giver wallet showing despatching only 696HZ today!
Seem bounty expected admins of node did the update job currently! All red color backdated nodes are all those with dinamic ip non hallmarked node:)
Couldn't happy that much
And again bounty node running dry!!!!
Remember, nodes need to to be updated to V 3.9.1 by tomorrow to continue receiving your node bounty payment.
Since May 3 only payments for current software versions?
I would expect a significantly higher payout...
About half of my peers use an old version.
But unfortunately I can see it is not that much higher in number. Bounty giver wallet showing despatching only 696HZ today!
Seem bounty expected admins of node did the update job currently! All red color backdated nodes are all those with dinamic ip non hallmarked node:)
Couldn't happy that much
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.
Done:
programm output ("BAMM" = BalanceAlarmMailMailer.py
):
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:
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:
(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!
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*
... 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
):Code:
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:
Code:
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
Code:
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:
Code:
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.
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!
Remember, nodes need to to be updated to V 3.9.1 by tomorrow to continue receiving your node bounty payment.
Since May 3 only payments for current software versions?
I would expect a significantly higher payout...
About half of my peers use an old version.
can anybody help me how to build the horizon source code in a windows machine?
Do you mean running HZ wallet from your win machine? To run HZ wallet you don't need to building them on win machine, all you need is to install Java there. Go to java.com and install it. After installing edit nhz-default-properties file at conf dir inside HZ source directory you download earlier.
Now go to START>RUN>cmd
Nevigate your HZ directory and run run.bat
Your wallet should be running.
Now from your browser open http://127.0.0.1:7776/ and enjoy HZ crypto world!
Don't Forget to let us know if have successful or not.
thanks a lot!
can anybody help me how to build the horizon source code in a windows machine?
Do you mean running HZ wallet from your win machine? To run HZ wallet you don't need to building them on win machine, all you need is to install Java there. Go to java.com and install it. After installing edit nhz-default-properties file at conf dir inside HZ source directory you download earlier.
Now go to START>RUN>cmd
Nevigate your HZ directory and run run.bat
Your wallet should be running.
Now from your browser open http://127.0.0.1:7776/ and enjoy HZ crypto world!
Don't Forget to let us know if have successful or not.
Remember, nodes need to to be updated to V 3.9.1 by tomorrow to continue receiving your node bounty payment.
what's the difference between running a hallmark node and an ordinary node? i'm getting intereste payment for my ordinary node, if i run a hallmark node, do i get something else? how much more?
Diffrence between ordinary node and hallmarked node is very little. Hallmark node extra diclire only owner's account information to network. So that identity can be traced back to owner of it.
In dristibution part every day 1million HZ has been gifted away to community as node runners bounty equal amount to number of node up and running at said date. (1 million / number of up &running node) = paid per day to node owner. Currently node admin get paid of around 625 to 675HZ every day as bounty for running node.
To track you can check account NHZ-A9WQ-PC3J-B3SN-DHQSM from where it despatched to community.
Cheers!
Remember, nodes need to to be updated to V 3.9.1 by tomorrow to continue receiving your node bounty payment.
what's the difference between running a hallmark node and an ordinary node? i'm getting intereste payment for my ordinary node, if i run a hallmark node, do i get something else? how much more?
It might look easier to earn HZ by posting useless things on their own forum but you will soon find it hard even earning 100HZ out of that.
Actually, all HZ earned from forum postings is manually checked in order to prevent people from posting useless things. If a post is deleted then the HZ gets deleted too. Also, all withdrawals are processed manually in order to prevent people trying to game the system.
Check out https://horizonplatform.io/get-started/earning-horizon/ for more info.
Yes, I supported your statement by placing 'might looks easier' mean anyone might think 'fool' system by placing lot's of content to earn HZ. But when they get 'real value' spendable on their wallet, they will find thinks are not easier to bang HZ system and earn money but have to do real job to earn money.
Mean to me it is still worth valuing every HZ we see in market for trade.
Keep the work and grow HZ network hugh, really.
REPOST from the Crypto Currency Collectors Club:
Quick major update on HZchronos: I have talked with the HZchronos community and they have agreed that increasing the redeemable promotion time 24X is a very good idea. So what was previously worth 1 hour will be worth 24 hours soon (promotion time in the CCC with a pinned post, or with a logo up top) The deal is that the community has to sell me back 300 tokens at the same price they paid, no donations, just a sell back of some tokens so I could also own some and have more incentive to add to the value. So far 200 have been sold back, so this goal is likely to be reached. Prices are still pretty much based on 24 units per day, rather than one unit per day, and I believe after people start actually using it the value will become clear and the price should increase. Giving early investors a chance at very good profits and great utility when used.
Increasing the redeemable value 24x will not necessarily reflect in price or trade value, but potentially it could over the long run after it is used and the value becomes clear in practice and genuine demand. (Also possible I have more plans and other ways to increase the value down the road) The initial sale price was 3200 HZ per unit, assuming long term this change is reflected in the price, then the long term value potentially could reach 76800 HZ per unit, although traders and the market will determine that, but I do I believe price increases are more likely after people start using HZchronos and others start wanting to use it themselves. I have also removed any future expiration dates to it, but with the caveat that if I ever leave cryptos down the road someone else would take over the CCC and HZchronos in tandem. I have no plans for quitting cryptos, but this way there are no expiration dates, and therefore the greatest potential to increase in value and utility over time.
https://www.facebook.com/groups/1610748235805154/
Quick major update on HZchronos: I have talked with the HZchronos community and they have agreed that increasing the redeemable promotion time 24X is a very good idea. So what was previously worth 1 hour will be worth 24 hours soon (promotion time in the CCC with a pinned post, or with a logo up top) The deal is that the community has to sell me back 300 tokens at the same price they paid, no donations, just a sell back of some tokens so I could also own some and have more incentive to add to the value. So far 200 have been sold back, so this goal is likely to be reached. Prices are still pretty much based on 24 units per day, rather than one unit per day, and I believe after people start actually using it the value will become clear and the price should increase. Giving early investors a chance at very good profits and great utility when used.
Increasing the redeemable value 24x will not necessarily reflect in price or trade value, but potentially it could over the long run after it is used and the value becomes clear in practice and genuine demand. (Also possible I have more plans and other ways to increase the value down the road) The initial sale price was 3200 HZ per unit, assuming long term this change is reflected in the price, then the long term value potentially could reach 76800 HZ per unit, although traders and the market will determine that, but I do I believe price increases are more likely after people start using HZchronos and others start wanting to use it themselves. I have also removed any future expiration dates to it, but with the caveat that if I ever leave cryptos down the road someone else would take over the CCC and HZchronos in tandem. I have no plans for quitting cryptos, but this way there are no expiration dates, and therefore the greatest potential to increase in value and utility over time.
https://www.facebook.com/groups/1610748235805154/
Jump to: