[bisq-network/bisq] Redesign dao state monitoring [4] (PR #5782)

chimp1984 notifications at github.com
Mon Nov 8 21:41:42 CET 2021


@chimp1984 commented on this pull request.



> -
-        this.isInConflictWithNonSeedNode = inConflictWithNonSeedNode.get();
-        this.isInConflictWithSeedNode = inConflictWithSeedNode.get();
-
-        String conflictMsg = sb.toString();
-        if (!conflictMsg.isEmpty()) {
-            if (this.isInConflictWithSeedNode)
-                log.warn("Conflict with seed nodes: {}", conflictMsg);
-            else if (this.isInConflictWithNonSeedNode)
-                log.debug("Conflict with non-seed nodes: {}", conflictMsg);
+    private void processPeersDaoStateHashes(List<DaoStateHash> stateHashes, Optional<NodeAddress> peersNodeAddress) {
+        boolean useDaoMonitor = preferences.isUseFullModeDaoMonitor();
+        stateHashes.forEach(peersHash -> {
+            Optional<DaoStateBlock> optionalDaoStateBlock;
+            // If we do not add own hashes during initial parsing we fill the missing hashes from the peer and create
+            // the at the last block our own hash.

Fixed

-- 
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/5782#discussion_r745076824
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20211108/85eb3b5f/attachment.htm>


More information about the bisq-github mailing list