search

bisq-network / support

@bisq-network user support issues
https://bisq.wiki/User_support
19 stars 12 forks source link

Fee reimbursement for trade ooeeaqe3 #40

Closed cbeams closed 6 years ago

cbeams commented 6 years ago

This issue has been created per the process detailed in bisq-network/support#35 to track the reimbursement of trading and mining fees lost due to the 'failed transaction broadcast' problem being tracked at bisq-network/exchange#1193 and under investigation at bisq-network/exchange#1195.

If the trade ID in the title of this issue is yours, then please click the Subscribe button in the right menu of this issue to be notified about the status of your reimbursement.

If you do not see a Subscribe button, then you are not logged in to GitHub. Please log in or create an account if necessary. You'll then be able to Subscribe to this issue and you will get updates by email.

nuschpl commented 6 years ago

Added pull request, but please check if did it properly -from the trade maker, and taker transaction are now in blockchain, there is no deposit transation. I included trading fee and miniing fee from both maker and taker, not sure how to handle security deposit , don't see in other trades, does it mean it will be handled by app itself and another blockchain transaction with arbiter?

nuschpl commented 6 years ago

@cbeams should the security deposit be also included here ?

cbeams commented 6 years ago

That's great, @nuschpl, thank you! I'll double-check your changes later, but much appreciated.

Regarding the security deposit, no: it's not part of the reimbursement, because these funds never left your wallet. You may need to resync your SPV file, however, in order for the funds to show up properly again. This should have been described in the closing comment on your arbitration ticket for ooeeaqe3, but in case it wasn't, just go to Settings->Network info and click the "resync SPV chain" button.

nuschpl commented 6 years ago

@cbeams, yes I resync SPV already, but it still shows in locked trades. If it's local I assume something must trigger release what shows in locked trades is it still opened support ticket? OTR What cause resync required are some wallet address removed then readded or their private keys exchanged true TOR? Is it safe due to blockchain and TOR communication or only due to the way current version of Bisq client work?

cbeams commented 6 years ago

@nuschpl, regarding the locked funds, I'm going to need more information. Please share a screenshot of your Portfolio->My open offers and Portfolio->Open trades screens.

You can send these to me via email at chris@beams.io (PGP) or via @cbeams on Keybase if you prefer to do so for privacy reasons.

cbeams commented 6 years ago

@nuschpl, please also attach a screenshot of the Details screen for the trades related to your pull request at #55. For an example of what this should look like, see https://github.com/bisq-network/support/issues/53#issuecomment-358799056. Thanks.

nuschpl commented 6 years ago

@cbeams The transaction is no longer locked i see now "Ticket closed" in History instead Open Trades. Regarding details screenshot, please find attached: image

cbeams commented 6 years ago

Staged for reimbursement in d6b7ce6

cbeams commented 6 years ago

Closing as reimbursed via the batch transaction documented at https://github.com/bisq-network/support/issues/35#issuecomment-362038006.