search

bisq-network / support

@bisq-network user support issues
https://bisq.wiki/User_support
19 stars 12 forks source link

Fee reimbursement for trade "id": "702073-d28b0a79-7dd1-4b7e-970e-1bdce0cff0bf-1914 Error: Timeout reached. Protocol did not complete in 120 sec. #1505

Closed Scoop193 closed 8 months ago

Scoop193 commented 9 months ago

The XXXXX part in the issue title are the first characters of the Trade ID before the "-" (dash). Attention The trade protocol encountered some problems.

There was an error during trade protocol execution.

Error: Timeout reached. Protocol did not complete in 120 sec.

It might be that this error is not critical, and the trade can be completed normally. If you are unsure, open a mediation ticket to get advice from Bisq mediators.

If the error was critical and the trade cannot be completed, you might have lost your trade fee. Request a reimbursement for lost trade fees here: [1] [https://github.com/bisq-network/support/issues] SCREENSHOT HERE

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: .......... Taker: ........... Deposit: .......... BTC mining fees lost: .......... eg 0.00005 BTC Trade fees lost, please state if BSQ or BTC: .......... eg 5.43 BSQ or 0.000088 BTC

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: BTC address for reimbursement:

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

Other notes:

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

darawhelan commented 9 months ago

Hi @Scoop193 please can you complete the issue using the template with all the information required.

Scoop193 commented 9 months ago

This is what it shows on my end

On Mon, Nov 20, 2023, 9:23 AM Greg B @.***> wrote:

On Sun, Nov 19, 2023, 4:06 AM Greg B @.***> wrote:

On Sun, Nov 19, 2023, 4:05 AM Greg B @.***> wrote:

On Fri, Nov 17, 2023, 3:09 PM Dara Whelan @.***> wrote:

Hi @Scoop193 https://github.com/Scoop193 please can you complete the issue using the template with all the information required.

— Reply to this email directly, view it on GitHub https://github.com/bisq-network/support/issues/1505#issuecomment-1817034530, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASMXYSRQRSGUKGPNWA5BGELYE6753AVCNFSM6AAAAAA7LSUSNCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJXGAZTINJTGA . You are receiving this because you were mentioned.Message ID: @.***>

darawhelan commented 9 months ago

Have a look at some of the previous compensation requests to see how the template should be completed:

https://github.com/bisq-network/support/issues?q=is%3Aissue+is%3Aclosed