-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WIP] Use bisq's bitcoinj 0.15.1 #2772
[WIP] Use bisq's bitcoinj 0.15.1 #2772
Conversation
I added WIP so that it does not get merged accidentally. I will not have time soon for review and it will require a solid review. We also need to deplay soon versions with the security improvements against the scammer and i prefer to not add a big change like that in that period. Sorry for that delay, looking forward to get it in but unfortunately a bit bad timing atm.... |
Just a heads up: GitHub added Draft PRs those prevent merging. (Although you cannot downgrade a PR to be Draft, you have to start out with that.) |
Thanks. We are using that once the PR maker knows that it cannot be merged soon. In that case @oscarguindzberg did not had the information about the current priority changes so I needed to add the WIP afterwards... |
04af88a
to
a5a272d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
utACK
I leave it to @ripcurlx when to merge as it require a profound test cycle for all wallet use cases and DAO tx use cases.
I ran into the following error when launching a seednode (as a DAO full node) on regtest. It appears to be caused by updating to guava 27. We need to update btcd-cli4j to use guava 27 as well.
|
9e42c5e
to
3e1351b
Compare
I just:
Once bisq-network/btcd-cli4j#4 is merged I can update this pull request to use the latest btcd-cli4j version |
@oscarguindzberg Do you want to update the PR with the latest btcd-cli4j version before the merge? |
…eady included by bisq.
…tly() to match WalletAppKit.
… of InetAddress+port.
- WalletConfig was rewritten from scratch based on bitcoinj 0.15 WalletAppKit. - bitcoinj 0.15 allows bip32 custom paths by constructor parameters, some subclasses were removed.
…ansaction.getTxId().toString().
…inal DefaultRiskAnalysis.
3e1351b
to
1a5cf2e
Compare
@ripcurlx Just updated the PR to use the latest btcd-cli4j. I also did a rebase from master |
It's been a few months, what's the status of this PR? |
It was/is mostly ready, aside from thorough testing. It is stalled because we no longer have a bitcoinj maintainer and would be a risk to merge without one. |
I agree it seems a significant risk with no immediate benefit, even for the SegWit use case there are many other issues to consider such as how Bisq P2P clients that don't support SegWit wouldn't be able to verify those transactions - I guess it would hard-fork the Bisq P2P network ? |
I don't know if it is possible to see the version distribution, but even if we can't there is a significant difference between an updated library , implementing segwit and actually using segwit and its new adress-formats. |
bitcoinj has had some patch releases in the meantime (0.15.2, 0.15.3) I have created a branch that rebases the bisq specific changes to bitcoinj ontop of the 0.15.3 release. I am going to now try and rebase this PR ontop of bisq master and apply the 0.15.3-bisq bitcoinj version from my branch to hopeful move this work along. |
As we decided to close PRs with no activity > 30 days, I'll close this PR for now. Feel free to reopen it when it is ready to be merged again. |
No description provided.