Branch-and-bound coin selection#49
Closed
sneurlax wants to merge 3 commits into
Closed
Conversation
Contributor
Author
|
Closed as duplicate of #40 |
- fix: wasm target - fix: allow to increase maxCandidate number without overflowing
Adapt the branch and bound selection to the Locktime abstraction introduced for v5. The locktime parameter of CoinSelection.branchAndBound and the test call sites still used a raw int.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
In doing some maintenance on our fork of coinlib, I decided to break out the differences between cypherstack/coinlib and its peercoin/coinlib base. This is one of those differences: "Branch and bound" coin selection support. No worries if you don't want this :)