[bisq-network/proposals] Develop a network of Bisq merchants by adding conditional orders (#123)

MwithM notifications at github.com
Sat Sep 28 10:50:57 UTC 2019


After taking a look to Bisq v2 and the new trading protocol where there's only bonded BSQ instead of BTC multisig deposits, I think that the conditional orders for merchants could be easy to implement.

### OFFER CREATION

There's 3 agents involved in this trade: seller, buyer and store.
Store creates conditional offer to sell 0.1btc that will be displayed only if there's a selling offer for bank transfer of 0.1btc.
Seller creates and offer to sell 0.1btc at $1.000 via bank transfer. Store displays a conditional offer to sell 0.1 btc at $1.030 (3% premium).
Buyer accepts store's conditional offer at $1.030.

### BONDING

Store and seller needs to lock 125% of the trading amount in BSQ bonds, equal to 1.287.5$.
Buyer locks 50% of the trading amount, $515.

### PAYMENTS

As cash payments are very hard to verify, buyer needs to be the first to pay, at store. When the $10.300 payment is made, buyer needs to be sure that store clicks "payment received" button, that will trigger an alert to buyer's Bisq app. Buyer can now walk home to wait for BTC payment, which will be sent to an address communicated via Bisq chat to seller, or to Bisq client when accepting the sell offer.
Seller will be alerted too that the F2F payment has been made. At this moment, seller can make 0.1 BTC payment to buyer. Due to bonding, there's no need to wait to receive store's bank transfer of $10.000.
Store will make the $10.000 bank transfer to seller ASAP.
Only these info needs to be shared:
- Buyer's BTC address to seller.
- Seller and store bank transfer details between each other.

### TIME LIMITS

Buyer will have 2 labour days to pay at store. When the "Payment Received" button is clicked, a new timecount will be started, giving 5 days for the bank transfer to arrive to seller. Different time limits should be used for different payment mehtods. Seller will have 48 hours to make BTC payment. Seller and buyer need to confirm payment received with their Bisq client.

### WHAT IF (MEDIATION)

Buyer doesn't go to store: lose BSQ bond, equalling $515. Store and seller doesn't have to send any payment, as the trade is cancelled. Both should be compensated.
Seller doesn't pay 0.1 BTC to buyer: seller lose BSQ bond, equalling $1287.5. Buyer should be compensated.
Store doesn't pay $1.000 bank transfer to seller: store lose BSQ bond, equalling $1287.5. Seller should be compensated.

BTC and bank transfer payments are easy to verify, and chargebacks are being prevented. Weak point is cash payment. As in the current F2F protocol, if Bisq doesn't have clear reasons to act in a certain way in case of dispute (like police reports and judge statements), store and buyer could lose their bonds. Store needs to verify that there's no counterfeit bills and buyer needs to know that the "payment received" button has been clicked. This method have some advantages compared to a F2F public place meeting: store usually has already computers to run a Bisq node, own security measures, and is very used to receive cash payments. Millions of cash payments are made every day and counterfeit bills are still rare, and going to the baker, paying your cents and not receiving your bread is even stranger. Stores usually need reputation and that runs to our favour.
Store doesn't have to keep BTC anywhere, buyer doesn't have to bring btc or laptop, so this prevents from robbery. Online smartphones are very common for most of the countries. For those who don't, a Bisq certificate could be printed at the store as a receipt, but I don't know a cryptographic way to prevent this paper from being falsified.



-- 
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/123#issuecomment-536175721
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20190928/8d0b7194/attachment-0001.html>


More information about the bisq-github mailing list