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
0 new comment
144 sats \ 1 reply \ @02321d1dfd 22h freebie
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.
reply
0 new comment
21 sats \ 0 replies \ @justin_shocknet 22h
Known bug weeks ago and this just happened in the last few hours, would be a major oops
reply
0 new comment
511 sats \ 2 replies \ @nullcount 22h
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
reply
0 new comment
31 sats \ 0 replies \ @k00b 22h
I've had some peers on v0.19+ reach out about channels going offline, then force closing, for no apparent reason.
reply
0 new comment
42 sats \ 0 replies \ @evankaloudis 20h
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.
reply
0 new comment
71 sats \ 0 replies \ @justin_shocknet 22h
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...
reply
0 new comment
0 sats \ 0 replies \ @RamPl 18h outlawed
stackers have outlawed this. turn on wild west mode in your /settings to see outlawed content.