Bitcoin Forum
September 21, 2018, 10:50:30 PM *
News: ♦♦ New info! Bitcoin Core users absolutely must upgrade to previously-announced 0.16.3 [Torrent]. All Bitcoin users should temporarily trust confirmations slightly less. More info.
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 [103] 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 ... 155 »
  Print  
Author Topic: .  (Read 490823 times)
This is a self-moderated topic. If you do not want to be moderated by the person who started this topic, create a new topic.
BTCat
Legendary
*
Offline Offline

Activity: 1554
Merit: 1000


“DREAM - Create opportunity. Deliver success.”


View Profile
August 01, 2015, 08:41:04 AM
 #2041


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.



▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
█                             █
█                             █
█                             █
█                             ▀

█    ▀▀▀▀▀█▄      ▀▀▀▀▀█▄     ▀▀▀▀▀▀▀       ▄█▄       █▄    ▄█
█    ▄     ██          ▄█     ▄▄▄▄▄▄▄      ▄█▀█▄      █▀█▄▄█▀█
█    █    ▄█▀     █▀▀▀██                  ▄█▀ ▀█▄     █  ▀▀  █
█    ▀▀▀▀▀▀       ▀    ▀▀     ▀▀▀▀▀▀▀     ▀     ▀     ▀      ▀

█                             █
█                             █
█                             █
█▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄█



     ▄█████████████████████▄▄
                         ▀▀▀███▄
                              ▀██▄
 ▄▄▄▄▄▄▄▄▄▄▄▄                   ██▌
▀▀▀▀▀▀▀▀▀▀▀▀   ▄█               ▐██
               ██                ██▌
               ██                ██▌
▄▄▄▄▄▄▄▄▄▄▄▄   ██                ██▌
 ▀▀▀▀▀▀▀▀▀▀▀   ██               ▐██
               ██               ██▌
               ██             ▄██▀
     ▀█████▌   ██          ▄▄██▀
               █████████████▀▀
▄▄
██
██
██
██
██
██
██
██
██
1537570230
Hero Member
*
Offline Offline

Posts: 1537570230

View Profile Personal Message (Offline)

Ignore
1537570230
Reply with quote  #2

1537570230
Report to moderator
1537570230
Hero Member
*
Offline Offline

Posts: 1537570230

View Profile Personal Message (Offline)

Ignore
1537570230
Reply with quote  #2

1537570230
Report to moderator
1537570230
Hero Member
*
Offline Offline

Posts: 1537570230

View Profile Personal Message (Offline)

Ignore
1537570230
Reply with quote  #2

1537570230
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
duncan_idaho
Sr. Member
****
Offline Offline

Activity: 354
Merit: 250


View Profile
August 01, 2015, 08:47:52 AM
 #2042


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.

            ▄▄████▄▄
        ▄▄██████████████▄▄
      ███████████████████████▄▄
      ▀▀█████████████████████████
██▄▄       ▀▀█████████████████████
██████▄▄        ▀█████████████████
███████████▄▄       ▀▀████████████
███████████████▄▄        ▀████████
████████████████████▄▄       ▀▀███
 ▀▀██████████████████████▄▄
     ▀▀██████████████████████▄▄
▄▄        ▀██████████████████████▄
████▄▄        ▀▀██████████████████
█████████▄▄        ▀▀█████████████
█████████████▄▄        ▀▀█████████
██████████████████▄▄        ▀▀████
▀██████████████████████▄▄
  ▀▀████████████████████████
      ▀▀█████████████████▀▀
           ▀▀███████▀▀



.SEMUX
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
  Semux uses 100% original codebase
  Superfast with 30 seconds instant finality
  Tested 5000 tx per block on open network
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
acha
Jr. Member
*
Offline Offline

Activity: 51
Merit: 10


View Profile
August 01, 2015, 09:28:25 AM
 #2043


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
cbkr
Newbie
*
Offline Offline

Activity: 56
Merit: 0


View Profile
August 01, 2015, 09:38:33 AM
 #2044

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
duncan_idaho
Sr. Member
****
Offline Offline

Activity: 354
Merit: 250


View Profile
August 01, 2015, 10:11:10 AM
 #2045

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.

            ▄▄████▄▄
        ▄▄██████████████▄▄
      ███████████████████████▄▄
      ▀▀█████████████████████████
██▄▄       ▀▀█████████████████████
██████▄▄        ▀█████████████████
███████████▄▄       ▀▀████████████
███████████████▄▄        ▀████████
████████████████████▄▄       ▀▀███
 ▀▀██████████████████████▄▄
     ▀▀██████████████████████▄▄
▄▄        ▀██████████████████████▄
████▄▄        ▀▀██████████████████
█████████▄▄        ▀▀█████████████
█████████████▄▄        ▀▀█████████
██████████████████▄▄        ▀▀████
▀██████████████████████▄▄
  ▀▀████████████████████████
      ▀▀█████████████████▀▀
           ▀▀███████▀▀



.SEMUX
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
  Semux uses 100% original codebase
  Superfast with 30 seconds instant finality
  Tested 5000 tx per block on open network
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
cbkr
Newbie
*
Offline Offline

Activity: 56
Merit: 0


View Profile
August 01, 2015, 01:28:06 PM
 #2046

fixed a bug and sent all transactions out again.
please message me with details (account#) if you did not receive you node bounty.
GoldenEye
Hero Member
*****
Offline Offline

Activity: 600
Merit: 500


View Profile
August 01, 2015, 04:01:11 PM
 #2047

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.
SomeRelax
Sr. Member
****
Offline Offline

Activity: 350
Merit: 250


View Profile
August 01, 2015, 05:55:09 PM
 #2048

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
cbkr
Newbie
*
Offline Offline

Activity: 56
Merit: 0


View Profile
August 01, 2015, 07:14:59 PM
 #2049

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
SomeRelax
Sr. Member
****
Offline Offline

Activity: 350
Merit: 250


View Profile
August 01, 2015, 07:51:46 PM
 #2050

is the node bounty script open source?
cbkr
Newbie
*
Offline Offline

Activity: 56
Merit: 0


View Profile
August 01, 2015, 08:51:11 PM
 #2051

is the node bounty script open source?

it is not, and we are not planning to make it public.
TheQuake
Newbie
*
Offline Offline

Activity: 19
Merit: 0


View Profile
August 02, 2015, 12:38:00 AM
 #2052

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

So you can confirm that payment per node for 01.08.2015 and 31.07.2015 was 314HZ (you paid 628HZ per node in the lastest payment)? On 30.07.2015 it was around 600HZ.
GoldenEye
Hero Member
*****
Offline Offline

Activity: 600
Merit: 500


View Profile
August 02, 2015, 08:48:09 AM
 #2053

How about, when the "Last Payment" time will be updated AFTER the payment was successfully sent?
It's happened again: no payment and the "Next Payment" counter was adapted.
cbkr
Newbie
*
Offline Offline

Activity: 56
Merit: 0


View Profile
August 02, 2015, 02:11:08 PM
 #2054

So you can confirm that payment per node for 01.08.2015 and 31.07.2015 was 314HZ (you paid 628HZ per node in the lastest payment)? On 30.07.2015 it was around 600HZ.

yes. 314.40237421 per node on 01.08., doubled for each node that should have gotten a payment on 31.07.
cbkr
Newbie
*
Offline Offline

Activity: 56
Merit: 0


View Profile
August 02, 2015, 02:23:18 PM
 #2055

How about, when the "Last Payment" time will be updated AFTER the payment was successfully sent?
It's happened again: no payment and the "Next Payment" counter was adapted.

that is intentional and changing this would require a rewrite of big parts of the bounty system.
I'm currently replaying today's transactions and I fixed another bug that prevented them from being sent in the first place.
today the amount is 482.92546181 per node, 1272 nodes total and 214 transactions
off-by-one errors possible because I pulled this from a debug script that didn't need to give perfect values at the time it was written, I'm just trying to improve transparency.

edit: all transactions sent.
GoldenEye
Hero Member
*****
Offline Offline

Activity: 600
Merit: 500


View Profile
August 02, 2015, 07:30:10 PM
 #2056

today the amount is 482.92546181 per node, 1272 nodes total and 214 transactions

Transparency is needed
thanks
duncan_idaho
Sr. Member
****
Offline Offline

Activity: 354
Merit: 250


View Profile
August 03, 2015, 06:13:35 AM
 #2057

Can someone who used version 4.0 can confirm that no more blokchain rescan while daemon is up and running?

            ▄▄████▄▄
        ▄▄██████████████▄▄
      ███████████████████████▄▄
      ▀▀█████████████████████████
██▄▄       ▀▀█████████████████████
██████▄▄        ▀█████████████████
███████████▄▄       ▀▀████████████
███████████████▄▄        ▀████████
████████████████████▄▄       ▀▀███
 ▀▀██████████████████████▄▄
     ▀▀██████████████████████▄▄
▄▄        ▀██████████████████████▄
████▄▄        ▀▀██████████████████
█████████▄▄        ▀▀█████████████
█████████████▄▄        ▀▀█████████
██████████████████▄▄        ▀▀████
▀██████████████████████▄▄
  ▀▀████████████████████████
      ▀▀█████████████████▀▀
           ▀▀███████▀▀



.SEMUX
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
  Semux uses 100% original codebase
  Superfast with 30 seconds instant finality
  Tested 5000 tx per block on open network
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
mike34
Member
**
Offline Offline

Activity: 81
Merit: 10


View Profile
August 03, 2015, 07:41:00 AM
 #2058

great work on the new wallet hz team so smooth and easier to use using less memory works great on windows 10
looks really nice as well.

 Grin Grin Grin Grin Grin Grin Grin Grin Grin Grin Grin Grin Grin Grin Grin Grin Cool Cool Cool Cool Cool Smiley Smiley Smiley Smiley Smiley Smiley Smiley Smiley Smiley Smiley Smiley Smiley Smiley

BITCORE ADDRESS                   19X6CoqWzCYp3frFsbpxmrGczyftenart1                       BITCOIN ADDRESS                    183hTfQW6xuSi3yMiJuH3NvPFRHE5U5oSS

ETHEREUM CLASSIC ADDRESS  0xfb915070495154a395aa4d9851658d8505fa1418       ETHEREUM ADDRESS     0xedc25d2dfb72c9c65564a91b7cde2f334159b100
GoldenEye
Hero Member
*****
Offline Offline

Activity: 600
Merit: 500


View Profile
August 03, 2015, 09:28:45 AM
 #2059

Can someone who used version 4.0 can confirm that no more blokchain rescan while daemon is up and running?

See here
Code:
2015-08-03 11:22:36 INFO: nhz.debugTraceLog = "nhz-trace.csv"
2015-08-03 11:22:36 INFO: Genesis block already in database
2015-08-03 11:22:36 INFO: Last block height: 413166
2015-08-03 11:22:36 INFO: nhz.forceScan = "false"
2015-08-03 11:22:37 INFO: Started API server at 127.0.0.1:7776
2015-08-03 11:22:37 INFO: Started peer networking server at 0.0.0.0:7774
2015-08-03 11:22:37 INFO: Initialization took 4 seconds
2015-08-03 11:22:37 INFO: Horizon server NHZ V4.0e started successfully.
duncan_idaho
Sr. Member
****
Offline Offline

Activity: 354
Merit: 250


View Profile
August 03, 2015, 12:45:11 PM
 #2060

Can someone who used version 4.0 can confirm that no more blokchain rescan while daemon is up and running?

See here
Code:
2015-08-03 11:22:36 INFO: nhz.debugTraceLog = "nhz-trace.csv"
2015-08-03 11:22:36 INFO: Genesis block already in database
2015-08-03 11:22:36 INFO: Last block height: 413166
2015-08-03 11:22:36 INFO: nhz.forceScan = "false"
2015-08-03 11:22:37 INFO: Started API server at 127.0.0.1:7776
2015-08-03 11:22:37 INFO: Started peer networking server at 0.0.0.0:7774
2015-08-03 11:22:37 INFO: Initialization took 4 seconds
2015-08-03 11:22:37 INFO: Horizon server NHZ V4.0e started successfully.

Thank you This is great improvement. If i update nodes to 4.0e then I will must update to 5.0 in future?

            ▄▄████▄▄
        ▄▄██████████████▄▄
      ███████████████████████▄▄
      ▀▀█████████████████████████
██▄▄       ▀▀█████████████████████
██████▄▄        ▀█████████████████
███████████▄▄       ▀▀████████████
███████████████▄▄        ▀████████
████████████████████▄▄       ▀▀███
 ▀▀██████████████████████▄▄
     ▀▀██████████████████████▄▄
▄▄        ▀██████████████████████▄
████▄▄        ▀▀██████████████████
█████████▄▄        ▀▀█████████████
█████████████▄▄        ▀▀█████████
██████████████████▄▄        ▀▀████
▀██████████████████████▄▄
  ▀▀████████████████████████
      ▀▀█████████████████▀▀
           ▀▀███████▀▀



.SEMUX
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
  Semux uses 100% original codebase
  Superfast with 30 seconds instant finality
  Tested 5000 tx per block on open network
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
█ █
Pages: « 1 ... 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 [103] 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 ... 155 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!