[bisq-network/proposals] Enable face to face (F2F) trade in Bisq (#24)

[Manfred Karrer]

I have an additional idea how to avoid the requirement that both traders bring their laptop to the meeting.
We could add a small feature to the Bisq mobile app (is close to completion state) where the BTC buyer can verify a code the seller hands him over.
That code acts like a signature that the BTC seller states that he has received the Fiat. Back at home he need to unlock the BTC at the trade and if not the buyer could present the code to the arbitrator and the arbitrator can verify that the code was correct. The buyer has no way to get the code beside that the seller gives him the code.

The code gets generated at the sellers app and the hash of the code will get included in the trade contract and sent to the buyer. At the meeting after the fiat has handed over the seller need to give the code to the buyer as kind of statement that he has received the Fiat. The buyer can verify the code by scanning the QR code (the seller can print it out or has it on the mobile app). The mobile app will receive the hash of the code when the trade starts and will calculate the hash when the seller presents the QR code and then compare that calculated hash with the one from the trade contract. If it matches the buyer has a secure proof that the seller has confirmed receipt of the fiat.

The usage of the code is optional, if both traders or at least the seller brings his laptop he can release the BTC directly as well. The buyer could press the payment started button before he goes to the meeting, so no need to bring his laptop. He can verify the payout tx at any block explorer on his mobile as well.  

-- 
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/24#issuecomment-406693836
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20180720/6b63b23c/attachment.html>