FYI. I changed to NiceHash and I am not seeing the disconnects like I do with prohashing. I consider this a Prohashing problem and nothing on my end. So until it is fixed I will use Nicehash. I'll check back here every day and change back one of the miners to prohashing from time to time to see how ...

And also. Let me say again. This problem started 21 December. I've been mining with these KNC Titans for over 2 years now on Prohashing without this problem.

No difference when setting c=litecoin

I don't get the difference between "d=" and "h=". In the help you also have this "Working around KNC Titan limitations: Use "h=3" or "h=5.". Should I use "h=5 d=8192"?

AppleMiner wrote:what password setting are you using on the titan?

a=scrypt h=5

Hi This might be related to https://forums.prohashing.com/viewtopic.php?f=16&t=2975 and https://forums.prohashing.com/viewtopic.php?f=16&t=2930 but i'm not sure so I'm creating another post. From the 21st of December I've had constant dropouts on my KNC Titans to Prohashing. They are in sepa...

Schh maybe we get double coins. Don't tell Chris

Same for me. 10 but it should be 5.

If the verizon ips you plan of using is in the same /24 as the old ones I suggest you request a new ip range in another /24 from verizon or it might be very easy for the attacker to find the backend.

Best is of course if verizon can firewall all traffic except javapipe

If needed I can supply you with some 10G VPSes for free to forward through until you have stuff sorted out. If you manage to get access to the backend again.