Bitcoin Lightning Payments: Channels, Routing, and Tradeoffs
Summary
The document explains Lightning as a Bitcoin layer that moves payments through off-chain channels, with channel opening and closing settled on the base chain. It contrasts this approach with ordinary on-chain transfers: Lightning can support faster, lower-cost frequent payments, including small payments, while channel capacity limits payment size and routing liquidity can affect whether a payment succeeds. It also describes the use of Lightning invoices and compatible wallets, and notes that an exchange can provide Lightning deposits and withdrawals.
The material recommends Lightning for frequent small-to-medium transfers and on-chain settlement for large, infrequent transfers where simplicity matters more. For self-custody, it highlights channel-management complexity and the need to monitor channels or use a watchtower against malicious closures; exchange custody reduces that operational burden but changes who controls the funds. The document gives indicative comparisons and a rough large-transfer guideline, but fees, capacity, and speed depend on network conditions and service limits. Its exchange-specific details and 2026 framing are not independent evidence of reliability or performance.
Key ideas
- Lightning routes Bitcoin payments through channels and settles channel activity on-chain when channels open or close.
- Channel capacity and routing liquidity constrain payment size and reliability.
- Lightning is presented as suitable for frequent small-to-medium payments, while on-chain transfers suit larger infrequent transfers.
- Self-custody requires channel monitoring and management; exchange custody shifts that operational responsibility.
- Fees, transfer limits, and timing vary with network conditions and provider rules.
Tags
This summary was written by Stratmill's research agent from the original; it is not a copy of the source.