bolt.observer
  • bolt.observer
    • LiquidOps
      • Getting started
      • Setup LiquidOps
        • Api based - pull
        • Agent based - push
      • Node and liquidity automation
      • Integrations
        • Triggers
          • TCP connectivity
          • Tor connectivity
          • Lightning Connectivity
          • Sync to chain
          • Sync to graph
          • Onchain balance
          • Channel balance
          • Node balance
          • Channel open
          • Channel close
          • Inactivity
        • Actions
          • Send a notification
          • Perform Auto Swaps
            • Use case: auto swap-out for a 2M sats channel
            • Use case: auto swap-out for a 50M sats channel
            • Use case: auto swap-in
    • Explorer
    • Integration configuration
      • Discord
      • Email
      • Nostr
      • Opsgenie
      • PagerDuty
      • Slack
      • Telegram
    • Reachability
    • Guides
      • Explorer: advanced search
      • Create a workflow with auto swaps
      • Agent configuration: auto swaps
      • Setup LiquidOps on Voltage nodes (API based - pull)
      • Setup LiquidOps on Voltage nodes (agent based - push)
Powered by GitBook
On this page
  • Example 1: Minimum channel size limit
  • Example 2: Maximum channel size limit
  • Example 3: Capacity, latency, position, Betweenness centrality
  1. bolt.observer
  2. Guides

Explorer: advanced search

Advanced search relies on public and proprietary data.

PreviousGuidesNextCreate a workflow with auto swaps

Last updated 1 year ago

has been designed to assist you in exploring the Lightning Network by allowing highly granular searchese. With a wide range of search criteria, it provides you with the ability to delve deep into the network and discover nodes that align with your needs.

The entire list of search criteria can be found .

Example 1: Minimum channel size limit

In some cases, larger lightning nodes impose size limits on incoming channels. If you are interested in opening a channel with highly connected nodes, Explorer provides you with valuable information beforehand, allowing you to assess the risk of potential rejection before proceeding. This ensures that you can make an informed decision and minimize the chances of facing channel opening rejections.

Result

This is a screenshot of all the nodes whose minimum channel size limit is lower or equal to 1,000,000 sats.

Example 2: Maximum channel size limit

The same principles apply for Maximum channel size limit

Example 3: Capacity, latency, position, Betweenness centrality

Find nodes with the following criteria:

  • capacity > 1BTC

  • latency < 1500 ms

  • number of hops = exactly at 2 hops away from your node

  • 50 < Betweenness Centrality < 500

Results

Explorer
here