techmetx11

The tests related to DNS connectivity (resolving stuff over Quad9's regular DNS server, not even DNS-over-TLS) seems to failing, which fails the whole PR. I've tested the unit tests on...

It seems like the latest commit fixed the DNS resolving errors (which I suspect is due to the hardcoded path to the TLS certificate bundle not existing within the CI's...

Were you mining in the daemon? or offloading RandomX verification to your `monerod` node (from p2pool or something)

> *snip* Yup, This definitely looks like the RandomX hasher's JIT code cache may have been overwritten by something, and it ended up executing garbage CPU instructions, which was what...

If this was a implemented feature in Monero clients, then there is nothing stopping giant mining pools from refusing to mine transactions if they aren't "unprotected" (1 ring member, etc.),...

> If I had to guess, it's probably the [RandomX JIT compiler](https://github.com/tevador/RandomX/blob/10494476d6236b177733224123747201dec180bb/src/jit_compiler_a64.cpp). Was it mining? IIRC, W+X should only be enabled on mining threads. You can try running the binary...

> I appreciate the response. Any idea if it can be turned off in anyway while not mining? Try running monerod with the env variable that @jeffro256 gave. This will...