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

Was this helpful?

  1. Lightning Network Tools
  2. Lightning Terminal

AutoOpen

AutoOpen helps node runners by opening new channels. It takes into account a variety of factors to improve the node’s position in the graph.

PreviousAutofeesNextLND Accounts

Last updated 6 months ago

Was this helpful?

AutoOpen and are available as part of Lightning Terminal’s Autopilot feature. When enabled, AutoOpen lets a node runner assign a budget, specify their time preference as well as define a minimum and maximum channel size. There is also the option to pass node pubkeys of preferred peers. It will then target a suitable point in time to batch open channels to save on fees.

New channels are selected to improve the node’s reach into the Lightning Network. To measure this reach, AutoOpen uses betweenness centrality, which calculates how many paths between any two other nodes in the network go through the node in question.

To use AutoOpen, and navigate to Autopilot under the Loop menu. This will let you enable AutoOpen, as well as set a budget, define the minimum and maximum channel sizes and specify preferred peers. The “speed” selector defines how sensitive AutoOpen should be to high onchain fees.

When enabling AutoOpen, you are sharing your node’s public key as well as your current and past channels. This allows AutoOpen to determine your position in the graph, as well as avoid peering you with nodes you previously had channels with, especially if these channels had to be force closed or still have enough liquidity.

When choosing channels, AutoOpen will look at your node’s channel size distribution and whether it overlaps with the channel size distribution of the new peer. As a small, not yet well connected node you may see channels being opened to well-connected nodes, while large nodes may see new peers that are smaller and less well connected. The channel size is determined using your node’s channel size, your peer’s channel sizes as well as your specified limits.

AutoOpen will look out for low fee next block targets (compared to long term block fee history) to decide when to open new channels. How sensitive you are to onchain fees can be set through the UI via the time preference configuration.

The new Autopilot feature will also set your initial channel fees for you. Using the fee rates of the new peer, AutoOpen will set the new adequate outbound fees for the new channel.

AutoOpen does not close channels. When broadly used, it is expected to further decentralize the Lightning Network graph by avoiding all nodes to be connected to the same large hubs at the center of the network, and instead increase betweenness-centrality by connecting nodes that do not yet share common peers.

Autofees
connect to Lightning Terminal
Configure your Autoopen budget in the Lightning Terminal interface