Difference between revisions of "Mediator"
Jump to navigation
Jump to search
(→Duties) |
|||
| Line 27: | Line 27: | ||
== Bonding == | == Bonding == | ||
<!-- indicate whether bonding is required for this role, and if so, how much --> | <!-- indicate whether bonding is required for this role, and if so, how much --> | ||
| − | 10.000 BSQ required | + | 10.000 BSQ required |
https://github.com/bisq-network/bisq/blob/42a037e/core/src/main/java/bisq/core/dao/state/model/governance/BondedRoleType.java#L68 | https://github.com/bisq-network/bisq/blob/42a037e/core/src/main/java/bisq/core/dao/state/model/governance/BondedRoleType.java#L68 | ||
[[Category:Roles]] | [[Category:Roles]] | ||
Revision as of 21:07, 4 March 2020
Issue
https://github.com/bisq-network/roles/issues/83
Team
https://github.com/orgs/bisq-network/teams/mediators
Duties
- Contact 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 https://github.com/bisq-network/support/issues and notify L2 Support.
Rights
- Writer access to the
bisq.supportKeybase subteam - Compensation request rights per case solved.
Bonding
10.000 BSQ required https://github.com/bisq-network/bisq/blob/42a037e/core/src/main/java/bisq/core/dao/state/model/governance/BondedRoleType.java#L68
