Static Channel Backups (SCB)

Welcome back! In our previous lesson, we introduced seed phrases and channel backups. Now let's dive deeper into Static Channel Backups (SCB)—understanding the format, how recovery works, and what makes them the industry standard for disaster recovery.

Understanding Static Channel Backups

A Static Channel Backup is a file that contains the minimal information needed to recover funds from Lightning channels after a catastrophic failure. Unlike a full database backup, it is "static" because it does not track every balance update; instead, it stores just enough data to initiate an emergency recovery process. Specifically, an SCB file includes your Channel ID, remote peer's public key, the channel point (funding transaction ID), and key cryptographic descriptors. Crucially, it does NOT contain your current balance or transaction history.

This minimalist approach relies on the Data Loss Protocol (DLP) defined in the Lightning specification (BOLT 2). When you restore an SCB, your node reaches out to its peers and signals that it has lost its channel state. Your peers, who still have the current state, will then initiate a "force close" on your behalf, broadcasting the most recent commitment transaction to the blockchain. This allows your funds to settle on-chain according to the last valid balance, prioritizing fund safety over seamless operation.

The Recovery Process

Recovery is a systematic operation. Start with a fresh installation of your node software on new hardware; do not attempt to copy over potentially corrupted old databases. Initialize the node using your seed phrase to recover your on-chain funds and identity. Once the node is running, import your SCB file (e.g., using `lncli restorechanbackup` in LND). Your node will then contact the peers listed in the backup and request them to force-close the channels. From there, you must wait: the peers broadcast the closing transactions, and after the necessary time-locks expire, your funds will return to your on-chain wallet. If a peer is offline, you must simply wait for them to return to complete the protocol.

A critical warning: NEVER attempt to restore your node by copying an old comprehensive database (like `channel.db`). Restoring an old state can cause your node to broadcast "revoked" transactions—effectively lying to the network about your balance. Your peers' nodes will interpret this as a theft attempt and automatically seize all funds in the channel as a penalty. SCBs avoid this risk completely by asking the peer to handle the closing process.

Implementation and Automation

Different implementations handle backups differently. LND creates a single `channel.backup` file that updates automatically; you can script this file to be copied to cloud storage or a remote server whenever it changes. Core Lightning relies on the `hsm_secret` and database snapshots, requiring a different backup strategy. Regardless of your platform, automation is essential. Since channel states change constantly, a manual backup from last week is useless for a channel opened yesterday. Many node-in-a-box solutions like Umbrel handle this automatically, but verifying that these backups are actually being created and are accessible is your responsibility.

Limitations and Best Practices

While SCBs are critical, they have limitations. They are designed for fund recovery, not seamless service restoration. Recovered channels will be closed, and you will not be able to route payments until you open new ones. Furthermore, the process relies on your peers being available and cooperative; if a peer is permanently offline or malicious, recovery becomes significantly harder.

To mitigate these risks, consider testing your recovery process on Testnet first to familiarize yourself with the commands. Beyond backups, you can enhance safety by using Watchtowers to protect against peer fraud and choosing reliable, well-connected peers who are likely to remain online. Treat your SCB as an emergency parachute: you hope never to use it, but you should check that it's packed correctly before every flight.

In this lesson, we've deep-dived into Static Channel Backups — how they work, recovery procedures, limitations, and best practices.

In our next lesson, we'll explore Node Security and Privacy — protecting your node from attacks and maintaining operational privacy.