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
This particular LND instance seems to still use the old feerate for calculating the tx, even though we send UPDATE_FEE and then COMMITMENT_SIGNED. It's as if the peer has ignored the UPDATE_FEE: they've incremented the locktime correctly, but are using the old feerate?
Initial commitment tx (sent from us):
020000000153c163041bf8c6024b9a410b89dd1064e905a3f4f32f10170ab1c1f0d46cd2770000000000dc1013800170410f0000000000160014f67d879eaca8be644ab416adfaa47f169ecfcbf1aa0f1320
Commit tx after fee incr:
020000000153c163041bf8c6024b9a410b89dd1064e905a3f4f32f10170ab1c1f0d46cd2770000000000dc10138001242c0f0000000000160014f67d879eaca8be644ab416adfaa47f169ecfcbf1ab0f1320
The commit tx they checked signature against:
020000000153c163041bf8c6024b9a410b89dd1064e905a3f4f32f10170ab1c1f0d46cd2770000000000dc1013800170410f0000000000160014f67d879eaca8be644ab416adfaa47f169ecfcbf1ab0f1320
This was fixed in #3329 . Zooming out in the logs revealed that multiple reconnects and two update_fee in flight caused the issue: lnd is sending the right thing here, c-lightning was wrong.
Issue and Steps to Reproduce
This particular LND instance seems to still use the old feerate for calculating the tx, even though we send UPDATE_FEE and then COMMITMENT_SIGNED. It's as if the peer has ignored the UPDATE_FEE: they've incremented the locktime correctly, but are using the old feerate?
Initial commitment tx (sent from us):
020000000153c163041bf8c6024b9a410b89dd1064e905a3f4f32f10170ab1c1f0d46cd2770000000000dc1013800170410f0000000000160014f67d879eaca8be644ab416adfaa47f169ecfcbf1aa0f1320
Commit tx after fee incr:
020000000153c163041bf8c6024b9a410b89dd1064e905a3f4f32f10170ab1c1f0d46cd2770000000000dc10138001242c0f0000000000160014f67d879eaca8be644ab416adfaa47f169ecfcbf1ab0f1320
The commit tx they checked signature against:
020000000153c163041bf8c6024b9a410b89dd1064e905a3f4f32f10170ab1c1f0d46cd2770000000000dc1013800170410f0000000000160014f67d879eaca8be644ab416adfaa47f169ecfcbf1ab0f1320
getinfo
outputlightningd v0.7.3
The text was updated successfully, but these errors were encountered: