Risks and Limitations

Welcome to the final lesson of Course 2! We've celebrated Lightning's benefits — now let's honestly examine its risks and limitations. Understanding these tradeoffs helps you use Lightning wisely and set appropriate expectations.

Fundamental Constraints and Hot Wallets

First, let's be clear: Lightning doesn't replace Bitcoin's base layer. It complements it. Each layer has strengths and weaknesses, and trying to use Lightning for everything will lead to frustration. Lightning is optimized for frequent, smaller payments. It's not designed for cold storage, large settlements requiring maximum security, or situations where you can't maintain any online presence.

Unlike on-chain Bitcoin, which can be stored completely offline, Lightning funds must be online to participate in the network, as your node needs to monitor the blockchain for potential cheating, route payments, and respond to channel partner actions. This requirement means Lightning funds are inherently "hot" and connected to the internet, making them more exposed to hacking, malware, and operational errors than cold storage. To mitigate this risk, you should only keep as much on Lightning as you would in a physical spending wallet; essentially, you should treat it like cash in your pocket rather than savings in a high-security vault.

Liquidity and Routing Challenges

Lightning payments require liquidity in the right places, meaning that for sending, you need outbound capacity in channels pointing toward the recipient, while for receiving, you must have inbound capacity so others can pay you. When it comes to routing, payments may fail if intermediate channels lack sufficient capacity, a constraint that is fundamentally different from on-chain Bitcoin where you can send any amount to anyone without pre-arrangement. Payment failures can occur if no route with sufficient liquidity exists or if a routing node is unresponsive. Although success rates have improved dramatically, these failures still happen more frequently than on-chain transactions. Mitigate these risks by using wallets with advanced pathfinding, ensuring your node is well-connected, and using services like LN+ for liquidity swaps.

Channel Management and Risks

Running a Lightning node requires ongoing attention. You must open channels with reliable peers, balance liquidity, and monitor channel health continuously. You must also be prepared to handle force-closes gracefully when they occur. When channels close uncooperatively through a force close, funds are locked for a time-lock period—typically ranging from 24 hours to two weeks. During this interval, your funds are stuck and unusable, and you may encounter high on-chain fees to claim them. These force closes can be triggered by software bugs, network connectivity issues, or uncooperative channel partners. To mitigate these risks, choose reliable peers, maintain backups, and avoid relying on funds that could potentially be locked.

If your node goes offline, a malicious channel partner could potentially broadcast an old state to steal your funds. Watchtowers can mitigate this risk by monitoring the blockchain on your behalf and automatically broadcasting penalty transactions if they detect cheating. While public watchtower services vary in reliability, running your own or using LN+ "Watch Swaps" (where node operators watch each other) provides effective protection.

Other Limitations and Reality

Although Lightning improves privacy significantly, it is not entirely anonymous. Direct channel partners are aware when they transact with you, and channel openings and closures remain visible on-chain. Additionally, Lightning's regulatory status varies by jurisdiction, and capacity limits still exist for very large payments. On-chain fee spikes can make channel management expensive.

Despite these limitations, Lightning works remarkably well for its intended use cases. Millions of payments route successfully every day. The key is using Lightning appropriately: it excels at daily spending, micropayments, and privacy-focused transactions, but is not suitable for long-term cold storage or life savings. Mitigate risks by limiting hot wallet funds, actively managing liquidity, using watchtowers, and maintaining privacy through best practices.

In this lesson, we've honestly examined Lightning's risks and limitations. This isn't to discourage you — it's to prepare you. Understanding tradeoffs makes you a more effective user and helps you make informed decisions about when Lightning is the right tool.

This concludes Course 2 on Benefits and Tradeoffs. You now have a balanced understanding of what Lightning offers and what it demands.

In Course 3, we'll get practical with Getting Started with Lightning — exploring the spectrum from simple custodial wallets to fully self-hosted nodes.