Re-phrase splice_channel error message
What the developer wrote
Authored by Jeffrey Czyz
Re-phrase splice_channel error message
What changed, and why it matters
This commit only rewords an error message shown when a user tries to splice a Lightning channel before it is ready. No code behavior, logic, or security boundary changes.
No security action needed; treat as a normal documentation/UX wording change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
A single string in an API misuse error is changed from ‘commitment point needs to be advanced once’ to ‘until a payment is routed’. The underlying check (holder_commitment_point.current_point().is_none()) and the returned error variant remain identical. It is a user-facing wording clarification with no functional or security impact.
Changed components
lightning/src/ln/channel.rsInspect captured patch +1 / −1
diff --git a/lightning/src/ln/channel.rs b/lightning/src/ln/channel.rs
index 115d68a..fe2a150 100644
--- a/lightning/src/ln/channel.rs
+++ b/lightning/src/ln/channel.rs
@@ -10574,7 +10574,7 @@ where
if self.holder_commitment_point.current_point().is_none() {
return Err(APIError::APIMisuseError {
err: format!(
- "Channel {} cannot be spliced, commitment point needs to be advanced once",
+ "Channel {} cannot be spliced until a payment is routed",
self.context.channel_id(),
),
});
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.