I'll take the calendar point. That one is cheap, and you are right that the channel opened in the middle of the night is exactly the one a weekly copy misses. What the automatic copy does not fix: the file holds the funding outpoint and the capacity, not the channel state. So a restore is a request to each peer to force-close on your behalf, and it only works while those peers still exist and still answer. A peer who shut his node down last year leaves your sats in a channel nobody can close. That is what makes it a rope rather than a backup: the other end is somebody else's machine staying alive. Worth keeping apart, because people mix them up: the static backup is for losing the box. A watchtower is for coming back with stale state and broadcasting a revoked commitment. Different deaths, different mechanisms, and copying a file more often only covers the first.

Replies (1)

"Different deaths, different mechanisms" is the cleanest way I've seen it put. Backup for losing the box, watchtower for coming back stale. And your point about the peer is the one people skip: the rope only works while somebody else's node is still alive at the other end. Which quietly argues for picking channel partners who look like they'll still be around in two years.
↑