Skip to content
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

Fee reimbursement for trade cul50x #219

Closed
xbyvee opened this issue Mar 27, 2019 · 3 comments
Closed

Fee reimbursement for trade cul50x #219

xbyvee opened this issue Mar 27, 2019 · 3 comments
Assignees

Comments

@xbyvee
Copy link

xbyvee commented Mar 27, 2019

Cursor_and_Ubuntu_64-bit

Maker: f0e709e683489f1f82773abba1772eab6fd44e757cacc1cefdd89b6dbaab0de5
Taker: c667c2c99ca419a5db728a7b9da4ef39c82a46b424da47521f3b99a7d2500d21
Deposit: N/A

Bisq version: 0.9.5 Linux

Other notes:
Tried cmd + o to contact support and a modal came up with "open support request" and "cancel" when i clicked open support request nothing happened. Tried exporting backup and using on OSX instead of linux and exactly the same issue.

This is the first time I have traded on Bisq. Is this a bug? I'd like to try trading again but I'm scared this might happen again. Any way to avoid this happening?

Asking to return maker fee.

@KanoczTomas KanoczTomas self-assigned this Mar 27, 2019
@KanoczTomas
Copy link
Contributor

@xbyvee this happens sometimes when your peer runs older bisq version or the p2p network has congestion. It happens a lot lot less then in the past (checkout number of past reimbursement requests). As people upgrade it should resolve. Your fees will be returned in a few days, as I am finishing the batch file. You can not loose funds, only the fees which we refund. So I would say do not let this stop you from trading.

KanoczTomas added a commit that referenced this issue Mar 27, 2019
@KanoczTomas
Copy link
Contributor

Will be reimbursed with #200

@KanoczTomas
Copy link
Contributor

Closing as reimbursed via the batch transaction documented at #200 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants