we went under one giga nethash after all, still adjusting, it seems
The difficulty still corresponds to 1.75GH/s, it needs more time to fully adjust
the slow adjust is sorta nice as it gives ample time to react
people trying to make transactions will disagree
The situation is not that bad, we are at >3 blocks per hour
the largest gap was 3h?
I think so
2h 27min
34638 to 34639
and if the minerbase grows to trigger a field change, more and more of them will prep up in time
I doubt it will happen any time soon
yeah, gives ample time to widen the nethash distribution
let’s see how that looks like in february
Fun times
@Fireduck just mine on jet, as far as i can tell the rest of your fleet does not actually contribute
The rest of the fleet does all the cpu work
the cpu on jet is really slow somehow
sounds weird
I know
I can't explain it
I would get only about 300hk/s from jet using ram and cpu as hard as I could
@Fireduck I don't understand why there's so much overhead.
but get about 1mh/s if I use it to support the rest of the fleet
@Clueless nor do I. I suspect it is something about being a 4-socket machine and maybe everything is lost in cross socket syncrhonization.
CPU processing hashes is slower than just providing IO to the rest of the fleet, no?
yep
It can sling over network faster than it can hash locally
I don't find that part confusing.
nethash: 871.708 Mh/s what diff are we heading to with 870 mh/s?
are you asking me to math?
38.92525885055614561430
; 870*1000000*600 522000000000 log(522000000000)/log(2) ~38.92525885055614561
The great thing about the log2 based difficulty is that the math is all very simple
yeah, thanks for the formula. i will write this down.
I should put it into the explorer of 'if we maintain this hash rate, this will be the difficulty'
maybe with better words
that is a very good idea.
no, that is snake eat tail