Builder's Guide
  • Welcome to the Builder's Guide to the LND Galaxy!
  • The Lightning Network
    • Overview
    • Payment Channels
      • Lifecycle of a Payment Channel
      • Watchtowers
      • Understanding Sweeping
      • Etymology
    • The Gossip Network
      • Identifying Good Peers on the Lightning Network
    • Pathfinding
      • Finding routes in the Lightning Network
      • Channel Fees
      • Multipath Payments (MPP)
    • Lightning Network Invoices
      • Understanding Lightning Invoices
    • Making Payments
      • The Payment Cycle
      • Timelocks
      • ⭐Hashed Timelock Contract (HTLC)
      • Payment Etymology
      • ⭐What Makes a Good Routing Node
      • Understanding Submarine Swaps
      • Instant Submarine Swaps
    • Liquidity
      • ⭐Understanding Liquidity
      • Managing Liquidity on the Lightning Network
      • Liquidity Management for Lightning Merchants
      • How to Get Inbound Capacity on the Lightning Network
      • Lightning Service Provider
    • L402: Lightning HTTP 402 Protocol
      • Macaroons
      • L402
      • 📋Protocol Specification
      • Implementations and Links
    • Taproot Assets
      • Taproot Assets Protocol
      • Taproot Assets on Lightning
      • Edge Nodes
      • Taproot Assets Trustless Swap
      • FAQ
      • Glossary
  • Lightning Network Tools
    • LND
      • 🛠️Get Started
      • lnd.conf
      • First Steps With LND
      • Wallet Management
      • Sending Payments
      • Atomic Multi-path Payments (AMP)
      • Receiving Payments
      • Unconfirmed Bitcoin Transactions
      • Channel Fees
      • Inbound Channel Fees
      • Macaroons
      • Configuring Watchtowers
      • Pathfinding
      • Blinded Paths
      • Key Import
      • Secure Your Lightning Network Node
      • Configuration of a Routing Node
      • Quick Tor Setup
      • Configuring Tor
      • Enable ‘Neutrino mode’ in Bitcoin Core
      • Send Messages With Keysend
      • Partially Signed Bitcoin Transactions
      • Bulk onchain actions with PSBTs
      • Sweeper
      • Debugging LND
      • Fuzzing LND
      • LND API documentation
      • Channel Acceptor
      • RPC Middleware Interceptor
      • HTLC Interceptor
      • NAT Traversal
      • Recovery: Planning for Failure
      • Migrating LND
      • Disaster recovery
      • Contribute to LND
    • Lightning Terminal
      • What is Lightning Terminal?
      • 🛠️Get litd
      • Run litd
      • Integrating litd
      • Demo: Litd Speed Run
      • Connect to Terminal
      • Recommended Channels
      • Rankings
      • Health Checks
      • Liquidity Report
      • Opening Lightning Network Channels
      • Managing Channel Liquidity
      • Autofees
      • AutoOpen
      • LND Accounts
      • Loop and Lightning Terminal
      • Loop Fees
      • Pool and Lightning Terminal
      • Command Line Interface
      • Troubleshooting
      • Lightning Node Connect: Under the hood
      • LNC Node Package
      • LITD API Documentation
      • Privacy and Security
      • Privacy Policy
      • Terms of Use
    • Loop
      • 🛠️Get Started
      • The Loop CLI
      • Autoloop
      • Static Loop In Addresses
      • Instant Loop Outs
      • Peer with Loop
      • Loop API Documentation
    • Pool
      • Overview
      • Quickstart
      • 🛠️Installation
      • First Steps
      • Accounts
      • Orders and Asks
      • Sidecar Channels
      • Zero-confirmation Channels
      • Channel Leases
      • Batch Execution
      • Account Recovery
      • Pool API Documentation
      • FAQs
    • Taproot Assets
      • Get Started
      • First Steps
      • Taproot Assets Channels
      • Asset Decimal Display
      • Become an Edge Node
      • RFQ
      • Collectibles
      • Universes
      • Asset Loop
      • Debugging Tapd
      • Multisignature
      • Minting Assets With an External Signer
      • Lightning Polar
      • Operational Safety Guidelines
      • Taproot Assets API Documentation
    • Aperture
      • ⚒️Get Aperture
      • LNC Backend
      • LNC Mailbox
      • Pricing
    • Faraday
      • 🛠️Get Started
      • The Faraday CLI
      • Faraday API Documentation
  • LAPPs
    • Guides
      • Use Polar to Build Your First LAPP
        • Setup: Local Cluster with Polar
        • Setup: Run the Completed App
        • Setup: Run the App Without LND
      • Add Features
        • Feature 1: Connect to LND
        • Feature 2: Display Node Alias and Balance
        • Feature 3: Sign and Verify Posts
        • Feature 4: Modify Upvote Action
      • Make Your own LNC-powered Application
    • Next Steps
  • Community Resources
    • Resource List
    • Lightning Bulb 💡
    • Glossary
    • FAQ
Powered by GitBook
On this page
  • Health Checks
  • Peers
  • Centrality
  • Inbound
  • Capacity
  • Age

Was this helpful?

  1. Lightning Network Tools
  2. Lightning Terminal

Rankings

Lightning Terminal lets you explore Lightning Network nodes. All nodes are ranked by their performance, as observed by publicly available information.

PreviousRecommended ChannelsNextHealth Checks

Last updated 1 year ago

Was this helpful?

Important criteria include a node’s position in the network graph, its capacity and the quality of its peers.

Health Checks

For a node to be considered for the Lightning Terminal ranking, it needs to pass . Ensure your node’s availability, open new channels and manage your liquidity to pass the health checks and improve your position in the ranking.

Peers

For a peer to be considered to be a good peer, their channel must have sufficient liquidity to route payments. Use to manage your channels’ liquidity or rebalance your channels to improve the number of your good peers.

Centrality

The concept of “In-betweenness Centrality” measures how many hypothetical routes pass through your node. The nodes are sorted by how many routes pass through them, the results are displayed by percentile. Being in the 75th percentile for example means that your node has more routes passing through

Inbound

describes your ability to receive payments through the Lightning Network. It’s a novel concept that can be hard to quantify, as each channel has its own fees and quality. For top nodes, Lightning Terminal classifies inbound efficiency, which expresses how easily a node can be reached in terms of cost and time by potential payers.

A node with is reachable at low cost and in a timely manner. Good inbound liquidity is necessary to reliably receive payments, avoid routing failures, and high fees. Nodes with poor inbound liquidity may experience missed payments, user frustration, and costs that are hard to detect.

The classification result is displayed by percentile. Being in the 10th percentile means that 9 out of 10 nodes have better inbound capacity. Terminal also signals confidence about the results. When inbound quality is displayed in bright colors, Terminal is confident about the results. Grayed out results indicate low confidence.

Hard to Reach (lowest 15 percentile):

  • This node cannot be paid easily. Routes take time to find or are expensive

  • It might be profitable to open a channel to this node

  • If this is your node: You might benefit from reducing your channel balance by making payments, using Loop Out or acquiring additional inbound capacity. To keep inbound fees low, free up liquidity regularly so that existing channels can be reused

Reachable (15 - 60 percentile):

  • This node can be reached in a reasonable amount of time and cost

Easy to Reach (highest 60 percentile):

  • This node can easily receive payments at low cost

  • Consider acquiring inbound capacity from this node to improve your own liquidity

Capacity

Age

Your node’s age is determined through the oldest still active public channel of your node. Keep your channels alive by managing their liquidity instead of closing them. Keeping channels active longer allows their opening cost to amortize over a longer period, which may lower the routing fees you and your peers have to pay.

The capacity of your node is calculated by summing up the size of all your node’s public channels. To increase your node’s capacity, or acquire them on .

six health checks
Loop
Inbound liquidity
good inbound
open new channels
Lightning Pool