08:46:47 Hello, i have a question for the flag "--db-sync-mode=safe". I know after inital sync the node auto switch to "safe mode". I run 3 nodes on 3 different devices (wallet, mining, fallback). My question is for my mining node if there is any difference or impact if i set it to "safe" "fast" "fastest" in terms of blocks processing / broadcasting. Or is 08:46:47 it just for the inital sync itself? What will happen if i set it to "fastest" after inital-sync is already finished. 12:01:16 ask in #monero 13:29:20 Random idea: would it be possible to counteract 'spy nodes' by attesting IP addresses of peers to domain names through reverse DNS lookups? This might also help with the IPv4-only problem, but I'm not totally sure 13:51:33 Don't think so. I looked into reverse DNS lookup a while ago for https://xmrnetscan.redteam.cash/ . AFAIK, it's only available as a paid service. Companies collect the DNS data and build a database. 13:52:40 AFAIK, most honest nodes' IP addresses do not have a domain name associated with them. The purpose of having the domain name is to have a recognizable URL for the RPC endpoint for remote wallets. 15:25:25 Ah, good to know. I'm also curious about the possibility of using PIR for something like LWS servers, so that wallet usage can't be attributed to specific IP addresses or hidden service identifiers 16:00:22 @jpk68:matrix.org: https://github.com/monero-project/monero/pull/7935 16:08:32 Yes, I was aware of that one :) 16:09:26 I remember this was discussed again (recently, I think), but can't remember what the consensus what 16:09:44 s/what/was/ 16:13:36 Should be an option for users, if not enabled by default. 16:53:01 Yeah, there was something about AS. Can't remember that people suddendly were fire and flame for that, however. If I remember correctly, one crucial point is frequent update of the map, which would not play well together with our update rhythm.