You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Previously, onchain_send silently fell back to the node's default fee estimation when given an invalid fee_rate_sat_per_vb (e.g., overflows), and bolt12_receive silently dropped the quantity parameter when amount_msat was not set. Both cases now return an error instead.
Matching CLI-side validation added for both cases.
👋 Thanks for assigning @tnull as a reviewer!
I'll wait for their review and will help manage the review process.
Once they submit their review, I'll check if a second reviewer would be helpful.
The reason will be displayed to describe this comment to others. Learn more.
Just removed the cli side validation. Too hit this would have to enter something greater than u64::MAX / 250 which is super unlikely a user enters anyways and don't want to add the whole rust-bitcoin dep tree to the cli just for that.
The reason will be displayed to describe this comment to others. Learn more.
Debatable, @TheBlueMatt previously wanted to drop quantity from the LDK Node API (lightningdevkit/ldk-node#642, but was closed as abandoned). Matt, do you still think we should?
Previously, an invalid fee_rate_sat_per_vb (overflows) was silently
collapsed into None via .and_then(), causing the node to substitute
its default fee estimation without informing the user. Now the server
returns an InvalidRequestError if the fee rate overflows.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Previously, setting quantity without amount_msat silently produced a
variable-amount offer with no quantity constraint. Now both the server
and CLI reject this misconfiguration with a clear error message.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Previously,
onchain_sendsilently fell back to the node's default fee estimation when given an invalidfee_rate_sat_per_vb(e.g., overflows), andbolt12_receivesilently dropped thequantityparameter whenamount_msatwas not set. Both cases now return an error instead.Matching CLI-side validation added for both cases.