You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I migrated an existing installation from linux with umbrel 0.5 to raspi with umbrel 1.2.2.
To accelerate the migration, i copied the Bitcoin fully synced blockchain to the new installation. In order to do, i stopped the services bitcoind and lnd after some minutes of running.
I guess the process of rescaning the addresses and chain for transactions from my wallet was broken and i can not resume it.
I started the lnd process with args reset-wallet-transactions=true but in the logs it tells that is rescaning for 0 addresses.
[INF] LNWL: Started rescan from block 0000000000000000000a487228e3d5b7b4e1a86xxx (height 661xxx) for 0 addresses
From the official recovery faq of lightning, i saw that we can specify the number of addresses to rescan with the argument "--recovery_window=2500" when unlocking the wallet. lncli unlock --recovery_window=2500
Where is it possible to specify this argument to unlock the wallet?
The text was updated successfully, but these errors were encountered:
I migrated an existing installation from linux with umbrel 0.5 to raspi with umbrel 1.2.2.
To accelerate the migration, i copied the Bitcoin fully synced blockchain to the new installation. In order to do, i stopped the services bitcoind and lnd after some minutes of running.
I guess the process of rescaning the addresses and chain for transactions from my wallet was broken and i can not resume it.
I started the lnd process with args reset-wallet-transactions=true but in the logs it tells that is rescaning for 0 addresses.
[INF] LNWL: Started rescan from block 0000000000000000000a487228e3d5b7b4e1a86xxx (height 661xxx) for 0 addresses
From the official recovery faq of lightning, i saw that we can specify the number of addresses to rescan with the argument "--recovery_window=2500" when unlocking the wallet. lncli unlock --recovery_window=2500
Where is it possible to specify this argument to unlock the wallet?
The text was updated successfully, but these errors were encountered: