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

[jmacxx]

I will devote up to 1 month on this and my estimate for cost would not exceed $8000.  If my deliverable is not up to standards the DAO can decline my compensation request.

I will deliver progress reports twice a week posted to this thread so that:

-   (a) it keeps me focused on results,
-   (b) if I get stuck or go down a wrong path suggestions can be made.


Plan of work:
- Identify actions that a generic blockchain/wallet module has to fulfil => document.
- Write a document detailing what existing Bisq would need to change to adapt using the generic wallet module => this work would also help define the scope of a generic wallet module.
- Look at the potential blockchains/wallets to be supported and how they can be abstracted by a generic module interface => document each.
- Produce a functional prototype of the most promising solution which shows how the various use cases are handled.
- Adapt the prototype to a different wallet/chain backend, thus showing how it fulfils the requirement.
- Any lessons learnt from the prototyping can be applied back to the design doc/RFCs.
- Investigate what potential issues if a wallet/technology does not support spending chained unconfirmed transactions.

My intention is that prototypes would feature heavily as supporting evidence to the final deliverables.


-- 
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-830103050
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20210430/b3b6a0e4/attachment-0001.htm>