Difference between revisions of "Mediator"
Jump to navigation
Jump to search
(Mediator) |
(→Rights) |
||
| Line 15: | Line 15: | ||
== Rights == | == Rights == | ||
<!-- list in bullet points all special privileges that owner(s) of this role are granted, e.g. repository access --> | <!-- list in bullet points all special privileges that owner(s) of this role are granted, e.g. repository access --> | ||
| + | * Writer access to the bisq.support Keybase subteam | ||
| + | * Triage access to Support Team#Repositories | ||
| + | * Edit access to the #Coverage Calendar | ||
== Bonding == | == Bonding == | ||
Revision as of 16:13, 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 or one side is not responding, ask for proof of that was payment made. (verified screenshot using veruv.)
- Proceed to close the ticket accordingly with the information obtained from both parties.
- Being Available on Keybase to help users that may not be able to reach you through Bisq.
- Response time of 24 hours maximum.
Rights
- Writer access to the bisq.support Keybase subteam
- Triage access to Support Team#Repositories
- Edit access to the #Coverage Calendar
Bonding
10.000 BSQ required for bonding
