is the pow output 32 bytes?

yes

256 bits

thanks

what's a typical hash rate for a high end CPU?

nvm found this monerobenchmarks.info

tevador regarding that cancelled GRIN ASIC: miningpoolstats.stream/grin-c32

568 kGPs, lol

that's more than 8500 G32-1800 miners

so they just decided to keep it for themselves

post production testing was surprisingly good and they decided to not sell it?

c32 hashrate on GRIN is much higher than c31 hashrate, this can't be GPUs

that's what you get when you jump in bed with ASIC manufacturers

100% unknown ??

that must be a bug, those ASICs are faster on CT31 than CT32

they would be stupid to mine CT32, at least until CT31 is phased out

a bug? It's calculated from network diff for C32

could be a display bug on the website

328GPS(+-5%) for CC31+, 65.6GPS(+-5%) for CC32+

C32 is slower, it's correct

so they do a 4x TM tradeoff for C32

but they get 100% rewards from C32

they would get 95% from C31

maybe it doesn't work on C31 :D

if they produced 8500 machines already, then the twitter post is a big lie

well, there's also Obelisk and someone other manufacturer too, don't remember exactly

maybe it's their ASIC which does only C32

sech1: if you look at the blockchain explorer, there is not a single C32 block in the last 100 blocks: grinscan.net

I doubt anyone is mining it

hmm, then it's weird

maybe a glitch

miners will start switching to C32 in March-April

or maybe C32 difficulty is just set to this high values and will drop when the switch happens

I don't know how exactly this switching works

so it's just a high network difficulty at this point, no one is mining it

jtgrassie: monerop.com received block 12 seconds after all pools has wrong time

or has*

monerop.com has a 30 second server side cache in front of the web ui.

have you checked time?

i'm about stratum port

It's likely not cached

if you have monerod logs then what was the time of the last received block?

It must be 12 seconds delayed from others

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.

Then there is some problem in my heuristic for pool scanning

Share height and time (local time logged by daemon) of the last received block by your monerod