Mediator

This article documents the Mediator role.

Issue

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

Team

@bisq-network/mediators

Duties

TODO: transcribe / adapt this section to the dedicated Mediation process article, such that it can be consumed by both mediators and users alike. This section will remain, but should consist of a shorter list of bullet points linking to the Mediation article, being available on Keybase, mentioning what to do with updating / creating bug issues.

• 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 the 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.
• 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.support Keybase subteam
• Compensation request rights per case solved

Bonding

A 10,000 BSQ bond is required. See https://github.com/bisq-network/bisq/blob/42a037e/core/src/main/java/bisq/core/dao/state/model/governance/BondedRoleType.java#L68