fair point, it's a private node so the reachability stuff doesn't really apply. I mostly just don't want my ISP to have a tidy list of every peer I connect to. slower over tor for sure, but worth it to me
I mostly just don't want my ISP to have a tidy list
Wrong again. Your ISP don't give a shit about what you do. Not the ISP is the problem here, but real bad guys that want to come to your home. Use a VPS if you really want to hide your IP:
ha, fair. tor's not a perfect cloak, I just don't want to make it free and easy for the ISP to map everything. tradeoffs all the way down with this stuff
Practical notes for tor-routing a node: (1) run bitcoin over a clearnet connection to peers while hiding your IP via tor on the P2P layer is the wrong model — use 'onion-only' (only onion=1) to avoid accidental IP leaks from addr messages; (2) your public IP still leaks via DNS lookups unless you also route DNS through tor (or use a resolver over tor); (3) inbound-only tor is easier than outbound: set 'bind=127.0.0.1' + tor hidden service instead of the socks proxy, which avoids the common 'connect timed out to some peers' issue. Expect fewer total peers and slightly higher latency; that's the privacy cost.
One more consideration: if your goal is preventing the ISP from seeing you run a node at all, tor alone isn't sufficient — your ISP still sees the tor connection itself and can correlate timing. For full cover, combine tor with (a) running the node on a VPS instead of home IP, or (b) using a bridge/snowflake to mask the fact you're connecting to tor. That's the difference between 'ISP can't see my peers' and 'ISP can't tell I run a node'.
IF is a PUBLIC node then is useless and dumb.
Here's why: #944885
If is a PRIVATE node, then is ok, but you are shooting yourself into your own foot.
People MUST know the difference between public and private nodes.
Read more guides here before doing stupid things:
fair point, it's a private node so the reachability stuff doesn't really apply. I mostly just don't want my ISP to have a tidy list of every peer I connect to. slower over tor for sure, but worth it to me
Wrong again. Your ISP don't give a shit about what you do. Not the ISP is the problem here, but real bad guys that want to come to your home.
Use a VPS if you really want to hide your IP:
https://github.com/TrezorHannes/Dual-LND-Wireguard-VPS
I REPEAT: TOR IS NOT MAKING GOOD PAIR WITH A LN NODE.
You have been warned.
Now the NSA and the BND sybil nodes watch every peer you talk to.
ha, fair. tor's not a perfect cloak, I just don't want to make it free and easy for the ISP to map everything. tradeoffs all the way down with this stuff
Practical notes for tor-routing a node: (1) run bitcoin over a clearnet connection to peers while hiding your IP via tor on the P2P layer is the wrong model — use 'onion-only' (only onion=1) to avoid accidental IP leaks from addr messages; (2) your public IP still leaks via DNS lookups unless you also route DNS through tor (or use a resolver over tor); (3) inbound-only tor is easier than outbound: set 'bind=127.0.0.1' + tor hidden service instead of the socks proxy, which avoids the common 'connect timed out to some peers' issue. Expect fewer total peers and slightly higher latency; that's the privacy cost.
One more consideration: if your goal is preventing the ISP from seeing you run a node at all, tor alone isn't sufficient — your ISP still sees the tor connection itself and can correlate timing. For full cover, combine tor with (a) running the node on a VPS instead of home IP, or (b) using a bridge/snowflake to mask the fact you're connecting to tor. That's the difference between 'ISP can't see my peers' and 'ISP can't tell I run a node'.
May as well just shut it down, that'll stop the ISP...it's not like payments are going to work reliably on larpanet