[bisq-network/proposals] [WIP] UI of trust (for fiat trades) (#80)

Christoph Atteneder notifications at github.com
Thu Apr 25 15:16:02 UTC 2019


> _This is a Bisq Network proposal. Please familiarize yourself with the [submission and review process](https://docs.bisq.network/proposals.html)._

To make it as painful as possible for scammers to use Bisq for turning stolen bank accounts into BTC following proposals are in discussion right now:
- [Delay payout for Fiat trades if buyers account is fresh](https://github.com/bisq-network/proposals/issues/77)
- [Distributed reputation system](https://github.com/bisq-network/proposals/issues/78)
- [Self certification of bank account details using ID verified digital certificates](https://github.com/bisq-network/proposals/issues/79)

This proposal should discuss how we communicate these anti-scam strategies from a UI perspective. The UI should be flexible enough to support additional strategies that will be implemented in the future and should hide the complexity as much as possible to the user. Still it shouldn't give the user the false sense of security at the same time. 

We could hide the complexity of the different anti-scam strategies by splitting it up into:
- a general **trust score** (0%-100%)
  0% new account, 100% fulfilling all conditions currently defined. If we introduce new conditions in the future the current score can be reduced again until the new condition is fulfilled as well.
- a delayed payout indication

To tackle this problem I think it makes sense to look at this problem from two sides:
- The **seller** side (how can I prevent getting scammed and still trade fast)
- The **buyer** side (what do I have to do to be able to trade fast and how to get started with Bisq as a new users)

## BTC Seller

To be able to prevent getting scammed I want to be able to:

**As a maker:**
- define maximum risk I'm willing to take (minimum trust score)
- define time frame of delayed payout I'm willing to accept (maker deposit might be locked up for max. 31 days)

**As a taker:**
- see the trust score of an offer before taking it
- see the expected delay until my deposit gets unlocked again

## BTC Buyer

As the risk being scammed as a buyer is nearly zero, the use-cases for a buyer are more about how to increase their trust score and to reduce the time until payout.

To increase my trust score I should start trading as soon as possible. For that I should create accounts for all my payment methods I might want to use in the future right now to start account aging. I need to understand that there is no total risk score for my onion address or me as a user, but a different risk score for each of my payment methods.

**As a maker:**
To increase the probability of my offers to get taken I can:
- lock-up a high security deposit (up to 50% of trade amount for fiat trades)
- define an amount range with a low minimum to get my first offer accepted as soon as possible (relevant for https://github.com/bisq-network/proposals/issues/78)
-  unlock this restrictions immediately by self certification (https://github.com/bisq-network/proposals/issues/79) or locking up a BSQ bond (https://github.com/bisq-network/proposals/issues/32).

**As a taker:**
The buyer is dependent on the limitations set by the seller.

## User flows to be changed
- Payment account creation
- Create offer
- Take offer

Although this proposal is WIP it is important to get feedback especially on terminology (trust score,..) and the different use cases as soon as possible so we are not missing anything essential or failing to communicate it properly. I'll update this proposal with screenshots and more detailed concepts for each section over the next couple of days.


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


More information about the bisq-github mailing list