00:21:36 <koe> is the pow output 32 bytes?
00:22:53 <cohcho> yes
00:22:59 <cohcho> 256 bits
00:23:20 <koe> thanks
03:01:00 <koe> what's a typical hash rate for a high end CPU?
03:04:21 <koe> nvm found this https://monerobenchmarks.info/
17:49:58 <sech1> tevador regarding that cancelled GRIN ASIC: https://miningpoolstats.stream/grin-c32
17:50:06 <sech1> 568 kGPs, lol
17:50:49 <sech1> that's more than 8500 G32-1800 miners
17:51:00 <sech1> so they just decided to keep it for themselves
17:51:47 <cohcho> post production testing was surprisingly good and they decided to not sell it?
17:51:55 <sech1> c32 hashrate on GRIN is much higher than c31 hashrate, this can't be GPUs
17:52:38 <sech1> that's what you get when you jump in bed with ASIC manufacturers
18:02:24 <hyc> 100% unknown ??
18:43:24 <tevador> that must be a bug, those ASICs are faster on CT31 than CT32
18:44:09 <tevador> they would be stupid to mine CT32, at least until CT31 is phased out
18:45:26 <sech1> a bug? It's calculated from network diff for C32
18:46:09 <tevador> could be a display bug on the website
18:47:59 <tevador> 328GPS(+-5%) for CC31+, 65.6GPS(+-5%) for CC32+
18:48:28 <sech1> C32 is slower, it's correct
18:48:30 <tevador> so they do a 4x TM tradeoff for C32
18:48:41 <sech1> but they get 100% rewards from C32
18:49:17 <tevador> they would get 95% from C31
18:49:41 <sech1> maybe it doesn't work on C31 :D
18:50:35 <tevador> if they produced 8500 machines already, then the twitter post is a big lie
18:51:07 <sech1> well, there's also Obelisk and someone other manufacturer too, don't remember exactly
18:51:33 <sech1> maybe it's their ASIC which does only C32
19:01:35 <tevador> sech1: if you look at the blockchain explorer, there is not a single C32 block in the last 100 blocks: https://grinscan.net/
19:01:52 <tevador> I doubt anyone is mining it
19:03:14 <sech1> hmm, then it's weird
19:03:18 <sech1> maybe a glitch
19:04:29 <tevador> miners will start switching to C32 in March-April
19:05:22 <sech1> or maybe C32 difficulty is just set to this high values and will drop when the switch happens
19:05:29 <sech1> I don't know how exactly this switching works
19:09:51 <tevador> https://github.com/Lolliedieb/lolMiner-releases/wiki/All-you-need-to-know-about-Grin-difficulty,-C29,-C31-fade-out-and-C32
19:24:09 <sech1> so it's just a high network difficulty at this point, no one is mining it
20:11:00 <cohcho> jtgrassie: monerop.com received block 12 seconds after all pools has wrong time
20:11:11 <cohcho> or has*
23:38:04 <jtgrassie> monerop.com has a 30 second server side cache in front of the web ui.
23:39:59 <cohcho> have you checked time?
23:40:42 <cohcho> i'm about stratum port
23:41:22 <cohcho> It's likely not cached
23:44:02 <cohcho> if you have monerod logs then what was the time of the last received block?
23:44:13 <cohcho> It must be 12 seconds delayed from others
23:45:47 <jtgrassie> cohcho: the moment the daemon height changes, the pool is signalled and fetches a new block template. Checking against all my other daemons the time is within a second or 2.
23:46:24 <cohcho> Then there is some problem in my heuristic for pool scanning
23:46:53 <cohcho> Share height and time (local time logged by daemon) of the last received block by your monerod