Bitfinex' bfx-lnd1 node seems to be offline, with several force-closed channels. The channel with my node has been force-closed by their node, and I don't know why that happened. Do you know what's going on?
pull down to refresh
pull down to refresh
Bitfinex' bfx-lnd1 node seems to be offline, with several force-closed channels. The channel with my node has been force-closed by their node, and I don't know why that happened. Do you know what's going on?
I think they have migrated to lnd 0.19.2. and not increased their gossip defaults. Another big node ran into the issue some weeks ago but was able to solve by increasing the defaults
https://github.com/lightningnetwork/lnd/pull/10096/files
But only guessing.
Known bug weeks ago and this just happened in the last few hours, would be a major oops
I've noticed a handful of nodes "crashing out" with similar symptoms in recent weeks. May be related to the new features (bugs) introduced since LND v0.19+
https://github.com/lightningnetwork/lnd/issues/10033
I've had some peers on v0.19+ reach out about channels going offline, then force closing, for no apparent reason.
This is almost certainly the case.
Large nodes like bfx-lnd1 need to explicitly override the defaults with much higher values than are even recommended in the LND docs.
Very strange, only 26 out of 600+ so far according to explorers, I'd assume optimization if not for the fact they're all forced closes...
I see 10096 is merged, but not 10033. For those still with 0.18.5, would you recommend updating to 0.19.3 or not yet?
That's definitely concerning, especially given the reputation and size of Bitfinex’s bfx-lnd1 node. When a major node like that goes offline and starts force-closing channels, it usually signals one of three things: planned maintenance, a technical failure, or a security-related issue (like potential compromise). Since there hasn’t been an official statement yet, the uncertainty can understandably be frustrating especially for those directly affected. Hopefully, this is just temporary and they’ll issue an explanation soon. In the meantime, it's a good reminder to stay vigilant, monitor your node's health closely, and consider how much exposure you want to large hubs in the network. Decentralization is powerful, but dependency on centralized entities even in Lightning has its risks.