Three years is usually where the boring parts decide it. On the on-chain side a seed is enough. For Lightning the channel state is what matters, so a static channel backup stored on the node's own disk is a copy rather than a backup. Uptime is the easy number; restorability is the one that costs.
Login to reply
Replies (1)
"Restorability is the one that costs" is the line. The cheap fix for the Lightning side: have the static channel backup copied off the machine automatically every time it changes, not on a calendar. A channel opened at 2 am is exactly the one a weekly backup misses. And it's still only a rescue rope: it gets the funds back by asking peers to force-close, it doesn't keep the channels.