-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Track dropped arbitration messages #1173
Comments
For the record, my last known incident with dropped arbitration messages happened on January 6th, as documented in the forum at https://bisq.community/t/cannot-see-answers-of-closed-dispute-ticket/4262. I followed up with the user in a private chat there and all is well. |
I have several disputes where one trader is not responding, possibly due to dropped messages: |
@keo-bisq Can you post that on the Forum as well? |
Trade |
Trade |
Note: adding the above message on this issue was a mistake on my part. I meant to add it to #1174, and I've done that now at #1174 (comment) |
Trade ID |
It appears that the seller in trade |
One of my arbitration messages to the buyer in trade This dropped message caused at least one full day of unnecessary delay in the arbitration process. |
Issue moved to bisq-network/support #85 via ZenHub |
Per details in the description of #1172, this issue exists for tracking arbitration cases where messages have been dropped, or we believe they have been dropped.
To make note of an incident, add a comment to this issue as soon as possible, mention the Trade ID, who the arbitrator is, and explain what happened as best as you can. Do not include identifying details about the trade or traders involved.
Note: this issue and the instructions are primarily intended for @bisq-network/arbitrators, but individual traders are also welcome to follow these instructions if they believe they're experiencing a dropped message problem during arbitration.
In any case, by keeping close track of how often this problem is happening, we'll be able to know when we've solved it.
This issue is closely related to, but distinct from #1174. Please do not confuse the two.
The text was updated successfully, but these errors were encountered: