[bisq-network/proposals] N-factor counterparty confidence mechanisms (#83)

Steve Jain notifications at github.com
Wed May 8 11:06:52 UTC 2019

> verification should always be done at payment account level

Agree. But I'm starting to think blocking could happen at the onion-address level...no need for users to put with a scammer's other bad accounts. Maybe the UI could suggest addresses to block in real-time based on signed payment accounts, and every software release could include an updated blacklist.

> CouldnĀ“t it be possible to store locally a whitelist of trusted payments accounts?

That's exactly what I'd like to see.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20190508/b628a6d6/attachment.html>

More information about the bisq-github mailing list