private or changing IP address considerations about lnp-node HOT 1 CLOSED

I think the case with "not having a public ip" can be split into several variants, which have to be addressed in different ways:

1. For mobiles, where IP constantly changes, there is no "listening" mode for the LN(P) node(s). Instead, a user would HAVE to run a full LN node on his own server - like at some "home box" or in a private cloud like the one provided by @nodl. At @mycitadel we will be providing both of that options for LNP Node.
2. For hosts which are behind NAT, a special NAT traversal have to be used. While I am very interested in UDP hole punching, I still haven't a chance to do an implementation for it. So for now there are two main options:

• expose a node as a Tor hidden service - and with https://github.com/Cyphernet-DAO/rust-cyphernet the LNP Node will get full tor support in the next release (v0.10)
• use Bifrost network to "holepunch" NAT: if your local-behind-NAT node has a connection/channels with any other node a node interested in connecting your node can send a "RPC message" using sphinx routing specifying its IP address (or using an intermediary, if both nodes are behind NAT). It's like Tor Rendezvous protocol but over LN, without Tor :) BOLT-based LN nodes can't do that, but Bifrost can

Yes, we need to look what else can be added to LNP-BP invoices to get all of those options supported.

from lnp-node.