-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Allow spending of unconfirmed BSQ change outputs #2482
Merged
ManfredKarrer
merged 12 commits into
bisq-network:master
from
ManfredKarrer:allow-spending-unconfirmed-bsq-utxs
Mar 4, 2019
Merged
Changes from all commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
03d0a22
Allow spending of unconfirmed BSQ change outputs
ManfredKarrer 4332c16
Cleanup
ManfredKarrer e62557c
Merge branch 'master' into allow-spending-unconfirmed-bsq-utxs
ManfredKarrer 9475cf2
Merge branch 'master' into allow-spending-unconfirmed-bsq-utxs
ManfredKarrer 1802508
Fix BSQ balance display for unconfirmed change outputs
ManfredKarrer 568be3d
Add missing check for isAvailableForSpending at unverifiedBalance
ManfredKarrer a0dd010
Fix balance update in case at vote result. Rename methods
ManfredKarrer 8d73308
Refactor: Rename onParseTxsComplete to onParseBlockComplete
ManfredKarrer e414e91
Refactor: Rename onParseTxsCompleteAfterBatchProcessing to
ManfredKarrer c5a383d
Fix balance for confiscated bonds
ManfredKarrer afd9d9c
Fix table layout
ManfredKarrer c91792c
Fix incorrect BSQ validator in send BSQ view
ManfredKarrer 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 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 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 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 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 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 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.
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.
Don't we need to check that it's also unspent or is the unconfirmed list only for unspent txs?
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.
As we remove entries for all connected outputs of any inputs we should not get that problem (e.g. user spend utxo from previously unconfirmed tx). If we would miss one it would throw an error on the BitcoinJ level if we try to use an input which is already spent. But I will have a look to add an additional check.