In this guide, we will walk you through the best practices for maintaining a mainnet lnd Lightning Network node. lnd is a golang implementation of the Lightning Network Specification, maintained by Lightning Labs which fully conforms to the Lightning Network Specification (BOLTS).

Hopefully if you are reading this, you have already completed our Build a Lapp guide and our Installation guide.

This guide assumes some basic knowledge of how Bitcoin and the Lightning Network operate. We recommend understanding of the following concepts before proceeding with the guide, as some foundational concepts will ease the learning curve.

A note on Feature Bits:

To allow easy upgrades to the network, nodes advertise the features that they support so that there are no misunderstandings when trying to communicate. These feature bits are advertised in two places:

  • Node announcements: broadcast to the entire network, indicating the features that a node supports and those which it requires. These feature bits can be viewed using the DescribeGraph API call.

  • Invoices: to allow updates to the way in which we make payments, invoices also include feature bits, so that payers know how the invoice can be paid. These feature bits are largely internally managed by lnd, so you do not need to worry about them.

The feature bits that a node supports determines the way in which your node can interact with it; on a node-level, it determines the channel types you can open, and on an invoice-level, it determines the ways in which you can pay that invoice. If your implementation depends on a feature in this guide that notes that it needs a specific feature bit, be sure to check that the nodes you interact with support the feature bits you need!