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

Christoph Atteneder notifications at github.com
Mon Jun 24 12:52:19 UTC 2019


> 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.

The idea was to provide arbitrators with an interface to sign account age witnesses that fulfill following conditions:
- Account age witness date is before selected date (e.g. 1st of March)
- Of selected payment account type (e.g. SEPA)
- Was in a dispute with following condition: buyer received BTC (fiat was successfully transferred)

So we should be quite sure that we only sign accounts that had real trades.
Arbitrators could run this signing again and again as it should only sign account age witnesses without a signed witness.

For bootstrap markets where the signing is not required yet, arbitrators can also sign accounts whenever they like. As soon as we have sufficient signed accounts or based on other metrics we can decide to force the market to require signed accounts after a certain date (similar as we do it now with the 1st of March rule).

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

After being signed the tolerated small trade amount of 0.01 BTC gets lifted 30 days later and the account will be able to sign other accounts x days (e.g. 60 days?) after the signing date.

What do you think?

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


More information about the bisq-github mailing list