2018-10-11 04:10:57
I've been buying a little.

Fireduck
2018-10-11 04:11:28
How many altcoins have the devs buy more with their own money? :wink:

Fireduck
2018-10-11 07:07:06
re: you in <#CAR9AKG64|random> :D

Rotonen
2018-10-11 14:36:39
There is no connection, sir

Fireduck
2018-10-11 23:38:12
Anyone experiencing variance in expected hash rates? I have 2 servers that @mjay benchmarked at 3 M/s and one is getting 1.5-1.4 M/s. Another one is getting 1.5 M/s to 850 K/s. Originally the second only had half the cores enabled and when I enabled all of the cores it went to 1.5 M/s but I shut down to change the power strip and it reverted to 850 K for some reason. Another server I have has done 800 K/s before but now consistently registers about 450 K/s. I might try upgrading to 1.4.0. Any other ideas?

aikida3k