[bisq-network/support] Fee reimbursement for trade zyjzoe5 (#976)
Stan
notifications at github.com
Mon Aug 2 15:50:04 CEST 2021
Dispute Details View (mediator pazza never found support ticket on his UI)
![zyjzoe5-dispute-details](https://user-images.githubusercontent.com/36207203/127871289-a7a63764-ad32-4220-878a-874104f5d889.png)
Failed Trade Details (peer would not communicate with mediator or myself on Bisq chat or keybase)
![zyjzoe5-failed-trade-details](https://user-images.githubusercontent.com/36207203/127871298-bd566eef-9a86-45f5-b24f-9ad3f5817e1f.png)
Maker: .......... `f92ca78ae9f9385b499ca48081f0fa0b25e3d3bbb0ae572cf3cfd133ad38f85d`
Taker: ........... `f4f616634526068951761fb95b699dda8ee9e2bbc3a965fe2c3ee94cec9bf78b`
Deposit: .......... `c8d0a58163e7df951a9762f131ad27b8b1a304db066d88a770c7a718f7134a4f`
Bisq version: 1.7.1 and v.1.7.2
BTC address for reimbursement: `1HUP4WvE9MBouPSaTviKAUUnr9Ze3EVPbe`
Other notes:
TRADE: zyjzoe5-52376056-1bb2-471b-bac5-e33a2af3a47e-170
Problem: I took an offer from a maker that never paid a maker fee. My 0.04604780 BTC taker fee is locked up.
I was unable to create support ticket and chat with mediator pazza on Bisq UI (he never saw support ticket).
I was unable to communicate with maker via Bisq chat due to chat bugs and unwillingness of other side to communicate on keybase.
Other side was unwilling to chat with mediator @pazza on keybase.
Maker fee TX ID `f92ca78ae9f9385b499ca48081f0fa0b25e3d3bbb0ae572cf3cfd133ad38f85d` NEVER REACHED MEMPOOL
Taker fee TX ID `f4f616634526068951761fb95b699dda8ee9e2bbc3a965fe2c3ee94cec9bf78b` CONFIRMED
Deposit TX ID `c8d0a58163e7df951a9762f131ad27b8b1a304db066d88a770c7a718f7134a4f` NEVER REACHED MEMPOOL
https://mempool.space/tx/f92ca78ae9f9385b499ca48081f0fa0b25e3d3bbb0ae572cf3cfd133ad38f85d
https://mempool.space/tx/f4f616634526068951761fb95b699dda8ee9e2bbc3a965fe2c3ee94cec9bf78b
https://mempool.space/tx/c8d0a58163e7df951a9762f131ad27b8b1a304db066d88a770c7a718f7134a4f
Peer: 6ld2bdl5muonnzeum5vph4fknu44avuhrz6qzwsldrekmxpwdawwpcad.onion:9999
>_Issue [#197](https://github.com/bisq-network/support/issues/197) can be used as a good example of a correct reimbursement request._
--
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/support/issues/976
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20210802/751b2620/attachment.htm>
More information about the bisq-github
mailing list