[bisq-network/bisq] Remove CapabilityRequiringPayload from NewBlockBroadcastMessage (#3250)

[chimp1984]

We remove the CapabilityRequiringPayload interface to avoid risks
that new BSQ blocks are not well distributed in case the capability is
not exchanged at the time when the message is sent. We need to improve
the capability handling so that we can be sure that we know the actual
capability of the peer.
You can view, comment on, or merge this pull request online at:

  https://github.com/bisq-network/bisq/pull/3250

-- Commit Summary --

  * Remove CapabilityRequiringPayload from NewBlockBroadcastMessage

-- File Changes --

    M core/src/main/java/bisq/core/dao/node/messages/NewBlockBroadcastMessage.java (17)

-- Patch Links --

https://github.com/bisq-network/bisq/pull/3250.patch
https://github.com/bisq-network/bisq/pull/3250.diff

-- 
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/3250
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20190912/1e114b42/attachment.html>