11:34:36 <ErCiccione[m]> would people prefer to not have this chat listed on getmonero?
11:44:33 <Inge-> 6:24 < hyc> eh? please don't
11:44:33 <Inge-> 16:25 < hyc> it's low noise now, should stay that way
12:20:52 <ErCiccione[m]> yeah, was asking to make sure it was a shared opinion
15:29:42 <gingeropolous> ErCiccione[m], i also enjoy the low noise. i think people that want to find it will find a way.
15:30:09 <ErCiccione[m]> ok. I closed the PR
17:40:12 <hyc> thanks
17:40:28 <hyc> I expect people who are interested probably find their way here from -dev
18:10:18 <gingeropolous> i wonder if randomx verification could be made cheaper by including headers for each loop
18:10:40 <gingeropolous> so then a hash check could be performed after performing the first loop
20:44:27 <sech1> Nonce bits heatmap: https://i.imgur.com/ccbyqey.png
20:49:34 <hyc> about what you'd expect for nonces counting up from zero
20:50:07 <hyc> using the high byte for job separation I suppose
20:50:41 <sech1> high byte is nicehash and xmrig-proxy
20:51:06 <hyc> so yes, distributing work
20:51:19 <sech1> bits 14-15 is xmrig's nonce batch size (32768)
20:52:27 <hyc> looks like bits 15-24 are also distributing work
20:53:01 <sech1> No, it just progresses from 0 to 16777216 in steps of size 32768
20:53:06 <hyc> ah
20:53:09 <sech1> not many CPUs can do 2^24 hashes in ~2 minutes
20:53:26 <sech1> so bits 23-24 get really cold
20:53:55 <hyc> makes sense
20:54:38 <sech1> usually very slow 10-15 minute blocks can have these bits set to 1. Or monerod solo miners - they select start point at random
20:55:55 <sech1> there's a spike in bits 20-22 around 450 on horizontal axis. This is EPYC servers on Azure when we had that 900 MH/s miner
20:56:42 <hyc> heh cute