AsĪ result, unlike the channel.db file, it's always safe to copy this fileįor backup at ones desired location. Each time a channel is opened orĬlosed, this file is updated on disk in a safe manner (atomic file rename). This is a special file that contains SCBĮntries for all currently open channels. Method will likely be via the channel.backup file that's stored on-diskĪlongside the rest of the chain data. There are multiple ways of obtaining SCBs from lnd. Right after the channel is created, as we have all the data required to make aīackup, but lack information about the future HTLCs that the channel will By "fully settled" we mean funds that are in theīase commitment outputs, and not HTLCs. Given a valid SCB, the user will be able to recover funds that are fully Random node can't attempt to import another user's channels. Protect privacy of the users channels in the back up state, and ensure that a Themselves are encrypted using a key derived from the user's seed, this way we Their channels in the case of partial or complete data loss. Provide a simple, safe method to allow users to recover the settled funds in Knows if they have the latest state of a channel or not. Those methods can be dangerous as one never This method of backing up channels, vs doing things like rsyncing or copying We say safe, as care has been taken to ensure that there are no foot guns in Ultimately leads to us recovering the funds from the channel on-chain.
Need to initiate the Data Loss Protection (DLP) feature in the protocol, which The backup contains all the information we To be obtained once: when the channel is created. Off-Chain RecoveryĪfter version v0.6-beta of lnd, the daemon now ships with a new featureĬalled Static Channel Backups (SCBs). Remember to remove the flag once the rescan was completed successfully toĪvoid rescanning again for every restart of lnd. When finished, the following is returned, To track the recovery progress, one can use theĬommand lncli getrecoveryinfo. Depending on how old the wallet is (the cipher seed stores the wallet'sīirthday!) and how many addresses were used, the rescan may take anywhere fromĪ few minutes to a few hours. That final line indicates the rescan is complete! If not all funds haveĪppeared, then the user may need to repeat the process with a higher recovery LNWL: Catching up block hashes to height 748, this might take a while LNWL: Recovered addresses from blocks 748-748 LNWL: Scanning 1 blocks for recoverable addresses CHBU: Swapping old multi backup file from test_lnd3/data/chain/bitcoin/simnet/temp-dont-use.backup to test_lnd3/data/chain/bitcoin/simnet/channel.backup CHBU: Updating backup file at test_lnd3/data/chain/bitcoin/simnet/channel.backup LNWL: RECOVERY MODE ENABLED - rescanning for used addresses with recovery_window=2500 LTND: Wallet recovery mode enabled with address lookahead of 2500 addresses When a new lnd node is created, it is given a 24-word seed phrase, called anįormats look similar, but the only commonality they share is that they use theĪ valid seed phrase obtained over the CLI lncli create command looks something The SCB file is encrypted using a key derived from the user's seed. If one is only attempting to recover on chain funds, then only the first item Your encrypted Static Channel Backup file (or the raw data).Depending on theĮxact nature of operation of a given lnd node, one of these pools of fundsįund recovery for lnd will require two pieces of data: Multi-sig output typically referred to as a payment channel. Off-chain funds on the other hand exist within a 2-of-2 Outputs under the control of lnd that can be spent immediately, and withoutĪny auxiliary data. Coins in lndĬan exist in one of two pools: on-chain or off-chain. In this document, we'll go over the various built-in mechanisms for recoveringįunds from lnd due to any sort of data loss, or malfunction. Recovering Funds From lnd (funds are safu!) Streaming Updates via SubscribeChannelBackups.Recovering Funds From lnd (funds are safu!).
0 kommentar(er)
