[bisq-network/projects] [WIP] Segwit support implementation (#42)

[Oscar Guindzberg]

> _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. -->
Implement segwit in bisq according the plan drafted in https://github.com/bisq-network/proposals/issues/226

## 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? -->
As described in https://github.com/bisq-network/proposals/issues/226 :
- Reduce btc miner fees.
- Allow users to extract btc to native segwit addresses.
- Migrate out from bitcoinj 0.14 because it is not being maintained.
- Get access to the non-segwit-related features in bitcoinj 0.15 in case a dev wants to use them in the future.
- Avoid potential malleability attacks (there is no documented feasible malleability attack to bisq, but it is good to be on the safe side)

## 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? -->
- bisq using a customized bitcoinj based on bitcoinj 0.15.8
- Users allowed to receive/extract btc using both native segwit addresses ("bc1xxxxxx") and legacy addresses ("bc1xxxxxx") 
- Trade protocol updated to use segwit.
- Bisq version with all those changes released
- Support provided after segwit support is released and activated: support users, implement hot fixes ASAP if needed. 

## 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? -->

## 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? -->

## 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. -->

## 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. -->

## Notes
<!-- Include anything else worth mentioning about this project. This section is optional and should be omitted if empty. -->


-- 
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/42
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200826/701d9fc9/attachment.html>