Avoid splice checks when responding to stfu#4630
Conversation
Only gate local quiescence initiation on splice RBF eligibility. If the counterparty initiated quiescence first, respond with non-initiator stfu once pending channel updates are clear.
|
👋 Thanks for assigning @jkczyz as a reviewer! |
|
I've now thoroughly reviewed every hunk in this diff. Let me trace through the key scenario to verify correctness: Scenario: Node 0 has a pending Old code path (buggy):
New code path (fixed):
The fix is correct. The guard at line 14624 guarantees the No issues found. |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #4630 +/- ##
===========================================
+ Coverage 28.02% 86.63% +58.61%
===========================================
Files 126 159 +33
Lines 69960 110500 +40540
Branches 69960 110500 +40540
===========================================
+ Hits 19606 95735 +76129
+ Misses 49020 12230 -36790
- Partials 1334 2535 +1201
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
| // Since we may have also attempted to initiate quiescence but the counterparty | ||
| // initiated first, we'll retry after we're no longer quiescent. |
There was a problem hiding this comment.
IIUC, we would attempt to contribute as an acceptor, assuming we are both initiating for a splice.
|
👋 The first review has been submitted! Do you think this PR is ready for a second reviewer? If so, click here to assign a second reviewer. |
Only gate local quiescence initiation on splice RBF eligibility. If the counterparty initiated quiescence first, respond with non-initiator stfu once pending channel updates are clear.