Fix DependencyGraph vsize calculation
#12618
Draft
Conversation
This file contains 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #12584
DependencyGraphclass required the inputs' amount and size to compute the availablevsize. However, we already know the available vsize by summing the vsize credentials, which are the source of truth. If well recomputing the available vsize is not correct, it was never a problem until the payment in coinjoins were introduced because that feature requires to introduce "virtual" inputs to the list of registered inputs what theDependencyGraphdidn't know how to treat (and shouldn't have to treat at all).In fact, the `DependencyGraph