Appearance
LNC
LNC is how LN Advisor connects the browser to your node.
In practice, it gives the app a live session to LND without asking you to expose the node directly to the public internet.
What it does here
LN Advisor uses LNC to:
- pair the browser with your node
- read node data directly from the frontend
- keep the node as the source of truth for the app
- avoid building a separate node-specific backend just to fetch channel and routing data
Connection flow in the app
There are two frontend states:
- first connection: enter the LNC pairing phrase and a password
- returning session: enter the password for the saved pairing
On the first successful connection, the browser stores the local session state protected by the password you chose. After that, LN Advisor only needs the password to reopen the saved session.
What you need before connecting
Before you use LN Advisor with a real node, you need:
- an LND node
- Lightning Terminal /
litd - an LNC pairing phrase generated from that node
The pairing phrase is what the browser uses to establish the initial trust relationship with your node.
Data read through LNC
LN Advisor uses the active LNC session for:
getInfolistChannelslistPeersdescribeGraphforwardingHistoryqueryMissionControlgetNodeMetrics
Where LN Advisor uses it
Channel Fees
- reads channel state, fee context, forwarding history, and mission control data
Opening Recommendations
- reads channels, peers, graph data, mission control, and node metrics
Node Analysis
- reads graph, forwarding, mission control, and node metrics directly for inspection
Why LN Advisor uses LNC
LNC is a good fit for this app because:
- the browser can read live node state directly
- the app can prepare recommendation inputs locally before send
- the operator can inspect the request boundary in the UI
- the same session supports both direct analysis pages and recommendation pages
Official LNC docs
See Private Pipeline for how LN Advisor uses that session before sending recommendation requests.