01:41:31 <br-m> <jeffro256> sech1: quick implementation question: the cache and dataset are byte-for-byte the same after V2 right ?  In other words, I don't need to do any special invalidation because of V2, correct ?
01:41:51 <br-m> <jeffro256> The prefetching is different as I understand it , but that doesn't affect the data itself ?
08:57:59 <sech1> jeffro256 yes, cache and dataset are the same. You only need to set the RANDOMX_FLAG_V2 for RandomX virtual machines when you switch to v2
11:04:01 <DataHoarder> cache and dataset are the same
11:04:38 <DataHoarder> the superscalar hash is not changed (but ofc it gets called more in light mode)
11:05:49 <DataHoarder> just to be consistent one could put the hardfork threshold (initial one that changes PoW function) on a randomx epoch change
11:06:28 <DataHoarder> the the changes are all within VM code and parameters
11:07:06 <DataHoarder> the even
11:42:17 <sech1> No need to put it on RandomX epoch change. I even added logic to XMRig to not update the dataset if it's a switch to v2 and it's not an epoch change
12:26:59 <DataHoarder[m]> yeah, if you have the cache/dataset pointers around they can be passed to the VM creation and that'd just work (somehow this message wasn't seen)
13:08:55 <sech1> Don't even need to create a new vm, see "test_switch" in src/tests.cpp
13:13:21 <DataHoarder[m]> I mean for monero code itself and verification, not external miners