Develop your own data-driven Lightning Network insight
Discover network-wide statistics on nodes, interactively explore node local networks, measure the impact of opening or closing a channel, and identify potentially profitable opportunities
Log in to access additional features in the Build-Your-Own-Chart and Channel Simulator tools
Upgrade your account to get access to these features:
- Automated channel simulations with fee and capacity recommendations to find optimal peers
- Find optimal LightningNetwork+ swaps on-demand
- Automated capacity-fee simulator runs on your peers
- Measure the value of outbound liquidity to your peers
- Get unlimited access to all LNnodeInsight tools
Visuals
Simulators
Community tools
Log in by signing the verification message below using your node
Invalid signature!
WebLN action canceled
Something went wrong with the signature verification
Automated weekly channel simulation optimization report
* Committed node variable filters will be activated the next time the optimization engine runs
* Can be updated at any time but new submissions override previous ones
Filter settings saved!
LightningNetwork+ swap optimization report
Outbound liquidity value report
Current ranks
Historical ranks and node liquidity distribution
Summary stats
Step 2: enter or select pubkey/alias of up to 3 nodes with which to simulate adding or removing channels
*Existing peers of the node selected in Step 1 will only appear if 'Remove' is selected
Node centrality ranks
Previous run results
Capacity-Fee suggestion summary
Betweenness centrality
Betweeness centrality measures the number of shortest paths that pass through a node. A higher number of shortest paths a node has to any two other node in the network, the more likely they will be included in a route depending on the liquidity balance of each channel in the path.
Closeness/hopness centrality
Closeness/hopness centrality is a measure of how many hops it takes to reach any node on the network from a given node. The better the rank, the fewer the hops required to reach any and all nodes.
Eigenvector/hubness centrality
Eigenvector/hubness centrality measures influence of a given node in the network. Higher ranks imply a well-connected node that is linked to other well-connected nodes. A lower eigenvector centrality could also imply a new and/or underserved node in the network.
Maximum liquidity flow
Maximum flow is the highest amount of sats that can theoretically be pushed through a path if liquidity were 100% outbound. In reality, outbound across a path is likely 50% or less.
Passive rebalancing
This is a fee strategy that attempts to encourage higher liquidity volume and ideally bi-directional volume such that channel balances are passively maintained. The success of this strategy depends on multiple factors, and can often be difficult to achieve.
Active rebalancing
This is a fee strategy that typically observes less volume but recovers a higher proportion in fees that should cover the cost of rebalancing to maintain adequate channel balances.
Signing a message with your node's private keys
lnd
lncli signmessage "message to sign here"
c-lightning
lightning-cli signmessage "message to sign here"
eclair
eclair-cli signmessage --msg=$(echo -n 'message to sign here' | base64)
Ride The Lightning
Navigate to Lightning > Sign/Verify > Copy
Thunderhub
Navigate to Tools > Sign message > Copy
Outbound liquidity value
The value of outbound liquidity (i.e., your channel fees) is estimated by analysing the cost of potential payments in your node's neighborhood as well as to common payment destinations. Sustained volume at high fees imply high outbound value. High volume at relatively lower fees (i.e., lower percentile) suggests a given channel is underpriced, especially if liquidity moves in one direction only. Low volume at high fees suggests that a given channel may be overpriced. However, it may be worth maintaining higher fees at low volume depending on the size of a forwarded HTLC and the inbound & outbound channel pairs that forward the HTLC. Low volume at low fees suggests low demand through that channel. It may be worth considering reallocating liquidity elsewhere if low demand at low fees persists.