02:27:53 Sindy: https://mrelay.p2pool.observer/m/matrix.angled.rip/HWvbmgylInuoaMZJoabBdisl.png (Screenshot_20251009_192721.png) 02:28:10 most recent block even displayed is p2pool from 2 days ago 02:28:24 definitely very broken 02:28:31 no idea why most of the names aren't showing up though 02:57:14 Is there any ztrash tx vs fcmp++ txs size/efficiency information somewhere? 03:01:14 @elongated:matrix.org: we should compile something. especially regarding transaction batch verification time. 14:32:43 syncing monerod, what does this error mean? `2025-10-10 14:31:25.617 W Invalid DNSSEC TXT record signature for updates.moneropulse.org: validation failure : no DNSSEC records from 9.9.9.9 for DS updates.moneropulse.org. while building chain of trust` 14:33:10 should I change my dns nameserver? 14:34:14 quad9 did not give DNSSEC records 14:35:18 what dns would give DNSSEC records? 14:35:50 on getmonero it says I can use 1.1.1.1 or 8.8.8.8, maybe I'll try it 14:36:04 yeah i tried dig 14:36:13 it seems like quad9 doesn't return any DS records 14:36:22 but 1.1.1.1 does 14:36:58 8.8.8.8 doesn't though, it even brings up this error "Invalid denial of existence of updates.moneropulse.org/ds" 14:37:26 maybe MITM'd or some shit 14:39:41 honestly i cannot tell if this is an actual result from the DNS server (and they're intentionally tampering with it) or if it's my ISP tampering with the results to omit DNSSEC 14:41:43 I think it DNS MITM should be rare 14:42:07 it's maybe used targeting individuals as far as I understand how it works 14:42:23 it's used to target specific domains 14:42:29 nontheless DNS over TLS is a thing 14:42:42 my PR for DNS-over-TLS should be reviewed :( 14:43:24 I just set my router to use it then point everything at my router for DNS 14:44:51 the resolver library that monerod uses already has built-in DNS-over-TLS support 17:52:11 16:41:43 I think it DNS MITM should be rare 17:52:23 ISPs or some routers override any plaintext DNS with their own 17:52:28 no matter which port it runs on 17:52:30 ^ 17:52:32 server* 17:52:37 as long as it's in port 53* 17:52:38 DNS MITM is much more common than you think 17:53:00 usually they do this for caching, but they get stuff wrong 17:53:06 (or blocking) 17:53:08 oh yeah "caching" 17:53:22 some ISPs have shit peerings :) 17:53:41 they do that to improve latency, instead of 4s+ you end up with just 2s latency 17:53:48 they did that in the worst way that broke the DNS standard 17:53:56 which led to many complaints 17:59:55 But wouldn't such MITM be invalidated by non-matching certificates?.. 18:00:19 I know of a cell carrier that inserted ads into HTTP, but bare HTTP is rare now, so never seen it. 18:13:27 BlueyHealer: mitm doesn't need to change the records 18:13:34 just for example not return records for domains 18:13:38 or not do DNSSEC etc. 18:34:45 "Another problem is that some mail carriers might get sly and try to find out who is delivering what letters. The Fluorine Fermi update changes how letters are sent and who they are sent to, which makes it extremely hard for spies to trace the trail. This helps the Monero mail service escape these cunning carriers." 18:34:52 This gem is from here: https://www.cryptopolitan.com/monero-releases-fluorine-fermi-update/ 18:36:43 lolol 18:37:16 pigeon2peer protocol 18:42:41 64bit speedup (vs 32 bit) for wallet scanning only. There's a patch marked as draft that speeds up sync time considerably, but I've left it as draft because technically it increases chances of chain split. Chances are low, but possible. > <@ravfx:xmr.mx> What is that supercop thing? Required or no to build monerod? 18:43:39 Could we merge it and use it just for wallets ? 18:44:01 Do you have a link to the PR? I might apply it to the wallet we are Building 18:44:31 Worst case is that the wallet gets stuck syncing ? 18:47:10 <17lifers:mikuplushfarm.ovh> @rbrunner7: well, that same article also suggests this 18:47:20 <17lifers:mikuplushfarm.ovh> https://mrelay.p2pool.observer/m/mikuplushfarm.ovh/XksOfIuYyDdVDVVPmmukHPPB.png (image.png) 18:47:50 Er ... I think Supercop is used for wallet scanning - just not for syning blocks 18:48:00 @rbrunner7: ELI5 prompt 18:50:27 @binarybaron:matrix.org: Its been used in wallets for years. The new PR is just for curve order checks on tx keys. It's really high in profiles when syncing 18:54:17 Carrot will shift to x25519 which has speedups for arm, whereas the supercop 64bit assembly is x86-64 only. The supercop project has a new neon (arm) assembly which would help with pre-carrot scanning, but last I checked that code is still marked as unverified 19:40:45 DataHoarder, I kinda don't associate it with MITM then... Like, it's what my ISP is already doing by blocking Twitter/Facebook/etc. 19:41:17 it's MITM, just not trying to change things to a different endpoint 19:41:24 literally man in the middle 19:41:48 even a passive MITM is considered that, and if blocking/overriding is done, that's active, maybe not malicious 19:42:18 MITM being normalized doesn't mean it's not man in the middle :D 19:42:42 I just think of "redirecting traffic elsewhere" or "trying to read the traffic" rather than "terminating the traffic", since, y'know, there is no "middle" to be in now. 19:48:21 what do you guys recommend to swap ltc to xmr with mininal fees? 19:54:24 <321bob321> Basicswap 20:14:22 https://x.com/monero/status/1834292929877180697 20:14:49 Except there is an issue with outgoing view keys 20:15:07 https://github.com/hbs/MoneroMisc/blob/master/CARROT-discussion.md 20:15:42 Please give us a choice 20:18:42 Why not better privacy by default? 20:42:19 Privacy is normal 23:22:35 What the one mean "Unable to send transaction(s) via Dandelion++ stem"? 23:22:53 I get it from time to time on one of my node, since Qubic afaik, I don't remember seeing 23:49:04 ravfx: do you use tx-proxy ?