Difference between revisions of "Mediator"

From Bisq Wiki
Jump to navigation Jump to search
Line 22: Line 22:
  
 
* Writer access to the <code>bisq.support</code> Keybase subteam
 
* Writer access to the <code>bisq.support</code> Keybase subteam
* [https://help.github.com/en/github/setting-up-and-managing-organizations-and-teams/repository-permission-levels-for-an-organization#repository-access-for-each-permission-level Triage] access to [[Support Team#Repositories]]
 
 
* Compensation request rights per case solved.
 
* Compensation request rights per case solved.
  

Revision as of 20:44, 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 in the multisig.
  • In case of disagreement or unclear information, proof may be required by the Mediator from either party.
  • 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 new 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