[bisq-network/bisq] Provide ASIC resistant PoW scheme for BSQ swaps (PR #5858)

[Steven Barclay]

@stejbac commented on this pull request.



> @@ -769,7 +769,7 @@ message Filter {
     bool disable_api = 27;
     bool disable_mempool_validation = 28;
     bool disable_pow_message = 29;
-    int32 pow_difficulty = 30;
+    double pow_difficulty = 30;

That would possibly be OK. But on a fast CPU running the PoW search in parallel (if we made an enhancement to do that), it might take around 1 microsecond per unit difficulty or less, so a difficulty set to INT_MAX would correspond to an average search time of less that 20 minutes on a fast machine. I'm not sure we would ever want to set the difficulty that high in case of heavy DoS attack, but it would still make posting BSQ swap offers just barely usable for people with fast machines.

-- 
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/bisq/pull/5858#discussion_r762138216
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20211203/0fbc776a/attachment.htm>