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 udnnh #827

Closed
72khz opened this issue Feb 14, 2021 · 5 comments
Closed

Fee reimbursement for trade udnnh #827

72khz opened this issue Feb 14, 2021 · 5 comments
Assignees

Comments

@72khz
Copy link

72khz commented Feb 14, 2021

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

reimburse-request

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: 4d48375acf2f955fd1bde87f9f9c4f37219bfcd19aeb3f83e979124dfc862fb4
Taker: e146fd0878db7002ae08fc14c1157f6d58717e1c55c292b396ad2d6cac5b1de5
Deposit: c748ab194a13f7073111f1ac1117973392eadf4b73f881f5c0563145884bb745

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: v1.5.5

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

Other notes: Trade failed on step 1 after fee deposit. Funds lost. Please reimburse.

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

@72khz 72khz changed the title Fee reimbursement for trade XXXXX Fee reimbursement for trade udnnh Feb 14, 2021
@leo816
Copy link
Contributor

leo816 commented Feb 25, 2021

were you the maker or the taker? please provide the full screenshot of all the trade details

@leo816 leo816 self-assigned this Feb 25, 2021
@72khz
Copy link
Author

72khz commented Feb 28, 2021

were you the maker or the taker? please provide the full screenshot of all the trade details

Thank you for your response, @leo816. I was the taker. I have updated my Bisq version since the initial trade. Screenshots have been included below of the open trade section window, the open trade chat window, the attention/error message window within the open trade section and failed trade section.

Screenshot of Open Trade Window (Open Trade Section Window):
1-Trade ID udnnh - Screenshot of Open Trade Window

Screenshot of Trade Chat (Open Trade Section Window):
2-Trade ID udnnh - Screenshot of Trade Chat

Screenshot of Attention/Error Message Window 1 (Open Trade Section Window)
3-Trade ID udnnh - Screenshot of Attention Window

Screenshot of Attention Window/Message 2 (Failed Trades Section Window):
4-Trade ID udnnh - Screenshot of Attention Window 2 - Moving to Failed Trades

Additionally, if you need the the detailed JSON trade udnnh data and/or an un-blurred screenshot of the trade details (the first screenshot image that was posted in the initial support request message on this thread by me 14 days ago) for complete verification, I can provide those as well. For privacy, these file access links are password-protected and will each expire within 30 days (March 29, 2021). If access to the detailed json trade data and/or un-blurred screenshot image of the trade details, please contact me via email for the password: 72khz@pm.me

Detailed JSON trade udnnh data (.txt file):
https://drive.protonmail.com/urls/2X59V735HG

Un-Blurred Screenshot of udnnh Trade Details (.png file):
https://drive.protonmail.com/urls/8H3XK3JS7M

❤️

The information provided should verify the information of the trade, allow for the successful unlocking of funds and resolves this issue. If this is not the case and more information is needed, please let me know on this support request thread, or, you can contact me via email (72khz@pm.me) for any additional steps, or email me to receive password access to the 2 private links posted above.

With that said, I want to close the response with this: Thank you for your time, your attention, and for helping support one of the world's first (and, in my opinion, the best we have right now) decentralized cryptocurrency trading platforms. I wish the process to request and unlock funds from failed trades was much easier for Bisq (because I would really like to receive the funds back... just a thought for the future from an active Bisq user: can we somehow automatically and securely submit private trade information data [within the Bisq app] similar to how the XMR auto trade function works? Just a thought I had...), Anyways, I understand that the technology is still new, and time is very limited. Since it's new, and, like we see with many of these new decentralized blockchain projects, there are still improvements to be made, kinks and issues to be worked out, but, ultimately, I'm confident the Bisq network will improve over time. Bisq already has a proven track record of incredible features, updates and fixes. This is the first time I've had a major issue like this and I've successfully used it for quite a few trades. Kudos to the whole Bisq team. I cannot speak on behalf of the traders or community members, nor do I know the entirety of your role for the Bisq network (other than your response to this support request), but, from my perspective, @leo816 : your work, time, insight and vision within this space are sincerely appreciated and valued as the world begins to enter into the blockchain economy. Warm regards.

@72khz
Copy link
Author

72khz commented Mar 25, 2021

Hi @leo816 has there been any update on this at all?

My BTC address in case it is necessary for the next steps: bc1qgnylydw5h62a2zuc09f98ngz9rs9jk8gx2fvdt

Thanks again for your help!

@72khz
Copy link
Author

72khz commented Apr 4, 2021

Hi @leo816 it has been almost 2 months since this initial request. Can you, or someone from the Bisq community/support team, at least please give me confirmation on whether or not these funds will be reimbursed. @KanoczTomas @huey735 @cbeams

Any next steps or insight would be appreciated. Thank you again for your time.

@leo816 leo816 added this to Todo in Lost fee reimbursements via automation Apr 28, 2021
@leo816
Copy link
Contributor

leo816 commented Apr 28, 2021

sorry that I didn't answer earlier, the taker fee wasn't published and the funds never left your wallet. Therefore a reimbursement is not justified. If this were to happen in the future please contact us through keybase, my handle is @leo816

@leo816 leo816 closed this as completed May 9, 2021
Lost fee reimbursements automation moved this from Todo to Closed May 9, 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