pull down to refresh
214 sats \ 6 replies \ @DarthCoin 22 Aug \ on: My LN channel on Alby Hub was force-closed bitcoin
@Alby can you give more details?
Indeed same happen to my Alby hub with a LDK backend.
I think was due to these crazy high mempool fees going on.
It really sucks when you buy an inbound channel and they FC on you...
Also is really confusing, no info about the closing channel and where the sats are going, to which onchain wallet, closing tx, no way to trace that closing channel.
This happened due to this huge fee, short fee spike and an issue with some LSPs. It's actually a default lightning mechanism and a protective measure implemented in LDK.
it's a closure and the sats will become available in the savings balance.
we are investigating this and also collaborating with LSPs to see how this can be avoided in such a LSP relationship.
we will post an update later.
reply
The fee negotiating process between LN implementations is terrible. And that could trigger this nightmare. LN devs should really consider to fix or change this behavior. I know is a protection mechanism in LN protocol, but it doesn't make any sense to get fucked so easily for no reason.
People are paying sats to buy those LSP channels and closing them just like that will have a huge impact in using this kind of nodes and LN in general.
reply
yes, we also worked hard on this and have quite some measures around fee negotiation to protect users. it eats a lot of resources :)
it's also a bit of a balance depending on the channel partners and how "trusted" those are. some implementations are rather strict which does not make sense in a LSP context.
this case was even another edge case...
reply
and they FC on you
Well, technically - you FC on them here. Automatically, but still, it's a local FC.
reply