Arbitrator - Revision history

Pazza at 18:26, 16 April 2025

2025-04-16T18:26:05Z

Pazza at 02:33, 31 December 2022

2022-12-31T02:33:14Z

Pazza at 02:31, 31 December 2022

2022-12-31T02:31:02Z

W000000t: keybase > matrix

2022-01-22T19:16:06Z

keybase > matrix

Plebeian9000: bonding is not required for arbitrators

2020-08-13T15:15:41Z

bonding is not required for arbitrators

Cbeams: Remove unwanted Agent category

2020-06-08T07:59:43Z

Remove unwanted Agent category

HunterNyan: formatting

2020-04-27T05:13:07Z

formatting

HunterNyan: Added Bond, fixing links

2020-04-27T04:19:37Z

Added Bond, fixing links

Plebeian9000: add arbitrator role documentation

2020-04-02T14:22:28Z

add arbitrator role documentation

New page

An '''arbitrator''' resolves disputes that could not be resolved by traders on their own or with a [[Mediator|mediator]]'s help.

Arbitrators investigate disputes, just like mediators. But unlike mediators, whose suggestions encourage traders to make payouts from their own escrowed funds, an arbitrator's findings lead to a payout from the arbitrator themselves.

__TOC__

== Role Notes ==

=== Arbitrator's Role in Dispute Resolution ===

Currently, the arbitrator makes BTC payouts to aggrieved traders out of their own pocket and gets refunded by the Bisq DAO (hence the term ''refund agent'' used sometimes). But this arrangement is meant to be temporary, intended as a convenience so that traders can avoid making a reimbursement request to the DAO on their own. As software bugs are reduced and UX is improved, arbitrators will cease to make payouts, and instead, their findings will serve as a basis for the Bisq DAO to issue payouts directly to aggrieved traders.

The arbitrator role is one element of Bisq's decentralized dispute resolution process. Please see more details at [[Arbitration|arbitration]].

=== Arbitrator versus Legacy Arbitrator ===

Although arbitrators have been a component of dispute resolution on Bisq since its early days, the v1.2 update wholly changed the nature of the role.

Before the update, trade funds were secured in a 2-of-3 multisig escrow, in which arbitrators held the third key. They would evaluate disputes and then sign funds to traders as they saw fit. Since these arbitrators (which we now refer to as ''legacy arbitrators'') had some element of control over users' funds, those who filled the role had to be ''very'' highly trusted.

The v1.2 update enabled trade funds to be secured in a 2-of-2 multisig escrow, in which arbitrators have '''no involvement'''. Mediators handle most disputes, but if an arbitrator does get involved, payouts either come from the arbitrator's own pocket or from the Bisq DAO. Arbitrators are still trusted to conduct their role with integrity and consistency, but this is a wholly different kind of trust, one that is unrelated to the handling of users' funds, and thus one that doesn't even require a bond.

== Issue ==
https://github.com/bisq-network/roles/issues/93

== Team ==
[https://github.com/orgs/bisq-network/teams/refund-agents @bisq-network/refund-agents]

== Duties ==
* Investigate trader disputes and determine how payout should be made (must respond to traders within 5 days)
* Do payouts to traders as appropriate with BTC
* Request BSQ reimbursement from the Bisq DAO

== Rights ==
* Write access to the <code>bisq.support</code> Keybase subteam

== Bonding ==
Not required.

[[Category:Roles]]

@@ Line 5: / Line 5: @@
 __TOC__
-{{Admonition_Warn|BTC All trade placed from 1st January 2023 will use a new trade protocol that is designed to further improve the decentralization of Bisq. The new protocol is a result of the proposal [https://github.com/bisq-network/proposals/issues/390 Distribute Burningman role to contributors who burned BSQ] which was vote on in Bisq DAO cycle 41 with 100% approval.
+{{Admonition_Warn|All trades placed from 1st January 2023 will use a new trade protocol that is designed to further improve the decentralization of Bisq. The new protocol is a result of the proposal [https://github.com/bisq-network/proposals/issues/390 Distribute Burningman role to contributors who burned BSQ] which was vote on in Bisq DAO cycle 41 with 100% approval.
 The protocol change means trades placed from 1st January 2023 will have an important difference should the trade end in arbitration. This is as a result of the accepted proposal [https://github.com/bisq-network/proposals/issues/386 do not pay out the security deposit of the trade peer to the arbitration case winner].
@@ Line 22: / Line 22: @@
 === Arbitrator's Role in Dispute Resolution ===
-Currently, the arbitrator makes BTC payouts to aggrieved traders out of their own pocket and gets refunded by the Bisq DAO (hence the term ''refund agent'' used sometimes). But this arrangement is meant to be temporary, intended as a convenience so that traders can avoid making a reimbursement request to the DAO on their own. As software bugs are reduced and UX is improved, arbitrators will cease to make payouts, and instead, their findings will serve as a basis for the Bisq DAO to issue payouts directly to aggrieved traders.
+Currently, the arbitrator makes BTC payouts to aggrieved traders out of their own pocket and gets refunded by the Bisq DAO (hence the term ''refund agent'' used sometimes). But this arrangement is intended as a convenience so that traders can avoid making a reimbursement request to the DAO on their own.
 The arbitrator role is one element of Bisq's decentralized dispute resolution process. Please see more details at [[Arbitration|arbitration]].

← Older revision		Revision as of 02:31, 31 December 2022
Line 4:		Line 4:

	__TOC__		__TOC__
		+
		+	{{Admonition_Warn\|BTC All trade placed from 1st January 2023 will use a new trade protocol that is designed to further improve the decentralization of Bisq. The new protocol is a result of the proposal [https://github.com/bisq-network/proposals/issues/390 Distribute Burningman role to contributors who burned BSQ] which was vote on in Bisq DAO cycle 41 with 100% approval.
		+
		+	The protocol change means trades placed from 1st January 2023 will have an important difference should the trade end in arbitration. This is as a result of the accepted proposal [https://github.com/bisq-network/proposals/issues/386 do not pay out the security deposit of the trade peer to the arbitration case winner].
		+
		+	What this means in practice is IF a trade ends in arbitration the arbitrator will only payout the trade amount plus one users security deposit. Previously they paid out the trade amount plus both user's security deposits. Therefore, traders ending in arbitration will notice the following:
		+
		+	* The arbitration 'winner' will not be compensated for the inconvenience caused by the trade going to arbitration.
		+	* The arbitration 'loser' will not be be refunded their deposit partially or in full.
		+
		+	This chance is necessary for the security of the new protocol.
		+
		+	Remember arbitration should be seen as the last resort. All efforts should be made for trader to come to an agreement with themselves or via the mediator.}}

	== Role Notes ==		== Role Notes ==

@@ Line 37: / Line 37: @@
 == Bonding ==
 [https://github.com/bisq-network/bisq/blob/master/core/src/main/java/bisq/core/dao/state/model/governance/BondedRoleType.java#L69 Bond Link]
-* [[DOA_PARAM|DOA PARAM.BONDED_ROLE_FACTOR]]
+* [[DOA_PARAM|DAO PARAM.BONDED_ROLE_FACTOR]]
 [[Category:Roles]]

← Older revision		Revision as of 05:13, 27 April 2020
Line 39:		Line 39:
	200 * [[DOA_PARAM\|DOA PARAM.BONDED_ROLE_FACTOR]]		200 * [[DOA_PARAM\|DOA PARAM.BONDED_ROLE_FACTOR]]
	[[Category:Roles]]		[[Category:Roles]]
		+	[[Category:Agent]]

@@ Line 33: / Line 33: @@
 == Rights ==
-* Write access to the <code>bisq.support</code> Keybase subteam
+* Write access to the <code>Support - Private</code> Matrix room
 == Bonding ==

@@ Line 22: / Line 22: @@
 == Issue ==
-[https://github.com/bisq-network/roles/issues/93 Refund Agent #93]
+https://github.com/bisq-network/roles/issues/93
 == Team ==
@@ Line 36: / Line 36: @@
 == Bonding ==
-[https://github.com/bisq-network/bisq/blob/master/core/src/main/java/bisq/core/dao/state/model/governance/BondedRoleType.java#L69 Bond Link]
+Not required.
-* [[DOA_PARAM|DAO PARAM.BONDED_ROLE_FACTOR]]
 [[Category:Roles]]