Uh oh!
There was an error while loading. Please reload this page.
Note the mempool policy requirements of zero-fee commitment channels - #4187
Conversation
👋 Thanks for assigning @TheBlueMatt as a reviewer! |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@## main #4187 +/- ##
==========================================
+ Coverage 88.86% 88.87% +0.01%
==========================================
Files 180 180 Lines 137869 137863 -6 Branches 137869 137863 -6 ==========================================
+ Hits 122520 122531 +11 + Misses 12539 12523 -16 + Partials 2810 2809 -1
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:
|
| /// is set) or `static_remote_key` channel. | ||
| /// | ||
| /// To have confidence that a force-close transaction will reach miners and get confirmed, | ||
| /// zero-fee commitment channels require your Bitcoin node **and some of its peers** to |
There was a problem hiding this comment.
Might be worth being explicit that there needs to be a path between your node and miners running 29+.
13a5269 to
30e3bdcCompare30e3bdc to
426c881CompareUh oh!
There was an error while loading. Please reload this page.
TheBlueMatt
commented
Oct 30, 2025
Backported to 0.2 in #4193 |
No description provided.