21 sats \ 5 replies \ @rolznz 25 Aug \ parent \ on: My LN channel on Alby Hub was force-closed bitcoin
Sorry about this. The withdraw function a bit broken (it didn't set aside enough fees to pay the onchain transaction) and will be fixed in 1.6.0 (released on github) which should also go out to Alby Cloud in the next few days.
write
preview
21 sats \ 4 replies \ @rolznz 25 Aug
Also, if you don't use the wallet any more and have no channels, you can import the seed into Sparrow wallet and send the sats out from there (only recommended if you are not actively using Alby Hub)
reply
0 sats \ 3 replies \ @DarthCoin 25 Aug
Yes I know that. I just wanted to be able to use as is (testing all functionalities) and also I tried to open a new channel with those onchain funds with no success. The wallet is locked.
But I will wait for new release and reset the node switching to LND backend. More testing. New apps like this must be intense tested and improved with feedback. I do not complain that is not workinng smooth from beggining, these are normal issues that must be informed to devs and give as much feedback is possible.
reply
0 sats \ 2 replies \ @rolznz 25 Aug
I really appreciate that, thanks.
What do you mean by the wallet being locked? this does not sound good!
reply
0 sats \ 1 reply \ @DarthCoin 25 Aug
locked - not being able to do any tx with it. I tried to look into logs (debug section), but there is not very detailed and seems to be ok. It's OK, if you already found the problem and will be fixed, no problem, will wait for the fix and test again. I really like this idea of Alby Hub and want to go discovering more about it. Will send also some more feedbacks.
reply
21 sats \ 0 replies \ @rolznz 25 Aug
Thanks very much!
For the logs, you'd have to change the log level. This will be difficult currently in Alby Cloud, but if you run Alby Hub self-hosted you can change the LDK_LOG_LEVEL environment variable (e.g. LDK_LOG_LEVEL=1 to enable trace logs).
reply