"solutions for tracing and attribution of privacy coins and Layer 2 off-chain transactions" the wording is very similar to the recent IRS tender

"Associate the public address of each user from the stealth address or aggregated addresses and provide statistical probabilities." and this is similar to the ciphertrace statements on stealth addresses. (Which seems to show a poor understanding of what they even are)

possible this is from ciphertrace and/or chainalysis and/or Integra FEC

.merges

lol

moneromooo: I assume you did not have the crash again?

reviews for 6940 6944 6946 missing, afterwards we can do a new release

erf, it did crash.

Same place. I guess I'll upload a debug build.

hmm ok then we better not include it for now and do just manual banning + peer list improvements

the --ban-list PR does not have an approval yet monero-project/monero #6920

It does now.

ty

moneromooo: sorry, just to confirm, the missing (unsigned) casting on line 1443 is fine? monero-project/monero #6933

now we only have to PR against branch

I just tried a test C program: paste.debian.net/hidden/5720ae88

(so yes, fine)

Looks like randomx might set pages to write and exec at the same time: monero-project/monero #6957

I think that's the default, yes

Faster ?

toggling write on and off costs a lot, yes

OK, makes sense.

Looking at the soure, it's toggled by RANDOMX_FLAG_SECURE, which is 16, the reporter has that set.

oh, we actually set _SECURE by default

rx-slow-hash.c:285

Wait. UMASK disables.

can turn it off with MONERO_RANDOMX_UMASK, yes

_SECURE is on by default for verification, off for mining

vtnerd: please open 6949 6954 against release-v0.17 branch

moneromooo: ^ but with 6933 6939 6942 6943 (and anything else you want to include from your side)

xiphon: just 6960

I'll do 6942 later, it conflicts with at least one of the others. The other 3 are done.