Fix fee calculation in bitcoind client#25
Merged
Conversation
The issue is that the `Sub` and `Sum` traits cannot have their generic parameter types unified automatically. Both types must be specified. Alternatively, specifying the `Sum` parameter types on separate bindings allows the compiler to correctly infer the `Sub` parameter type.
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
2 participants
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.
When using the bitcoind client for transaction resolution, the fee calculation was completely wrong. Every previous output was considered the fee.
The fix is calculating the fee as the difference between the transaction outputs and the previous outputs.