LND

• Name: LND
• URL: https://docs.lightning.engineering/lightning-network-tools/lnd
• Category: Bitcoin Lightning node implementation / wallet-and-node control plane / Lightning API infrastructure
• Tags: bitcoin-ecosystem
• Summary: LND is the Lightning node-and-API substrate. The useful point is the whole operator surface — channel state, routing, macaroons, watchtowers, PSBTs, recovery, and app-facing APIs — not the fact that it is a daemon binary.
• What it does:
  • Runs a full Lightning node implementation with support for opening and closing channels, maintaining channel state, validating the network graph, forwarding payments, and sending onion-routed Lightning payments
  • Supports multiple Bitcoin-chain backends including bitcoind, btcd, and the neutrino light-client path
  • Exposes two primary app-facing RPC interfaces: HTTP REST and gRPC
  • Provides a large operator docs surface covering wallet management, payment flows, channel fees, macaroons, watchtowers, PSBT handling, Tor, recovery planning, and disaster recovery
  • Includes automatic channel-management functionality through its autopilot subsystem
  • Publishes generated API docs and a broader developer-guide corpus for application builders and node operators
• Key claims:
  • The official README says LND is “a complete implementation of a Lightning Network node” and lists capabilities including channel creation/closure, channel-state management, graph validation, pathfinding, forwarding, onion payments, fee updates, and automatic channel management
  • The README says LND fully conforms to core Lightning BOLTs including BOLT 1/2/3/4/5/7/8/9/10/11, which is a strong clue that it is intended as foundational network infrastructure rather than an app-specific fork
  • The README says the daemon was designed to be developer friendly and exports two primary RPC interfaces: an HTTP REST API and a gRPC service
  • The official docs index exposes a much broader operational surface than the README alone, including pages for lnd.conf, wallet management, AMP, receiving payments, PSBTs, unconfirmed Bitcoin transactions, macaroons, watchtowers, key import, node hardening, Tor, debugging, recovery planning, and disaster recovery
  • The README warns that mainnet operators should follow explicit operational safety guidelines and still describes LND as beta software for safety purposes, which reinforces that running it is an operational discipline rather than a passive library install
  • The docs page links directly to generated LND API documentation, showing that LND is meant to be integrated programmatically by external applications and services
• Whitepaper: No canonical standalone LND whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the official README and the Lightning Labs LND documentation/API surfaces; see ../whitepapers/lnd-primary-sources-2026-05-02.md.
• Sources:
  • https://docs.lightning.engineering/lightning-network-tools/lnd
  • https://github.com/lightningnetwork/lnd
  • https://raw.githubusercontent.com/lightningnetwork/lnd/master/README.md
  • https://api.lightning.community/

Internal linkages

• Canonical implementation contrasts: core-lightning and eclair

• Major managed layer built on the same node-and-API substrate: greenlight

• Last reviewed: 2026-05-29 UTC