[bisq-network/proposals] Trading protocol change: release of funds in 2of2 multisig is signed by seller in first place. (#224)

MwithM notifications at github.com
Wed May 20 12:06:26 UTC 2020


With the objective to prevent seller from performing [future trades](https://github.com/bisq-network/proposals/issues/220#issuecomment-629582705), I propose to change the trading protocol to make seller be the first to sign the 2of2 multisig and let buyer sign the normal payout (buyer gets trade funds, both parts get their deposits back) at the end of the trade settlement.

This is how the trade protocol changes:
1. Buyer deposits +15% deposit and buyer deposits trade funds and 15% deposit.
2. Buyer sends fiat or altcoin payment to seller, press `payment sent `button ~~and provides the first signature of the 2of2 multisig tx.~~
3. Seller clicks `payment received`, ~~signing and publishing the multisig tx~~ and provides the first signature of the 2of2 multisig tx.
4. Buyer signs and publishes the multisig tx, releasing deposits and trade funds.

With the current protocol, when buyer pushes the `payment sent` button, provides the first signature of the 2of2 multisig. Even if buyer starts a dispute, seller can just sign the second signature, [overriding mediator's suggestion](https://github.com/bisq-network/bisq/issues/4162).

This proposal adds an extra step (number 4) but it makes future trading riskier as it does not allow sellers to omit mediation.
If, as proposed, buyer doesn't provide any signature when clicks payment sent, he will be able to open a dispute that will have effect. Buyer has more to loose in case of mediation after payment has been sent, so if he's the last to sign, we should expect buyer will release funds according to protocol.

-- 
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/224
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200520/7fb541b7/attachment.html>


More information about the bisq-github mailing list