Oddbean new post about | logout
▲ ▼
SaberhagenTheNameless | 15 days ago (raw) | root | parent | reply | flag 
 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
▲ ▼
provoost | 15 days ago (raw) | root | parent | reply | flag +2 
 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
▲ ▼
SaberhagenTheNameless | 15 days ago (raw) | root | parent | reply | flag 
 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