pull down to refresh

🛡️ Stealth Mode: Protecting your Bitcoin Privacy with Tor (Visual Guide)
57 sats \ 2 comments \ @coffee 17 Jul bitcoin_beginners

Hey Stackers,

We all know privacy is a fundamental right, especially when it comes to our sats. I wanted to share this infographic that perfectly illustrates the "Glass Safe" problem of using Bitcoin without Tor.

Key takeaways from the graphic:

  • The Exposure Risk: Lightweight wallets (like standard Electrum setups) can leak your IP and total net worth to random servers.
  • The Tor Shield: Tor masks your who (IP/Location) but not always your what (wallet activity).
  • Physical Security: Preventing the dreaded "$5 Wrench Attack" by decoupling your wealth from your physical address.
  • The Gold Standard: Running your own Bitcoin Core full node over Tor is still the ultimate way to stay private.

I think this is a great resource to share with newer bitcoiners who might not understand why IP privacy matters.

What is your current setup? Are you running your own node over Tor, or using a lightweight wallet with Orbot/Tor Browser? Let me know your thoughts!

write
compose
related posts
1 sat \ 1 reply \ @Murch 17 Jul

Running Tor is a reasonable recommendation, but I can’t help but feel that the concern here is misrepresented.

Determining the originating node of a transaction requires operating a large number of nodes to surveil transaction announcements from as many peers as possible. Submitting a transaction via -privatebroadcast or even through a block explorers interface already changes the calculus significantly. Even after a transaction is associated with an IP address, this does not leak the entire wallet balance unless the surveillant additionally does extensive graph analysis and the wallet even has sufficient footprint to let a surveillant make the connections.

Also, if you are looking for another angle on this, running a non-Tor Lightning node would match your description better.

reply
0 sats \ 0 replies \ @coffee OP 18 Jul freebie
Running Tor is a reasonable recommendation, but I can’t help but feel that the concern here is misrepresented.

Determining the originating node of a transaction requires operating a large number of nodes to surveil transaction announcements from as many peers as possible. Submitting a transaction via -privatebroadcast or even through a block explorers interface already changes the calculus significantly. Even after a transaction is associated with an IP address, this does not leak the entire wallet balance unless the surveillant additionally does extensive graph analysis and the wallet even has sufficient footprint to let a surveillant make the connections.

Also, if you are looking for another angle on this, running a non-Tor Lightning node would match your description better.

I learned a lot. Thank you.