[bisq-network/projects] Introduce interface between Bisq and BitcoinJ (#30)

[dmos62]

@cbeams I agree a PR example is a good idea.

The 1:1 wrap part is just to get the foundation for where to move BitcoinJ-specific logic. I.e. the refactoring happens on top of that. You'd move the logic in one set of commits (like in the sketch) and then you'd most likely simplify it in another set of commits (not in the sketch).

At first I was thinking of calling it `btc.client`, since it would handle all Bitcoin networking, but then realised that actually the `bisq.core.btc` package is our Bitcoin client, and the proposed package would be the lowest-level of that client, hence the `bisq.core.btc.low`. It's low-level in that it hides BitcoinJ logic that the rest of the `btc` package shouldn't care about and exposes the basic interface that the rest of the `btc` package will use. It makes sense to me at this point, but that might change and I don't have strong feelings either way.

-- 
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/projects/issues/30#issuecomment-630119561
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200518/90a2d878/attachment.html>