15:15:41 According to this, XMRig uses a fixed offset for where the nonce is meant to be in the hashing blob: https://github.com/xmrig/xmrig/blob/7897f10c48899842749aa74a32d8405e0fe74af1/src/base/net/stratum/Job.cpp#L174 15:15:42 Since the nonce comes after the timestamp, which is a varint, isn't this dangerous? Once timestamp varints eventually become 6 bytes long, this offset will be wrong and from what I understand, that means miners will start replacing the last byte of the prev block hash thinking it's part of the nonce, making them mine invalid blocks 15:52:41 Yes 15:52:52 Reminder: fix it in XMRig before Tue Oct 26 3058 03:46:08 GMT+0000 15:53:02 I have just a bit more than 1000 years to fix it :D 15:53:38 Major and minor version are also varints, there's more chance one of those will become 2 bytes before 3058 15:56:19 All pool software also uses fixed nonce offset. I think it's a bit early to talk about the fix, because many things can change before Monero v128 :) 15:59:35 P2Pool software calculates nonce offset correctly, thanks to parsed block template handily available 15:59:49 Let’s just make sure that the fixed nonce doesn’t become *too* embedded into the currency infrastructure 15:59:50 The people using XMR 1000 years in the future will thank us lol 16:00:06 (Ie we don’t need to fix it per se, we just need to keep it fix*able*) 16:00:09 Everyone will use P2Pool in 1000 years :D 16:00:20 The good ending:) 17:00:17 Is there an ETA on v0.18.3.4? 18:29:59 is there an ETA on RandomX v2? 18:30:48 tomorrow morning 18:35:35 also FCMP, i haven't heard any updates for a while 18:47:18 Its progressing, i think you'll probably find more info in monero-research-lab or monero-research-lounge 23:05:20 Is this really happening? Will it require a hard fork?