Claiming "outcome": "UNCLAIMED" after recovery #8182
Replies: 2 comments 4 replies
-
Also have this in the logs from one of the unclaimed channel points (68329b44c0aaf848a4f4d19e04f5a5291029913fd794a415ab841f0ed952d62e:0)
|
Beta Was this translation helpful? Give feedback.
-
Hi @tempo-beme, it seems like that all channel closes settled on-chain and the settled balances have already been used to open new channels. https://mempool.space/testnet/address/tb1q7hdw3f9mnfy36e7uhgnx375zm94ca9hfqvn2r6l5dh0kk4y7pczskakkxj I'd say this is why you can't recover with |
Beta Was this translation helpful? Give feedback.
-
Hi,
I have been practicing recovering a node after a failure on testnet but have hit a roadblock.
I had a lnd node where I have been backing up the
channel.backup
file. This node had three open channels. I shut down the node and then attempted to restore it byrestorechanbackup
and passing in thechannel.backup
fileThis managed to find the previous channels and force close them, I think? However, my
channelbalance
has the balance of only one of the channels. when I runlncli closedchannels
, I get the printout below. From this, you can see that one channel appears as outcome "claimed" but the other two appear as "unclaimed". I'm not sure what needs to be done to "claim" them. Also, I'm a bit confused as to why all the channels appear as"close_initiator": "INITIATOR_REMOTE",
. I expected them to beINITIATOR_LOCAL
?To recover these funds I have tried:
chantools sweepremoteclosed --recoverywindow 300 --sweepaddr tb1quljn5gcttuw6xekjg2dcp9ua2crezn8q2n46my --publish -t --apiurl https://blockstream.info/testnet/api/
This returned
found 0 sweep targets with total value of 0 satoshis which is below the dust limit of 600
Any help would be greatly appreciated.
Beta Was this translation helpful? Give feedback.
All reactions