Log in by signing the verification message below using your node


Not sure how to sign a message?

Invalid signature!


Automated weekly channel simulation optimization report

*Results can take up to 24 hours to display after successfully paying subscription invoice

LightningNetwork+ swap optimization report

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 paths in the network.

Log in to access additional features in the Build-Your-Own-Chart and Channel Simulator tools

Upgrade your account to have us automate channel simulations to find optimal peers, optimal LN+ swaps, and to get unlimited access to all LNnodeInsight tools

Visuals

Simulators

Community tools


Also see node stats on

Current ranks

Historical ranks

Loading...

Summary stats

Step 2: enter or select pubkey/alias of up to 3 nodes with which to simulate adding or removing channels

Node centrality ranks

Previous run results


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.

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