<oembed><type>rich</type><version>1.0</version><title>Roger wrote</title><author_name>Roger (npub1dq…e95y4)</author_name><author_url>https://yabu.me/npub1dqjq6jfjj5py9yjyxnzmzxqrt2fyfz54wr90rl084m980tausrjq9e95y4</author_url><provider_name>njump</provider_name><provider_url>https://yabu.me</provider_url><html>I&#39;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.&#xA;&#xA;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&#39;s machine staying alive.&#xA;&#xA;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.</html></oembed>