Difference between revisions of "Mediator"
Jump to navigation
Jump to search
(→Rights) |
(→Rights) |
||
| Line 19: | Line 19: | ||
* 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]] | * [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]] | ||
| − | |||
== Bonding == | == Bonding == | ||
Revision as of 16:52, 4 March 2020
Issue
https://github.com/bisq-network/roles/issues/83
Team
https://github.com/orgs/bisq-network/teams/mediators
Duties
- Establish a communication channel with 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 between parties, proof that the payment was made must be presented.(verified screenshot using veruv.)
- 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 you through Bisq.
- Respond to time of 24 hours or less.
Rights
- Writer access to the
bisq.supportKeybase subteam - Triage access to Support Team#Repositories
Bonding
10.000 BSQ required for bonding
