Need some help with Blixt closed channel \ stacker news ~bitcoin

pull down to refresh

Need some help with Blixt closed channel

461 sats \ 19 comments \ @EntropyBearer 16 Jun bitcoin freebie

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. ;)

view all related items

1 reply \ @Lux 17 Jun

Had a similar situaton few months ago, didn't see the funds after force close. Recovered them with chantools.

50 sats \ 0 replies \ @EntropyBearer OP 17 Jun freebie

You are the real MVP @Lux. chantools solved the problem. For anyone from the future having a similar problem, the command I used was:

https://m.stacker.news/35762

¹ ² ³

No point hiding the address I sweep to as I exposed the origin address on the post anyway. ↩
As for the general usage, I exported both AEZEED_MNEMONIC and AEZEED_PASSPHRASE as environment variables, so I didn't have to pass it on each command. ↩
I manually published the transaction showed in that screenshot, but one could also append the --publish flag to publish it right through the CLI. ↩

22 sats \ 10 replies \ @Natalia 16 Jun

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).

isn't default closing it to the Taproot address? Weird indeed.

did you try the whole process as I mentioned in #464537?

It's not a huge amount of sats, but sats are sats.

don't worry, your sats still belong to you; just need some time and effort to locate it. 😂

0 sats \ 9 replies \ @EntropyBearer OP 16 Jun freebie

Precisely. And using it (the zprv) on Sparrow shows me the opening transaction just fine.

https://m.stacker.news/35560

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...

1 sat \ 3 replies \ @SatsMate 16 Jun

If it is a closed channel shouldn't you have the option to send it via on-chain?

Also, what is the methodology for some of these wallet closing channels? I had a Breeze wallet channel close recently and the only thing I can think of is I didn't update the app/or send anything in a decent period. It would be nice to be notified before channel closure, because in this case I had a decent amount (thankfully recovered).

0 sats \ 0 replies \ @falcoonbr 17 Jun

Doesnt blixt have any "channel states" (lncli pendingchannels)? waiting, pending open, pending close, pending force close? if that was a force close then it would show the block maturity height

0 sats \ 0 replies \ @EntropyBearer OP 16 Jun

I'm using the lightning implementation built-in on Blockstream's Green Wallet, and they are using Greenlight for the "on-demand lightning node" and Breez as the LSP. Last week I had a swap deposit through on-chain fail to complete (it did get confirmed on-chain). They managed to make a refund possible, but I couldn't say what happened.

I guess that's the state of mobile lightning wallets as of today, we shouldn't be too reckless.

0 sats \ 0 replies \ @EntropyBearer OP 16 Jun

If it is a closed channel shouldn't you have the option to send it via on-chain?

Yep, but it apparently went to a different wallet derivation, as the FC should go to a taproot address, not a native segwit one. Still trying to figure out why that happened.

Also, what is the methodology for some of these wallet closing channels?

I think Blixt is pretty much using LND "rules". As for Breez, not sure, but I guess they are using Greenlight/Core Lightning ¹ as of today.

https://blog.blockstream.com/lightning-platform-breez-to-integrate-greenlight-to-build-non-custodial-lightning-apps ↩

Footnotes

Footnotes