[bisq-network/projects] Specify interface and architecture for wallet and blockchain data modules (#52)

jmacxx notifications at github.com
Sun May 23 17:02:09 CEST 2021


What remains, from my point of view:

- IMO there needs to be the concept of `capability` in the interface so that Misq knows if a provider can be used for what kind of trading methodologies (not all chains and not all wallet providers can satisfy the advanced use cases).
- Produce a design. (a generic interface handling different implementations while being able to satisfy various use cases: normal transfers; unsecured trading; escrow; timelocks).  The prototypes can be considered a rough design, but I thought you had asked for a RFC document.  I would expect to take 2 days creating it.
- You mentioned [focus on bitcoind and electrum](https://gist.github.com/jmacxx/587ac9a59d7d060b4f9fdf37fa9cc8ef#gistcomment-3753359); however I think we also need to provide a third option: BitcoinJ exposed thru the same generic interface.
- If using electrum for trading with escrow we'll need something that helps construct the transactions (i.e. getting the scripts/keys/addresses all sorted out).  A library - currently we use BitcoinJ for that.

Lets discuss in tomorrow's meeting.


-- 
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/52#issuecomment-846576963
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20210523/60988247/attachment.htm>


More information about the bisq-github mailing list