[bisq-network/proposals] Encourage usage of Bonded Reputation by calculating a score for all offers (#138)

chimp1984 notifications at github.com
Tue Dec 17 17:35:36 UTC 2019


Just to make clear I NACK that proposal for above reasons. There still might be the valid use case for account age signing limit lift, but that requires more analysis.

Additional to the above reasons there are more downsides which would require clear benefit to justify a trade-off.
- It lowers anonymity set if it pushes traders to trade only between bonded users. Traders who want more privacy would get partitioned.
- We should not emphasis on marketmakers as those could impose a censorship resistence and privacy risk. Professional traders with high volumes will be treated as a business and then like centralized exchanges, so they might become subject to regulation and KYC requirements. Bisq must not follow strategies to become dependent on market makers and must not make compromises for increasing the importance of those. That said they are seen helpful for liquidity and welcome but we must not sacrifice anything to make their role in Bisq stronger.
- There are informal security mechanisms like that if an offer has a very good price that you should be suspicious (as it happens with the April scammer, he made many "too good to be true" offers). If we add "wrong signals" for security we might lower those "common sense" security mechanisms as traders would think, ah its a 5 start offer, nothing can go wrong.
- People do not read information and often do not understand much of Bisq. The risk that any display (star, or whatever) would be interpreted by users as kind of "rating" from Bisq is real. We have to avoid that. Also to explain it correctly it is a UX challenge and adds more complexity. 

-- 
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/138#issuecomment-566668327
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20191217/3537d565/attachment.html>


More information about the bisq-github mailing list