2019-01-04 08:27:05
we went under one giga nethash after all, still adjusting, it seems

Rotonen
2019-01-04 13:18:31
The difficulty still corresponds to 1.75GH/s, it needs more time to fully adjust

mjay
2019-01-04 17:07:58
the slow adjust is sorta nice as it gives ample time to react

Rotonen
2019-01-04 17:08:30
people trying to make transactions will disagree

Rotonen
2019-01-04 17:09:38
The situation is not that bad, we are at >3 blocks per hour

mjay
2019-01-04 17:17:21
the largest gap was 3h?

Rotonen
2019-01-04 17:23:59
I think so

mjay
2019-01-04 17:25:03
2h 27min

mjay
2019-01-04 17:26:10
34638 to 34639

mjay
2019-01-04 17:34:15
and if the minerbase grows to trigger a field change, more and more of them will prep up in time

Rotonen
2019-01-04 17:38:07
I doubt it will happen any time soon

mjay
2019-01-04 17:44:29
yeah, gives ample time to widen the nethash distribution

Rotonen
2019-01-04 17:44:48
let’s see how that looks like in february

Rotonen
2019-01-04 17:50:12
Fun times

Fireduck
2019-01-04 18:13:16
@Fireduck just mine on jet, as far as i can tell the rest of your fleet does not actually contribute

Rotonen
2019-01-04 18:14:45
The rest of the fleet does all the cpu work

Fireduck
2019-01-04 18:14:52
the cpu on jet is really slow somehow

Fireduck
2019-01-04 18:20:47
sounds weird

Rotonen
2019-01-04 18:21:36
I know

Fireduck
2019-01-04 18:21:45
I can't explain it

Fireduck
2019-01-04 18:22:03
I would get only about 300hk/s from jet using ram and cpu as hard as I could

Fireduck
2019-01-04 18:22:17
@Fireduck I don't understand why there's so much overhead.

Clueless
2019-01-04 18:22:18
but get about 1mh/s if I use it to support the rest of the fleet

Fireduck
2019-01-04 18:22:48
@Clueless nor do I. I suspect it is something about being a 4-socket machine and maybe everything is lost in cross socket syncrhonization.

Fireduck
2019-01-04 18:22:54
CPU processing hashes is slower than just providing IO to the rest of the fleet, no?

Clueless
2019-01-04 18:23:04
yep

Fireduck
2019-01-04 18:23:13
It can sling over network faster than it can hash locally

Fireduck
2019-01-04 18:23:16
I don't find that part confusing.

Clueless
2019-01-04 18:37:00
nethash: 871.708 Mh/s
what diff are we heading to with 870 mh/s?

fydel
2019-01-04 18:38:49
are you asking me to math?

Fireduck
2019-01-04 18:39:47
38.92525885055614561430

Fireduck
2019-01-04 18:40:37
; 870*1000000*600
522000000000
log(522000000000)/log(2)
~38.92525885055614561

Fireduck
2019-01-04 18:40:50
The great thing about the log2 based difficulty is that the math is all very simple

Fireduck
2019-01-04 18:41:15
yeah, thanks for the formula. i will write this down.

fydel
2019-01-04 18:42:57
I should put it into the explorer of 'if we maintain this hash rate, this will be the difficulty'

Fireduck
2019-01-04 18:43:03
maybe with better words

Fireduck
2019-01-04 18:43:19
that is a very good idea.

fydel
2019-01-04 20:06:00
no, that is snake eat tail

Rotonen