-
Notifications
You must be signed in to change notification settings - Fork 456
Introduce FundingContributionBuilder API #4516
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
jkczyz
merged 6 commits into
lightningdevkit:main
from
wpaulino:funding-contribution-builder
Apr 21, 2026
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
b4b3bfb
Remove wallet argument from FundingTemplate::splice_out
wpaulino 41a2baa
Make PriorContribution::holder_balance non-optional
wpaulino 11610af
Derive FundingContribution::net_value implicitly
wpaulino 58f226e
Disallow net-negative contributions when adding value
wpaulino b1c3e29
Introduce FundingBuilder for splice requests
wpaulino 9f9fe58
Replace FundingTemplate contribution methods with FundingBuilder
wpaulino File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bug:
splice_outnow has additive output semantics when a prior contribution exists (viawith_prior_contribution). On RBF calls, the builder is seeded with the prior's outputs, thenadd_outputs(outputs)appends the same withdrawal again — doubling the withdrawal amount.Trace for the RBF case:
outputs = [TxOut { value: 546, ... }], no inputs (splice-out)outputs = [withdrawal]splice_outcallsadd_outputs([withdrawal])→outputs = [withdrawal, withdrawal]build()→amend_without_coin_selectionconstructs a splice-out with doubled outputscompute_feerate_adjustmentchecksfee + 1092 <= holder_balance— which passes (capacity > 20K sat)The old
splice_out_syncdestructured the template with..which discarded the prior contribution, so outputs were always treated as absolute. The newsplice_outis additive.Fix: use
without_prior_contributionin the closure when a prior exists, or userbf_prior_contribution_syncfor the RBF case. For example:(The
splice_inclosure has the analogous issue — already flagged in a prior review pass.)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@wpaulino Should we address this given the earlier comment?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Discussed offline. We'll wait for #4550 to land.