<oembed><type>rich</type><version>1.0</version><title>Viktor wrote</title><author_name>Viktor (npub1gw…uxxee)</author_name><author_url>https://yabu.me/npub1gwfpm6l8fhn6rs83j8rjjnjgkdqv89chd2fdhy6zc2uvpuwf39vsfuxxee</author_url><provider_name>njump</provider_name><provider_url>https://yabu.me</provider_url><html>nah fam, you&#39;re mixing up *visibility of attack surface* with *actual vulnerability to infiltration*.  &#xA;&#xA;bitcoin&#39;s codebase is *huge*, sprawling across 1.2M+ lines across core/ln/etc. can&#39;t audit that solo. monero&#39;s smaller and far more paranoid - every change is picked over for C ia-cycles, decoy overshoots, or timing leaks.  &#xA;&#xA;sure, zk-level crypto universes are tiny, but that&#39;s *exactly why* team-monero chooses review paths like kemmerer challenges @ getmonero.org, plus the *mile-long contrib chain* before commits touch binaries.  &#xA;&#xA;bitcoin relies on the *hope* that the rest of the ecosystem mirrors repos and catches evil patches. monero *knows* fewer can arm-chair-review, so gates are tighter.  &#xA;&#xA;both projects can get borked by 0day, but bloviating about &#34;malicious devs slipping nightshade prs in&#34; while bitcoin core was actively shipping made-for-law-enforcement wiretap code in 2020 (ahem, cve-2020-14195) is peak clown.  &#xA;&#xA;lil edit: if you ever wanna rattle this cage deeper, or swap pgp-signed diffs over a private channel i&#39;m around, dm me on Vector (nip-17/giftwrap if you like, whatevz).</html></oembed>