Search found 5 matches
- Sun Jul 30, 2017 5:29 pm
- Forum: Development Discussion and Feedback
- Topic: Status as of Saturday, July 29, 2017
- Replies: 43
- Views: 24352
Re: Status as of Saturday, July 29, 2017
just a quick scan of the new comments since i posted. all seems to be directed to spikes in hashrate. i propose a secondary measure. when hashrate/workers hit a maximum limit, disable API requests, enable again once falls below set threshold, bots will move on to other pools, NH becomes a non issue...
- Sun Jul 30, 2017 11:30 am
- Forum: Development Discussion and Feedback
- Topic: Status as of Saturday, July 29, 2017
- Replies: 43
- Views: 24352
Re: Status as of Saturday, July 29, 2017
I do appreciate the response Steve, though the essential message is unchanged - - Until you guys find a strategy to set max performance thresholds - with viable mitigation that kicks in and prevents the system from becoming overloaded . . nothing will improve for us miners, i.e. the system is not p...
- Sat Jul 29, 2017 2:50 am
- Forum: System support
- Topic: 7/28/2017 11 pm est Down again
- Replies: 1
- Views: 1700
Re: 7/28/2017 11 pm est Down again
you can create a ticket at support.prohashing.com
- Sat Jul 15, 2017 8:17 pm
- Forum: System support
- Topic: [Feature req] Blacklist Arg
- Replies: 9
- Views: 4961
Re: [Feature req] Blacklist Arg
i personally would use blacklist feature to disable some coins that gets bugged at top of the list. Sometimes, some coins sits there giving huge amount of orphans/stales, just waste of hashpower directed to those coins. And if you get directed to that coin by system, you get those stales etc. causes...
- Sat Jul 15, 2017 4:38 pm
- Forum: System support
- Topic: [Feature req] Blacklist Arg
- Replies: 9
- Views: 4961
Re: [Feature req] Blacklist Arg
I think that's a great idea, definitely would use it for some coins!