pull down to refresh

sure, not too much pain if you are good with routing tables and firewalls. I consulted gpt the last time I did it. opening ports for connections from the outside world takes balls and patience.
private channels are just the ones not announced via gossip. so the sender does not know how to reach your node and you need routing hints in your invoices.
You don’t have to. Just add a bit of firewalling, use IPv6 exclusively, and give every user a strict IPv6‑only VPN tunnel dedicated to the Bitcoin/Lightning protocol. Maybe a bit more – you could use WireGuard, but roll it out with a Tailscale‑style configuration.
reply
We could also take a domain, set the FQDN, and use IPv6 SLAAC at the end—rotating the IPv6 addresses according to security requirements if that’s feasible.
reply
ok, but if you know so much, why did you start this thread?
reply
I was looking for something like that.
reply