22 sats \ 10 replies \ @Natalia 16 Jun \ on: Need some help with Blixt closed channel bitcoin
isn't default closing it to the Taproot address? Weird indeed.
did you try the whole process as I mentioned in #464537?
don't worry, your sats still belong to you; just need some time and effort to locate it. 😂
Precisely. And using it (the
zprv
) on Sparrow shows me the opening transaction just fine.That's what's bugging me. Where did that last address came from? :/
I followed #464537. And also used Zeus/Blixt besides Sparrow. Weirdly enough, Zeus/Blixt shows stuff as if it was a new wallet, they didn't recover neither
tx
nor previous channels.Oh, and I used the
Static Channel Backup
file, so it might have being corrupted and could have messed up the recovering process...reply
reply
No clue what happened to be honest... And the weird part is that Blixt/Zeus show conflicting info, comparing it to Sparrow as once the channel closed, I even tried to restore the wallet on both Zeus and Blixt, without the SCB file, to see if the address from the forced close managed to appear. No luck even so...
reply
reply
Yeah, I thought about the "recentness" of the transaction. But even so, shouldn't it appear as pending in the wallet even being only in the mempool (without any confirmations)?
reply
idk how it exactly works during the sweeping, but it probably has something to do with the time lock? @DarthCoin and from my previous FC transaction, it did take some time for the onchain sats to "come back."
let's wait a bit and find out.
reply
can't say that this issue is specific to Blixt.
Blixt in the end is a LND node so all the issues with closing channels are related to how LND works.
Sorry but I can't figure it out what was going on from these sparse informations.
Will need more logs and dev expertise.
I would suggest to contact @hampus (Blixt dev) with more logs and details.
reply
Speaking of logs, I'm seeing a lot of those on this last try. Any ideia on why I could be "stuck" around this block?