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

[mpolavieja]

Ok, I think I didn´t fully understand your concerns before.  I see not that it is much simpler to use the signing as a way to simply unlock the limit of 0,01 BTC and leave everything else as it was.

The only concern there would be that a scammer colluding with a signer waits 2 months to get the highest limits as soon as the account is signed.  Now I understand the importance of a waiting period after the signing process, which is not to allow the new user to make big trades until we are more or less sure that the signing trade has not been chargebacked.

So my answer is to the question of  how to calculate the trade limits is **to keep using the account creation date**

>QUESTION: Do we want to force the signing restriction on all currencies for a high risk payment method or only for certain currencies (e.g. main markets: EUR, USD, CAD,...)?

Enforcing the signing restriction would need some kind of trusted setup to appoint signers on new markets, or to allow that accounts become signers simply by aging while there are no signers or very few signers.  Otherwise new markets could never have signers. 

So my answer to that question is that I would not force the restriction on all currencies to allow bootstraping.   However, the ideal solution would be to always make the signing in the background, but not enforcing the restriction for a currency until a minimum number of active signers exist.  But I don´t know how much dev effort it is and therefore if it is worth implementing it. 

**Question:** For main markets, under what condition are you thinking that a signed account will become a signer account?

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