Static Channel Backup

Overview

Meaning and scope

A Static Channel Backup is LND recovery data used with the node seed to recover settled Lightning channel funds after catastrophic data loss. The Static Channel Backup procedure should protect recovery material, separate approval roles, document every action, and test that the restored system reproduces the intended accounts and controls.

Mechanism and operation

An LND SCB contains information about channels and peers and is encrypted for the node. During recovery, the restored node contacts peers and asks them to force-close channels, allowing the owner to recover settled on-chain funds. It complements the wallet seed and must correspond to the affected node. Missing peer availability or unusual channel conditions can complicate recovery. Operators should automatically copy updated channel backups to independent locations, preserve the node seed separately, and verify backup integrity. Recovery procedures should follow the implementation’s current guidance and avoid using stale channel databases incorrectly. Tests should confirm that backups belong to the intended node without exposing production secrets.

Practical payment example

A Lightning node operator stores a static channel backup and restores it after hardware loss. The recovery procedure accounts for channel-state coordination and avoids representing the backup as a full substitute for current channel data.

Operational checks

The scope of Static Channel Backup should identify the protected wallet, key, account, service, or business process; the triggering failure; who may declare the incident; which identity and entitlement evidence is required; and the recovery point and recovery time objectives that govern restoration. For Static Channel Backup, independent storage and periodic exercises reduce correlated failure but introduce their own custody obligations.

Distinctions and limits

An SCB does not restore channels to their former live operating state or reconstruct every latest commitment locally. For Static Channel Backup, important risks include fraudulent recovery requests, guardian collusion, unavailable shares, outdated backups, compromised cloud accounts, missing derivation metadata, untested procedures, and simultaneous loss of primary and backup systems.

Related reading

Related definitions: channel backups, backup.