[bisq-network/proposals] Adjust parameters for JPY order book to reduce friction for new users (#98)

mpolavieja notifications at github.com
Thu Jun 13 07:54:33 UTC 2019


> 2. Reduce the minimum security deposit to 0%, and make the default 0%

I think this combined with no BTC trade fee for the buyer would be very interesting not only for BTC/JPY but for all markets.  I was refraining from proposing this because there many other important things that need to be implemented and developers is an extremely scarce resource, but since more or less it's been brought up, I´ll briefly describe my proposal regarding this:

**No security deposits and no seller´s BTC locking for small quantities (< $30 or $50)**

This could work for f2f and also for bank transfer payment methods, for the latter only sellers with high fiat account age would be allowed for this trades, so they risk their bank payment bank account to be banned from Bisq if they misbehave.  The seller would not release his BTC until the buyer sends the money first.   The BTC could be sent outside Bisq, so SegWit or LN could be used.

For bank transfers, since the seller already has a "reputation" (old account) he could optionally require the buyer a very small down payment ($5 or $10) through an easy and fast method such as Paypal or Venmo *before engaging on the trade*, to ensure he does not lose the maker trading fee (if finally there is any).  This would require communication between traders.   

To cover the maker trading fees (if any) and the mining fees (if any), the seller could mark-up the BTC price of the transaction in order to cover those costs.

All the above would help a lot bootstrapping markets, and it would lower the barrier of entry for buyers that don´t have BTC, which I think it is important for Bisq as a fiat on ramp. 

This type of small trades with "trusted" BTC sellers would not have security deposits, but in general for all other trades I agree with @flix1 not to make the default security deposit 0%

-- 
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/98#issuecomment-501592894
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20190613/5e1eb151/attachment-0001.html>


More information about the bisq-github mailing list