Difference between revisions of "Mediator"

From Bisq Wiki
Jump to navigation Jump to search
Line 13: Line 13:
 
* Check: Maker Fee Transaction ID, Taker Fee Transaction ID and Deposit Transaction ID to make sure the transaction was published and funds aren't stuck.
 
* Check: Maker Fee Transaction ID, Taker Fee Transaction ID and Deposit Transaction ID to make sure the transaction was published and funds aren't stuck.
 
* If needed, Mediator will require private keys from both traders to carry out a manual payout.
 
* If needed, Mediator will require private keys from both traders to carry out a manual payout.
* In case of disagreement or unclear information, verified proof of payment may be required by the Mediator to either party.
+
* In case of disagreement or unclear information, verified proof of payment may be required to either party by the Mediator.
 
* Proceed to close the ticket after analyzing the information obtained from both parties.
 
* Proceed to close the ticket after analyzing the information obtained from both parties.
 
* Being available on Keybase to help users that may not be able to reach out through the Bisq app.
 
* Being available on Keybase to help users that may not be able to reach out through the Bisq app.

Revision as of 20:53, 4 March 2020

Issue

https://github.com/bisq-network/roles/issues/83

Team

https://github.com/orgs/bisq-network/teams/mediators

@bisq-network/support

Duties

  • Message both parties of the trade (BTC buyer and BTC seller) to find out what the problem is and why the Support ticket was opened.
  • Check: Maker Fee Transaction ID, Taker Fee Transaction ID and Deposit Transaction ID to make sure the transaction was published and funds aren't stuck.
  • If needed, Mediator will require private keys from both traders to carry out a manual payout.
  • In case of disagreement or unclear information, verified proof of payment may be required to either party by the Mediator.
  • Proceed to close the ticket after analyzing the information obtained from both parties.
  • Being available on Keybase to help users that may not be able to reach out through the Bisq app.
  • Respond time of 24 hours or less.
  • When bugs occur, create detailed issues on Github and notify L2 Support.

Rights

  • Writer access to the bisq.support Keybase subteam
  • Compensation request rights per case solved.

Bonding

10.000 BSQ required for bonding