[bisq-network/bisq] Improve handling of failed trades and offers (#3566)
chimp1984
notifications at github.com
Wed Nov 6 15:24:15 UTC 2019
chimp1984 commented on this pull request.
> - if (lockedUpFundsHandler != null) {
- lockedUpFundsHandler.accept(message);
+ // We check if there are locked up funds in failed or closed trades
+ try {
+ Set<String> setOfAllTradeIds = tradeManager.getSetOfFailedOrClosedTradeIdsFromLockedInFunds();
+ btcWalletService.getAddressEntriesForTrade().stream()
+ .filter(e -> setOfAllTradeIds.contains(e.getOfferId()) &&
+ e.getContext() == AddressEntry.Context.MULTI_SIG)
+ .forEach(e -> {
+ Coin balance = e.getCoinLockedInMultiSig();
+ if (balance.isPositive()) {
+ String message = Res.get("popup.warning.lockedUpFunds",
+ formatter.formatCoinWithCode(balance), e.getAddressString(), e.getOfferId());
+ log.warn(message);
+ if (lockedUpFundsHandler != null) {
+ lockedUpFundsHandler.accept(message);
I am not sure how to reproduce that and if deposit tx is null then the user cannot open a dispute.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/pull/3566#discussion_r343156626
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20191106/3dedf615/attachment.html>
More information about the bisq-github
mailing list