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