[bisq-network/proposals] Replace the role of Refund Agent with a new team of Arbitrators that can together publish one of several pre-signed 2 of 2 multisig timelocked payout transactions as proposed by a Mediator (#220)

huey735 notifications at github.com
Wed May 6 18:07:27 UTC 2020


I agree with the spirit of the proposal. The new trade protocol leads to funds being locked up longer than necessary thus affecting the liquidity. But feel like this may be over-complicating things.
We want an arbitrator/mediator role to be able to come in and solve disputes and release funds as soon as possible. And we want the possibility of publishing the following the payouts
 -- | btc-buyer | btc-seller | description
--- | --- | --- | ---
**amicable** | trade amount + security deposit | security deposit | trade goes accordingly
**amicable** | security deposit | trade amount + security deposit | traders decide to back out of the trade
**hostile** | trade amount | both security deposits | trade is successful but btc-buyer is penalized for infringing on the trade protocol
**hostile** | everything | nothing | trade is successful but btc-seller is penalized for infringing on the trade protocol
**hostile** | nothing | everything | trade isn't successful and btc-buyer is penalized for infringing on the trade protocol
**hostile** | both security deposits | trade amount | trade isn't successful and btc-seller is penalized for infringing on the trade protocol

This can be achieved by having a payout tx sent to a 2of3 multisig made up by the traders and one of these 5 arbitrators.
It is important to note that if we have the choice of arbitrator at the offer-taking step we can reduce the risk of theft by the number of arbitrators. Given that the choice is random and the arbitrators don't collude. With 5 arbitrators and a 20% security deposit the traders would have better assurances than now.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/proposals/issues/220#issuecomment-624803884
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200506/7f9fd11e/attachment.html>


More information about the bisq-github mailing list