14:17:58 <cohcho> 22163 miners with 51.5MH/s from nicehash[0] and 26395 miners with 935.9MH/s from miningpoolstats[1] are different and therefore can be summarized, right?
14:18:34 <cohcho> [0] http://web.archive.org/web/20191224132957if_/https://api2.nicehash.com/main/api/v2/public/orders/active2
14:18:41 <cohcho> [1] http://web.archive.org/web/20191224141157if_/https://data.miningpoolstats.stream/data/monero.js?t=1
15:11:39 <moneromooo> And a disquieting number of times where the instantaneous block rate is pretty high.
15:18:49 <cohcho> Small coins decided to abondon PoW and switched PoS some time ago. They didn't find any solution for constantly changing hashrate and delay between blocks. Their super-duper difficulty algos didn't has anything except beatuful name.
15:22:45 <cohcho> Monero isn't a small coin on the market of randomx mining but it may be changed.
20:13:06 <gingeropolous> i wonder if the tiny lag introduced by epoch changes can cause cascading effects in diff adjustment ....
20:23:43 <cohcho> You can write a simulation and test it.
20:34:34 <tevador> no cascading effect, but it will decrease the difficulty by about 0.001%
20:35:24 <tevador> because nobody is hashing for about 4 seconds every 2048 blocks
21:29:57 <cohcho> The source of "effects in diff adjustment" is obviously not constant hashrate of miners. But there is no solution unless you want to speed up mining reward distribution by lowering diff after dropping hashrate.
21:42:07 <tevador> the effect is so small that it can be ignored
21:43:09 <cohcho> No, I mean this effect "the instantaneous block rate is pretty high"
23:04:16 <tevador> "instantaneous rate" is a bit hard to measure in a Poisson process