[bisq-network/proposals] Implementation of protection tools: strengthening Account Age by requiring payments from 2 Bank Accounts (#93)

mpolavieja notifications at github.com
Fri Jun 7 09:09:43 UTC 2019


> Not sure if it is worth to implement this properly as we still have the amount limit (0.02 BTC) for unsigned accounts anyways. @mpolavieja What do you think?

But while 2FA is not implemented or when implemented is optional and single payments are still valid for account aging, what worries me a lot more than the quantity, is that if this happens it is very likely that active traders and market makers are the ones going to get hit.   The risk is that the bank closes the market maker account, so Bisq loses a big chunk of liquidity. 

So the best we can do is deter as much as possible the scammers to try it.  That is, that they feel that it will be extremely difficult that the signer is going to sign quickly (2FA, if not 2FA the signer will wait, etc).

>We could do that, but it is an additional challenge for the UI as it might cause some confusion on the buyer side if a signed account doesn't sign their account within the trade.

Yeah.  If this soft-limit is enforced the buyer should be informed that his account is still unsigned because not enough time did elapse from payment sending to confirmation and be advised to send the payment as quickly as possible on the next trade if he wants to get signed.   But yeah, it is bad UX, we should discuss if it is worth it.

IMO, **the most important risk to control is that a scammer does not become a signer**.  So we need to rely on signers reacting quickly and opening a dispute if they have a chargeback with a new account.  I´ll open another GitHub issue for that (You mean a proposal, right?).

-- 
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/93#issuecomment-499814482
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20190607/0eb6fc22/attachment.html>


More information about the bisq-github mailing list