Hey Stackers, what's up?
If any Blixt user could lend a hand I would be really glad.
I'm having trouble "locating" the funds of a forced closed channel using Blixt Wallet. First I would like to add that I read thought @Natalia's #464537 and that doesn't seem to be the problem (I tried increasing the gap limit on Sparrow anyways).
I'm gonna mention some transactions here to make it easier. Nonetheless, they originated from a Federation address, so I guess I won't be doxxing myself out too much.
Following the Money:
The thing that seems awkward to me is that it opened the channel from a Taproot address, but it seems to close it into a native segwit one (which won't appear in the same "expected" wallet).
Using the same
xprv root key
(but changing Sparrow to Native Segwit) doesn't seem to solve the problem.It's not a huge amount of sats, but sats are sats. So, if anyone have an idea of what could be happening it would be a huge help. ;)
chantools
solved the problem. For anyone from the future having a similar problem, the command I used was:Footnotes
--publish
flag to publish it right through the CLI. ↩zprv
) on Sparrow shows me the opening transaction just fine.tx
nor previous channels.Static Channel Backup
file, so it might have being corrupted and could have messed up the recovering process...Footnotes