Difference between revisions of "Mediator"

From Bisq Wiki
Jump to navigation Jump to search
(Edit for punctuation and style)
Line 13: Line 13:
 
* 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.
 
* 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.
 
* 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.
+
* 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.
 
* 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.
 
* Close the ticket after analyzing the information obtained from both parties.

Revision as of 20:23, 5 March 2020

This article documents the Mediator role.

Issue

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

Team

@bisq-network/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 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