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 fukfcgjg #567

Closed
dav1dpgit opened this issue Nov 27, 2020 · 11 comments
Closed

Fee reimbursement for trade fukfcgjg #567

dav1dpgit opened this issue Nov 27, 2020 · 11 comments
Assignees

Comments

@dav1dpgit
Copy link

The XXXXX part in the issue title are the first characters of the Trade ID before the "-" (dash).

SCREENSHOT HERE
image

The screenshot from the Bisq client must have the Trade ID, Deposit, Maker and Taker TXIDs visible. Of course some trades do not have all 3 types, that is ok. Make sure all private information is covered (like bank accounts, name, etc). Do not upload images where sensitive private data is visible!

Maker: cfbce12510aa02ceaf7b668e3bef99a902af7bf30abd8a7d5153d6a4cbd2b96f
Taker: N/A
Deposit: N/A

A reimbursement request has to contain textual representation of Maker, Taker and Deposit TXIDs (copy them from the client to the issue). All TXIDs that are visible in the screenshot must be copied to the issue in text form! Please use exact form for Maker/Taker/Deposit - no abbreviations like M:, T: or adding extra characters like "Maker TX:", etc. Leave those fields as they are and replace the "........" with the appropreate txid

Bisq version: 1.5.0

Provide the Bisq client version to help developers identify the causing issue.

Other notes:

Looking to receive my transaction BSQ fee back.

@jmacxx
Copy link
Contributor

jmacxx commented Nov 27, 2020

This issue is fixed by bisq-network/bisq#4764 which will be in the next release, 1.5.1

@dav1dpgit it looks like the your wallet is not synced properly.

@dav1dpgit
Copy link
Author

dav1dpgit commented Nov 27, 2020 via email

@jmacxx
Copy link
Contributor

jmacxx commented Nov 27, 2020

First, see if a restart of the Bisq app causes it to sync up. I always look at DAO -> BSQ Wallet -> Transactions and watch for the progress bar and latest verified block displayed there to catch up to mempool.space.

If it still does not sync then you probably want to do an SPV Resync

@dav1dpgit
Copy link
Author

dav1dpgit commented Nov 27, 2020 via email

@jmacxx
Copy link
Contributor

jmacxx commented Nov 27, 2020

Yes there's a process this ticket will go through to get your fees back. @leo816 will contact you here.

@leo816
Copy link
Contributor

leo816 commented Dec 1, 2020

please provide the btc address where you would like to be reimbursed

@leo816 leo816 self-assigned this Dec 1, 2020
@leo816 leo816 added this to Todo in Lost fee reimbursements via automation Dec 1, 2020
@leo816 leo816 moved this from Todo to Waiting for info in Lost fee reimbursements Dec 1, 2020
@dav1dpgit
Copy link
Author

please provide the btc address where you would like to be reimbursed

bc1qxqjay5rrjygsgcyu8gwh2ytk9f4dlmendag3mk

Thank you very much.

@dav1dpgit
Copy link
Author

dav1dpgit commented Dec 4, 2020

@leo816 If you are looking for a BSQ address, use this one:

B16ssKC5Fh2QaFip9NBzWYfZdA2xKsRidjY

@dav1dpgit
Copy link
Author

@leo816 When will this reimbursement be made?

@leo816
Copy link
Contributor

leo816 commented Dec 10, 2020

there has been an issue and we are trying to solve it asap

@leo816 leo816 moved this from Waiting for info to In progress in Lost fee reimbursements Dec 22, 2020
@leo816 leo816 moved this from In progress to Staged in Lost fee reimbursements Dec 22, 2020
@leo816
Copy link
Contributor

leo816 commented Dec 22, 2020

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

@leo816 leo816 closed this as completed Dec 22, 2020
Lost fee reimbursements automation moved this from Staged to Closed Dec 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

3 participants