[bisq-network/projects] Integrate Bitcoind as a wallet backend into Misq (Issue #62)

Alva Swanson notifications at github.com
Sat Dec 18 11:52:04 CET 2021


> _This is a Bisq Network project. Please familiarize yourself with the [project management process](https://bisq.wiki/Project_management)._

## Description
<!-- Briefly summarize the proposed project. Strive for one or two sentences of plain language that any user, contributor or stakeholder will understand. -->
This project integrates Bitcoind as a wallet backend into the Misq project. In Misq, we allow users to select between multiple wallets (see #52).

## Rationale
<!-- Make the case for the the project. Why is it important? Why should it be done now? What will happen if we don't do it or delay doing it? -->
In Misq, we want to break away from developing our own wallet. There are a lot of excellent wallets with which we can communicate using RPC calls.

## Criteria for delivery
<!-- Make a checklist defining the end state of the project. How will we know that the project is complete, i.e. delivered? What will exist at the completion of this project that does not exist now? What will have changed? What communications, promotions and/or documentation will exist to ensure people know about these changes? -->
This project is complete when the needed RPC calls to Bitcoind are implemented and merged into the Misq project (including integration tests).

## Measures of success
<!-- After this project has been delivered, how will we know whether it was a success? What can be measured to indicate that this project was worth the time, effort and compensation it cost? -->
We have our first full node wallet backend in Misq.

## Risks
<!-- What risks do we run by undertaking the project? What sensitive areas of code are to be modified? What negative implications might this project have on privacy, security, performance, compatibility, maintainability, user experience, etc? -->
None for the DAO. The only thing that can happen is that I fail to deliver.

## Tasks
<!-- Make a checklist defining in as much detail as is foreseeable who will need to do what in order to deliver the project. The checklist may be modified throughout the course of the project as new tasks emerge. Alternatively, once the project proposal is approved, you may choose to migrate the task checklist to a dedicated GitHub project board. -->
- [x] Bitcoind Process Manager (startup & shutdown)
- [x] RPC Connection to Bitcoind
- [x] Needed RPC calls
    - [x] `createwallet`
    - [x] `generatetoaddress`
    - [x] `getbalance`
    - [x] `getnewaddress`
    - [x] `listtransactions`
    - [x] `loadwallet`
    - [x] `sendtoaddress`
    - [x] `unloadwallet`
    - [ ] get list of utxo
    - [ ] sign a transaction 
    - [ ] Support PSBT
- [ ] Integration test for all RPC calls


## Estimates
<!-- Estimate the cost in USD of delivering this project. Indicate which teams are involved and provide subtotal estimates per team. This section need not be complete for the project proposal to be approved but must be complete for budget to be allocated. -->
I'll update this section after I'm familiar with the compensation procedure.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/projects/issues/62
You are receiving this because you are subscribed to this thread.

Message ID: <bisq-network/projects/issues/62 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20211218/707fff02/attachment-0001.htm>


More information about the bisq-github mailing list