Fix comment regarding holder commitment point
What the developer wrote
Authored by Jeffrey Czyz
Fix comment regarding holder commitment point
What changed, and why it matters
This commit changes a single word in a code comment, replacing 'current' with 'next' to accurately describe which commitment point is being populated when restoring a channel after an upgrade. There is no code change, no functional change, and no security impact.
No action required. This is a documentation-only change with no security relevance.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff is a one-word comment correction in lightning/src/ln/channel.rs. The comment now correctly states that the signer must be available to populate the ‘next commitment point’ rather than the ‘current commitment point’ during channel restoration. The surrounding code and logic are unchanged.
Changed components
lightning/src/ln/channel.rs (comment only)Inspect captured patch +1 / −1
diff --git a/lightning/src/ln/channel.rs b/lightning/src/ln/channel.rs
index 4d8c9d0..0328810 100644
--- a/lightning/src/ln/channel.rs
+++ b/lightning/src/ln/channel.rs
@@ -13835,7 +13835,7 @@ where
}
// If we're restoring this channel for the first time after an upgrade, then we require that the
- // signer be available so that we can immediately populate the current commitment point. Channel
+ // signer be available so that we can immediately populate the next commitment point. Channel
// restoration will fail if this is not possible.
let holder_commitment_point =
match (holder_commitment_point_next_opt, holder_commitment_point_pending_next_opt) {
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.