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

[MwithM]

>And the seller also doesn't have an opportunity to revoke a payment or overdraw it.

If Bisq used a stablecoin instead of a high volatile currency like BTC, this proposal would not be necessary.

My proposal missed on explaining different scenarios:

1. Buyer doesn't pay: seller demands mediation, gets a part of buyer's deposit, and his deposit + trade funds. In this point, buyer not pushing
2. Buyer pays but protocol has been violated by buyer (i.e. invalid reason of payment):  seller demands mediation, gets a part of buyer's deposit, and his deposit + trade funds. At this point, buyer not pushing the "payment sent" button doesn't makes much sense, because he already paid and want the btc to be released.
3. Buyer sends a valid payment but seller doesn't confirm reception: buyer demands mediation, gets a part of seller's security deposit + trade funds, and his security deposit. At this point is where the proposed change makes effect: before, seller could delay to push the "payment received" button until timelock activation, as he already had 1/2 of the signatures required.
4. Buyer gets the notification that seller has pushed "payment received" button: if he makes the second signature, he gets trade funds + security deposit and seller gets security deposit. As buyer likes to get trade funds and security deposit the sooner as possible and has more to lose than seller, he has incentives to release the multisig funds as soon as possible. At this point, requiring mediation would only make sense if seller pushed "payment received" exceeding the trading period. In that case, buyer could receive a big part of seller's security deposit.

Is future trading still possible? Yes, but risk is higher. Now buyer can open mediation and seller will lose a big part of the security deposit (which, by the way, could be optionally higher than 15% in case buyers want higher protection from volatility).

-- 
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#issuecomment-635813592
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200529/7809992c/attachment.html>