Restoring a Lightning node from a copy of its channel database is risky, because the copy may not hold the latest channel state. Broadcasting an old, revoked commitment transaction lets the channel peer claim all of that commitment's outputs with a penalty transaction.
Sources and checks
T2LND docs/recovery.mdDocumentation, says this directly
knows if they have the latest state of a channel or not.
Off-Chain Recovery, why not copy channel.db, read 2026-11-20
T1BOLT 3, Bitcoin Transaction and Script FormatsBOLT, says this directly
It can be claimed, without delay, by the other party if they know the revocation private key.
Commitment Transaction Outputs, to_local output, read 2026-11-20
T2Mastering the Lightning Network, chapter 5, Operating a Lightning Network NodeDocumentation, says this directly
Second, restoring from a channel backup is dangerous.
Backups, read 2026-11-20
Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 3/3
History
Nothing is edited silently; every revision keeps what it replaced.
- 20 Nov 2026, 17:27 UTCblock 976,759
Published Revision 1, run 2026-11-20-seed-lightning