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

Allow users to Open Arbitration ticket if first attempt fails #6797

Closed
pazza83 opened this issue Aug 8, 2023 · 0 comments · Fixed by #6818
Closed

Allow users to Open Arbitration ticket if first attempt fails #6797

pazza83 opened this issue Aug 8, 2023 · 0 comments · Fixed by #6818

Comments

@pazza83
Copy link

pazza83 commented Aug 8, 2023

I think there is currently a bug in Bisq where once a user broadcasts the DPT, and if for whatever reason, an arbitration ticket is not opened on their instance, they are then unable to press the arbitration button again as they get an error message due to the DPT being successful even though the opening of an arbitration ticket has not been.

This is annoying for the user as they will have to wait longer for the payout. It is also causes more work for the mediator and arbitration as a less secure off Bisq reimbursement is required.

An example of a recent error message a user received is:

Error
An error occurred at task: PublishedDelayedPayoutTx
TxBroadcastException{
     txId='d7b32b1f6602b0830492d6caebffc3b8ad4c417f7de91bb8f327284553b0eaf6'
} bisq.core.btc.exceptions.TxBroadcastException: We got broadcastTx called with a tx which has an open timeoutTimer. txId=d7b32b1f6602b0830492d6caebffc3b8ad4c417f7de91bb8f327284553b0eaf6

I have the logs from the user to provide if needed.

The ideal solution would be for the arbitration button to remain clickable based not on the DPT transaction alone but on if an arbitration ticket if is open on the user's instance. Or alternatively just not give an error message and just attempt to send the DPT AND open an arbitration ticket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant