You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ACINQ's Lightning node (presumably Eclair) purportedly sent my C-Lightning node a bad commitment signature. My node responded with a WIRE_ERROR, and ACINQ's node unilaterally closed the channel.
I would expect an honest node never to send any bad signatures.
From my limited understanding, I would surmise that the error occurred because my node sent a new feerate of 12114 but ACINQ's node responded with a new commitment transaction that still used the old feerate of 8136.
I am not sure if I could reproduce this issue. I had had this channel open with ACINQ for many weeks before this anomaly occurred. I suspect an edge case.
I do not know what version of Eclair is running on ACINQ's node presently.
My environment is C-Lightning 0.7.2.1, compiled from sources, running on Gentoo Linux.
I would expect an honest node never to send any bad signatures.
This error usually doesn't mean that the signature is invalid in itself, but rather that there is a disagreement on the data being signed. It's a typical interop problem.
my node sent a new feerate of 12114 but ACINQ's node responded with a new commitment transaction that still used the old feerate of 8136.
This reminds me ElementsProject/lightning#2661, which is a bug on c-lightning's side. Could be something different, I'll look into it.
ACINQ's Lightning node (presumably Eclair) purportedly sent my C-Lightning node a bad commitment signature. My node responded with a
WIRE_ERROR
, and ACINQ's node unilaterally closed the channel.I would expect an honest node never to send any bad signatures.
See the channel log from my C-Lightning node for the full details. Here is an excerpt from the point of reconnection through to the error:
From my limited understanding, I would surmise that the error occurred because my node sent a new feerate of 12114 but ACINQ's node responded with a new commitment transaction that still used the old feerate of 8136.
I am not sure if I could reproduce this issue. I had had this channel open with ACINQ for many weeks before this anomaly occurred. I suspect an edge case.
I do not know what version of Eclair is running on ACINQ's node presently.
My environment is C-Lightning 0.7.2.1, compiled from sources, running on Gentoo Linux.
03864ef025fde8fb587d989186ce6a4a186895ee44a926bfc370e2c366597a3f8f.log
The text was updated successfully, but these errors were encountered: