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 dkz4sv #774

Closed
reimbotsment opened this issue Jan 15, 2021 · 6 comments
Closed

Fee reimbursement for trade dkz4sv #774

reimbotsment opened this issue Jan 15, 2021 · 6 comments
Assignees

Comments

@reimbotsment
Copy link

reimbotsment commented Jan 15, 2021

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

SCREENSHOT HERE
Screenshot_20210115_200459

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: 6779c247dced5291c91a5acc57ff61295d6aff181ad2b7a94c92be0214124895
Taker: 26130811b992be26609671d81f36eb0ae40ed540e231b1c85439b173a5869c56
Deposit: 06cc39029943502194ad4d0c62c2a87c609ddf75a9ca75c6f94d731aae984098

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.4

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

Other notes: Please reimburse fees.
Thanks.
Preferred address:
deleted for privacy reasons.

Issue #197 can be used as a good example of a correct reimbursement request.

@leo816
Copy link
Contributor

leo816 commented Jan 26, 2021

please provide your preferred btc address for reimbursement

@leo816 leo816 self-assigned this Jan 26, 2021
@leo816 leo816 added this to Todo in Lost fee reimbursements via automation Jan 26, 2021
@leo816 leo816 moved this from Todo to Ready in Lost fee reimbursements Jan 26, 2021
@leo816
Copy link
Contributor

leo816 commented Jan 27, 2021

taker fee is invalid, no funds should have left your wallet

@leo816 leo816 moved this from Ready to Waiting for info in Lost fee reimbursements Jan 27, 2021
@reimbotsment
Copy link
Author

Thanks!
I know this is an unrelated issue, but I have 0.03btc locked in the top right corner. However, when I open the locked funds tab they are 0 BTC (which is the correct value). My question is, how can the 0.03btc in the top right corner go away to reflect the real value (0)BTC.

@leo816
Copy link
Contributor

leo816 commented Jan 27, 2021

did you try doing a spv resync? https://bisq.wiki/Resyncing_SPV_file

@reimbotsment
Copy link
Author

Yes, I have tried it multiple times, the display is still the same.

@leo816
Copy link
Contributor

leo816 commented Mar 7, 2021

if a user has still locked funds shown in the UI but no failed trade in the pending trades view, a closed or failed trade causes the problem. to solve that easiest is to delete the ClosedTrades and FailedTrades files in the db folder. the user has to shut down bisq first, do a backup and then delete those 2 files. after that the locked funds should be 0 if not other open trades

@leo816 leo816 closed this as completed Mar 7, 2021
Lost fee reimbursements automation moved this from Waiting for info to Closed Mar 7, 2021
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

2 participants