[bisq-network/proposals] Segwit support plan (#226)

[dmos62]

To add to what @chimp1984 said about handling backwards compatibility and migration under "Tools for dealing with backward compatibility", BitcoinJ 0.15.7 got service bit filtering for DnsDiscovery [0], (which is capabilities filtering you mentioned) letting you not connect to incompatible peers for example. Further, we can already check each peer's service bit and version; it's only a matter of wiring that information through to where we need it. We can even disconnect a peer if we don't like its service bit (simulating the mentioned new feature in 0.15.7), but it's not as neat as doing it on DnsDiscovery's level.

Even now BitcoinJ is still limited in how well it can discriminate peers (service bit filtering is not version filtering for example). We can expand BitcoinJ's facilities for our migration plans (and general robustness) if needed. I think that will often be preferable to doing something elaborate Bisq-side (like implementing parts of Bitcoin handshake on top of trade messages).

[0]  https://bitcoinj.github.io/release-notes#version-0157

-- 
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/226#issuecomment-633455668
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200525/37c298fe/attachment.html>