Oddbean new post about | logout
 > And the privacy implications are not as detrimental to Monero users for using a public node as they are for Bitcoin

Do you understand how BIP158 filters work? 
 Monero/Samourai/Red guys always just throw around podcast buzzwords they have no actual understanding of. No use argumenting, they will just throw more buzzwords. 
 The Joe-Roganization of technical discussion? :-) 
 Not sure about Joe Rogan, but the red guys are probably more offensive, as if you insult them directly when you introduce them to the concept of technical tradeoffs using their thing as example. 
 What "buzzwords" were said? 
 I don't know how Cake and Silentium work exactly. There is no standard yet for light clients, so claiming that non-standard experimental software is slow, is just not that relevant. Let's wait and see. 
 Isn't BIP158 for querying a node without exposing all your addresses? I don't think it hides sender/amount/receiver from the public node when you broadcast the transaction does it?

Correct me if I'm wrong 
 Transaction broadcast is a completely different issue than scanning. One shot Tor connections are a nice potential way to deal with that.

Dandelion would be nicer, but so far nobody has implemented it in a DoS resistant matter. Part of the problem there is that the Bitcoin Core mempool is already extremely complicated, though I'm still hopeful that will improve, e.g. with cluster mempool.
https://github.com/bitcoin/bitcoin/pull/29415 
 I mean it is still pretty relevant to the topic of using public nodes. Unless you're someone who plans on never broadcasting transactions.

But looks cool