Lightning Loop primary sources — 2026-05-02

Project status in this pass

• No canonical standalone whitepaper or litepaper surfaced.
• The clearest current source of truth is the official Loop docs plus the public lightninglabs/loop repository.
• The materials consistently frame Loop as non-custodial Lightning liquidity infrastructure for lnd operators rather than as a generic bridge or consumer wallet.

Primary-source snapshots

1) Loop overview docs

• URL: https://docs.lightning.engineering/lightning-network-tools/loop.md
• Key excerpt:
  • The docs say Loop lets users make a Lightning transaction to an onchain Bitcoin address (Loop Out) or send onchain bitcoin directly into a Lightning channel (Loop In).
  • They say Loop helps manage channel liquidity, uses non-custodial submarine swaps, batches Loop Out transactions to save fees, and uses L402s for authentication.
  • The overview also points directly to Autoloop, static Loop In addresses, instant Loop Outs, and API docs.

2) Main repository README

• URL: https://github.com/lightninglabs/loop
• Key excerpt:
  • The README calls Loop “a non-custodial off/on chain bridge” and highlights automated channel balancing, privacy-forward swaps, instant Loop Outs, static reusable addresses for Loop Ins, and progress monitoring.
  • It says loopd connects to lnd, that Loop requires lnd to be built with the relevant subservers, and that the daemon exposes gRPC and REST APIs secured with TLS and macaroon authentication.
  • This makes clear that Loop is a serious node-side service layer, not just a website flow.

3) Get-started docs

• URL: https://docs.lightning.engineering/lightning-network-tools/loop/get-started.md
• Key excerpt:
  • The getting-started guide says Loop comes bundled with Lightning Terminal (litd) but can also run directly from standalone binaries or source.
  • It requires an existing lnd setup and documents remote loopd deployments with copied macaroons and TLS certs.
  • This reinforces that Loop is part of a broader Lightning operator stack.

4) Autoloop docs

• URL: https://docs.lightning.engineering/lightning-network-tools/loop/autoloop.md
• Key excerpt:
  • The Autoloop docs say operators can enable automatic Loop In or Loop Out dispatch based on node-, peer-, or channel-level liquidity thresholds.
  • They document configurable fee ceilings, sweep confirmation targets, miner-fee caps, budget amounts, refresh periods, and dispatch limits.
  • That combination is strong evidence that Loop is best viewed as liquidity-management control plane infrastructure.

5) Static Loop In address docs

• URL: https://docs.lightning.engineering/lightning-network-tools/loop/static-loop-in-addresses.md
• Key excerpt:
  • The docs say static Loop In addresses are two-of-two taproot multisig timeout addresses where one key is held by the user and one by Loop.
  • They claim users can pre-deposit funds, withdraw before expiry, and later deploy those UTXOs into Lightning quickly without sacrificing the trustless swap model.
  • They also warn that the L402 token is needed to identify the user to the service and that losing it may force timeout-based recovery, which is an important operational caveat.

Working conclusion

Lightning Loop is best cataloged as a non-custodial Lightning liquidity and rebalancing control plane built around submarine swaps, operator automation, and lnd integration. The decisive evidence in this pass was the repeated combination of Loop In/Out liquidity flows, AutoLoop policy controls, static deposit addresses, and authenticated daemon/API surfaces for node operators.