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

Reduce or eliminate arbitration cases #39

Open
6 tasks
ripcurlx opened this issue Jul 29, 2020 · 1 comment
Open
6 tasks

Reduce or eliminate arbitration cases #39

ripcurlx opened this issue Jul 29, 2020 · 1 comment

Comments

@ripcurlx
Copy link
Member

ripcurlx commented Jul 29, 2020

This is a Bisq Network project. Please familiarize yourself with the project management process.

Description

Reduce or in best case eliminate arbitrator cases (refund agent cases).

Rationale

The v2 of the Bisq trade protocol was designed to handle a handful of arbitrator cases each month. Right now it is more like 1+ cases per day which is not sustainable and creates an unnecessary load on arbitrators.

This resulted in multiple proposals:

PRs:

It is required that we solve this problem one way or the other to reduce total trade time in case of arbitration and not to loose the arbitrator before an acceptable alternative is available.

Criteria for delivery / Measures of success

  • 3 arbitration cases/cycle if we have 3000 trades/cycle
  • refunds without arbitrator (mediator & DAO)

Risks

Tasks

  • Communicate penalty of trade protocol violation within trade process
  • Improve badge notification system to show indicator only if there is an open task to fulfill
  • Add desktop notifications
  • Enable mobile notifications for trading peer if available

Estimates

This project has no estimates as it is more an epic story. The tasks or proposals that we agree on working will have estimates instead.

@ripcurlx ripcurlx created this issue from a note in Priorities (Projects) Jul 29, 2020
@ripcurlx ripcurlx changed the title Reduce or eliminate arbitrator cases Reduce or eliminate arbitration cases Jul 29, 2020
@ripcurlx ripcurlx self-assigned this Jul 30, 2020
@ripcurlx
Copy link
Member Author

We shipped a deposit percentage suggestion based on volatility in v1.3.7. It seems to be helping, but it didn't reduce the refund agent cases to an acceptable level. So we need to continue with the improvements mentioned above and to find out the root cause of unresponsive sellers in the Monero market.

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

No branches or pull requests

1 participant