Oh yes. I think I recall this issue from back in 2022. Had a ton of force closes with LND peers because LND liked to throw ERRORs, when it should issue warnings.
This is the LND issue:
https://github.com/lightningnetwork/lnd/issues/6593
The CLN developers fixed this by just ignoring LND throwing that particular error, otherwise all CLN nodes would have regular FCs with LND, even though LND was the culprit.
Seems to be resolved on the LND side now.
zechendorf / Christopher
npub18q…r7jpu
2024-01-08 14:37:01
in reply to nevent1q…tnuv
Author Public Key
npub18qnp2a99trmvdarj092qcr32zs29z0fe487fkta8e9dtsf8fzw6qlr7jpuPublished at
2024-01-08 14:37:01Event JSON
{
"id": "73fd7b2d2dfaa4bd16c980fd349c0b82cf1cb2da0b4656c93c53232ced88b27a",
"pubkey": "38261574a558f6c6f47279540c0e2a1414513d39a9fc9b2fa7c95ab824e913b4",
"created_at": 1704724621,
"kind": 1,
"tags": [
[
"e",
"450ca4f0dfc71c464fc6bda7784468a06dc371c5295e57d79822ffd57ed77141"
],
[
"p",
"52b4a076bcbbbdc3a1aefa3735816cf74993b1b8db202b01c883c58be7fad8bd"
],
[
"r",
"https://github.com/lightningnetwork/lnd/issues/6593"
]
],
"content": "Oh yes. I think I recall this issue from back in 2022. Had a ton of force closes with LND peers because LND liked to throw ERRORs, when it should issue warnings.\n\nThis is the LND issue:\nhttps://github.com/lightningnetwork/lnd/issues/6593\n\nThe CLN developers fixed this by just ignoring LND throwing that particular error, otherwise all CLN nodes would have regular FCs with LND, even though LND was the culprit.\n\nSeems to be resolved on the LND side now.",
"sig": "4a0137625a02ea3e0bcd2e4bd8e3d27afb501f3cc5d53b0062c96f8eb36afec4822dbe3794ebf536c9ae22ce9dcc548f602918cb896d5b813edf9667a8cd1804"
}