Uh oh!
There was an error while loading. Please reload this page.
Introduce RenegotiatedFundingLocked monitor update variant - #3894
Conversation
👋 Thanks for assigning @TheBlueMatt as a reviewer! |
ldk-reviews-bot
commented
Jun 30, 2025
🔔 1st Reminder Hey @jkczyz! This PR has been waiting for your review. |
ldk-reviews-bot
commented
Jul 2, 2025
🔔 2nd Reminder Hey @jkczyz! This PR has been waiting for your review. |
ldk-reviews-bot
commented
Jul 5, 2025
🔔 3rd Reminder Hey @jkczyz! This PR has been waiting for your review. |
ldk-reviews-bot
commented
Jul 7, 2025
🔔 4th Reminder Hey @jkczyz! This PR has been waiting for your review. |
ldk-reviews-bot
commented
Jul 9, 2025
🔔 5th Reminder Hey @jkczyz! This PR has been waiting for your review. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
ldk-reviews-bot
commented
Jul 9, 2025
👋 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. |
00e8bb3 to
c1ead6aCompareCodecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@## main #3894 +/- ##
==========================================
- Coverage 89.65% 88.99% -0.67%
==========================================
Files 164 167 +3 Lines 134658 121836 -12822 Branches 134658 121836 -12822 ==========================================
- Hits 120734 108432 -12302 + Misses 11246 10988 -258 + Partials 2678 2416 -262
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:
|
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
c1ead6a to
a6d4b1eCompareUh oh!
There was an error while loading. Please reload this page.
TheBlueMatt
left a comment
There was a problem hiding this comment.
Note that rustfmt/MSRV are failing.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
a6d4b1e to
3bdf268Compare3bdf268 to
6c43f5dCompareldk-reviews-bot
commented
Jul 21, 2025
🔔 1st Reminder Hey @TheBlueMatt@jkczyz! This PR has been waiting for your review. |
ldk-reviews-bot
commented
Jul 21, 2025
🔔 1st Reminder Hey @TheBlueMatt@jkczyz! This PR has been waiting for your review. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
6c43f5d to
aa625f0CompareUh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
This is a new `ChannelMonitorUpdateStep` variant intended to be used whenever a new funding transaction that was negotiated and applied via the `RenegotiatedFunding` update reaches its intended confirmation depth and both sides of the channel exchange `channel_ready`/`splice_locked`. This commit primarily focuses on its use for splices, but future work will expand where needed to support RBFs for a dual funded channel. This monitor update ensures that the monitor can safely drop all prior commitment data since it is now considered invalid/unnecessary. Once the update is applied, only state for the new funding transaction is tracked going forward, until the monitor receives another `RenegotiatedFunding` update.
It's only intended to be set during initialization and used to check if the channel is v1 or v2. We rename it to `first_negotiated_funding_txo` to better reflect its purpose.
aa625f0 to
22d5428CompareUh oh!
There was an error while loading. Please reload this page.
This is a new
ChannelMonitorUpdateStepvariant intended to be used whenever a new funding transaction that was negotiated and applied via theRenegotiatedFundingupdate reaches its intended confirmation depth and both sides of the channel exchangechannel_ready/splice_locked. This commit primarily focuses on its use for splices, but future work will expand where needed to support RBFs for a dual funded channel.This monitor update ensures that the monitor can safely drop all prior commitment data since it is now considered invalid/unnecessary. Once the update is applied, only state for the new funding transaction is tracked going forward, until the monitor receives another
RenegotiatedFundingupdate.