Pages:
Author

Topic: . - page 53. (Read 491736 times)

newbie
Activity: 56
Merit: 0
August 01, 2015, 03:14:59 PM
fixed a bug and sent all transactions out again.
please message me with details (account#) if you did not receive you node bounty.

I do not want to annoy, the replay was noly for one day, but two missed.

payments from both days were included in the replay, as they would have been in the normal payout
sr. member
Activity: 350
Merit: 250
August 01, 2015, 01:55:09 PM
fixed a bug and sent all transactions out again.
please message me with details (account#) if you did not receive you node bounty.
message has been sent
thanks
hero member
Activity: 601
Merit: 500
August 01, 2015, 12:01:11 PM
fixed a bug and sent all transactions out again.
please message me with details (account#) if you did not receive you node bounty.

I do not want to annoy, the replay was noly for one day, but two missed.
newbie
Activity: 56
Merit: 0
August 01, 2015, 09:28:06 AM
fixed a bug and sent all transactions out again.
please message me with details (account#) if you did not receive you node bounty.
sr. member
Activity: 355
Merit: 250
August 01, 2015, 06:11:10 AM
Thanks for explanation. I read your post carefully and you have your right but not completely. I undertstood your point of view but you need too look at in from our perspective. We are a big part of this system, everyone invest some money, some time, some knowledge in this project. I remember (for example) version 3.8 and payout problem wasn't often. If you look for this bctalk thread for last month posts then you will see the frequency of problem. No week without problem.

For comparison IMO it looks like (for example) big ISP company  frequentlu cut out internet access for their users. I know how angry people are in this situation. And if that situation occur once a month then nobody care about it but if occu few times in a week then hell is starting.

I am not saying this only becouse of annoying. I want horizon team to be more professional an take care of their users and node owners. We are like big "family" and i so no reason for post like mine or yours to attack ourselves but we need to understand our needs.

Peace.
newbie
Activity: 56
Merit: 0
August 01, 2015, 05:38:33 AM
Ok. I am really angry then i give some advice becouse you statistically blowing up a payout script once a week and we (node operators loose money)
I work in IT department few years as a network/system admin so maybe this will be helpful for you:

1) If something work properly dont try to "fix" it
2) Don't make any changes in working system in production environment. Do it on testnet or other test environment
3) If you don't know what are you doing, don't touch it becouse in 99% you will broke it.
4) If you broke something, inform your users about that.

So guys please don't touch this damn payout script and stop blowing it up. We all want our HZ for supporting network. This situation is really frustrating for us and unprofessional. I loose my money for renting servers, for IP assignment and loose my time to upgrade nodes to newest hz release so i expect it working.

Ok listen,

in no particular order:

1) in over a year we had not much downtime and there was only one time where payments were lost. all other times we paid you guys compensation - often even more than you initially lost - even though you guys are annoying as hell.
2) if you have no idea how big the bounty system is, how many things are working together to do payouts every day and how many things in it can, for some unexpected reason fail, don''t try to lecture the actual developers about it, because you have NO IDEA and you are the reason it is really hard to contuinue caring and implementing new features and bugfixes.
3) if you would read the forum you would be able to see that we are indeed testing on the testnet - it's just that the testnet IS NOT THE REAL THING and there are slight differences. I know that the testing is not perfect but the bounty system has been there since day one - though you might not even remember that because I suspect you joined recently - and it's been growing ever since. It has to be adapted for new horizon versions, it needs new features to control which nodes get paid and which don't, and so on. in short: it HAS TO BE TOUCHED TO CONTINUE WORKING FOR YOU
4) as you can see, users are pretty much informed the second something breaks because people like you are jumping on the forum and tell everybody. that's great. Most of them already know that we will repay every bit if it's possible. (one time we did not have a log of the failed transactions, sorry!) I could have used the 15 minutes I was typing this post to fix things.
5) Please tell me your account ID and I will relieve you of the immeasureable suffering you have to endure with the bounty system by stopping transactions for you.
6) Suck it


Sincerely,

a pissed developer that has to fix everything while explaining everything countless times ont he forum to people that do not care

Edit: a word
jr. member
Activity: 51
Merit: 10
August 01, 2015, 05:28:25 AM

So guys please don't touch this damn payout script and stop blowing it up. We all want our HZ for supporting network. This situation is really frustrating for us and unprofessional. I loose my money for renting servers, for IP assignment and loose my time to upgrade nodes to newest hz release so i expect it working.

Give it a break dude. Realize crypto's is in early stages of developments and these things happen. As far I know HZ is paying very regularly and they try to not miss any payments or correct it all the time. Besides they need to install updates to prepare for bigger updates, etc. Growing something always goes with difficulties to overcome.

As far i remember (few releases ago) there were no many problems with payout script (sometimes but not often) Now is nightmare, is regular problem and looks like nobody care about it.

summer... all in the Bahamas
sr. member
Activity: 355
Merit: 250
August 01, 2015, 04:47:52 AM

So guys please don't touch this damn payout script and stop blowing it up. We all want our HZ for supporting network. This situation is really frustrating for us and unprofessional. I loose my money for renting servers, for IP assignment and loose my time to upgrade nodes to newest hz release so i expect it working.

Give it a break dude. Realize crypto's is in early stages of developments and these things happen. As far I know HZ is paying very regularly and they try to not miss any payments or correct it all the time. Besides they need to install updates to prepare for bigger updates, etc. Growing something always goes with difficulties to overcome.

As far i remember (few releases ago) there were no many problems with payout script (sometimes but not often) Now is nightmare, is regular problem and looks like nobody care about it.
legendary
Activity: 1960
Merit: 1010
August 01, 2015, 04:41:04 AM

So guys please don't touch this damn payout script and stop blowing it up. We all want our HZ for supporting network. This situation is really frustrating for us and unprofessional. I loose my money for renting servers, for IP assignment and loose my time to upgrade nodes to newest hz release so i expect it working.

Give it a break dude. Realize crypto's is in early stages of developments and these things happen. As far I know HZ is paying very regularly and they try to not miss any payments or correct it all the time. Besides they need to install updates to prepare for bigger updates, etc. Growing something always goes with difficulties to overcome.
newbie
Activity: 95
Merit: 0
August 01, 2015, 04:36:32 AM
I got the last payment 23.07.2015 3:44:14
I noticed that the countdown has stopped time:
Total Uptime: 307801 mins | Upime Until Next Payout: 359 mins
28.07.2015 updated version of the wallet on hz-v3.9.2-node
but no payment

required installation version hz-v4.0e-node?
sr. member
Activity: 355
Merit: 250
August 01, 2015, 04:14:15 AM
Ok. I am really angry then i give some advice becouse you statistically blowing up a payout script once a week and we (node operators loose money)
I work in IT department few years as a network/system admin so maybe this will be helpful for you:

1) If something work properly dont try to "fix" it
2) Don't make any changes in working system in production environment. Do it on testnet or other test environment
3) If you don't know what are you doing, don't touch it becouse in 99% you will broke it.
4) If you broke something, inform your users about that.

So guys please don't touch this damn payout script and stop blowing it up. We all want our HZ for supporting network. This situation is really frustrating for us and unprofessional. I loose my money for renting servers, for IP assignment and loose my time to upgrade nodes to newest hz release so i expect it working.
sr. member
Activity: 355
Merit: 250
August 01, 2015, 03:55:32 AM
Two days without node payment. What is going on?
newbie
Activity: 19
Merit: 0
July 31, 2015, 08:36:22 PM
Almost 4 weeks later, I would like to ask the question again.

Sorry for the wait, it's done now.
The test script worked fine on testnet, fingers crossed for the payout tonight.
I squished the data with zlib but I'm sure that's no problem for you. Smiley

Obviously has not worked. Sad
No payouts today.

:/ bug fixed.

Node check script notices that payments were sent, but they weren't.
hero member
Activity: 601
Merit: 500
July 31, 2015, 06:48:41 AM
The online time for the new V4.0e nodes is not counted by the node bounty script.

current beta versions now collect uptime

confirmed
newbie
Activity: 56
Merit: 0
July 31, 2015, 06:25:11 AM
The online time for the new V4.0e nodes is not counted by the node bounty script.

current beta versions now collect uptime
newbie
Activity: 56
Merit: 0
July 31, 2015, 06:12:14 AM
Almost 4 weeks later, I would like to ask the question again.

Sorry for the wait, it's done now.
The test script worked fine on testnet, fingers crossed for the payout tonight.
I squished the data with zlib but I'm sure that's no problem for you. Smiley

Obviously has not worked. Sad
No payouts today.

:/ bug fixed.
hero member
Activity: 601
Merit: 500
July 31, 2015, 04:40:41 AM
Almost 4 weeks later, I would like to ask the question again.

Sorry for the wait, it's done now.
The test script worked fine on testnet, fingers crossed for the payout tonight.
I squished the data with zlib but I'm sure that's no problem for you. Smiley

Obviously has not worked. Sad
No payouts today.
hero member
Activity: 575
Merit: 502
July 31, 2015, 03:39:43 AM
Database file link is corrupted. Can you post correct one?

the link is working for me:
go to the url http://hz-services.com/downloads/nhz_dbs/
and download the file 20150729-nhz_db-4.0e.zip
hero member
Activity: 601
Merit: 500
July 31, 2015, 03:33:28 AM
Database file link is corrupted. Can you post correct one?

The downloads you can find at the end of the page.

Or directly:
https://github.com/NeXTHorizon/hz-source/releases/download/hz-v4.0e/hz-v4.0e.zip

edit: sorry, this was the node
hero member
Activity: 601
Merit: 500
July 31, 2015, 03:32:20 AM
The online time for the new V4.0e nodes is not counted by the node bounty script.
Pages:
Jump to: