[bisq-network/proposals] Include an option to restrict offers from being taken by non-signed accounts (#133)

[mpolavieja]

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

### Problem description

It should be obvious that new users that come to Bisq to buy 0,25 BTC or more don´t really want to make 25 or more transactions as that would be prohibitively expensive and time consuming.  If those users I am referring to are posting offers to buy 0,01 BTC, it is very likely that they post them in order to get their account signed. 

If their offers are taken repeteadly by non signed accounts, that could be quite frustrating.  It could be a rather serious onboarding barrier as it would be a waste of time and fees for the new user.  Moreover, having a lot of small transactions might be also an issue with the bank.  Might be too noisy.

### Suggested solution

Provide the **option** to makers to restrict their offers so they can only be taken by signed accounts.  The risk of siloing liquidity amongst old users is very low, as it is unlikely that old signed users post offers as low as 0,01 BTC to trade only with signed accounts.   And if old users restrict their sell offers of 0.06, 0.12 or 0.25 BTC, the buyers that have the limits to take those offers are probably already signed, specially on the long run.

I suggest to include this option as a checkbox in the create offer screen and that it is always disabled if the account is already signed.  If the account with which the offer is being created is unsigned, I am not sure if it should be enabled by default.  If it is enabled by default it will make things easier for the new user.  If it is disabled by default, a pop up would be necessary to explain the user that he can enable that checkbox if he wants to get his account signed quicker (not to waste time and fees).

-- 
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/133
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20191103/8402ac1d/attachment.html>