-
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
Prepare Bisq for bitcoin-core v23 compatiblity #6219
Prepare Bisq for bitcoin-core v23 compatiblity #6219
Conversation
It was put there thinking it would be needed by the test harness and suites, which work fine without it, and it must be removed before API test harness can run against bitcoin-core v23. See bitcoin/bitcoin#22626 (comment)
This change is backward compatible for bitcoin-core v22. This change has not been tested against bitcoin-core v21, v20, v19. See https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes-23.0.md#p2p-and-network-changes See https://github.com/bitcoin/bitcoin/blob/23.x/doc/cjdns.md
This change needs thorough review before being merged. See bitcoin-core Issue "Remove txindex migration code #22626": bitcoin/bitcoin#22626 And comment about change not having a release note: bitcoin/bitcoin#22626 (comment) See src: https://github.com/bitcoin/bitcoin/blob/v23.0/src/txdb.cpp#L35 For API test suites: This change is backward compatible for bitcoin-core v22. This change has not been tested against bitcoin-core v21, v20, v19. Change needs to be thoroughly tested with desktop UI.
Thie test case is @disabled anyway, but run inside a suite instead, where it was not running the test daemon in debug mode (anyway).
Without this PR I see on bitcoin core version v23.0 this error:
With this PR no error is shown. |
|
Why we are removing -txindex? It seems still be available on bitcoin core v23.0. |
They are migrating away from it, and are no release notes about it. |
As I understand it, there is a legacy txindex conversion removed. There is still the new txindex in place. This seems not related to the CJDNS fix. Could you please separate the txindex change out so we can go forward with this PR. |
This reverts commit 3fe72b7. I made a mistake while testing this PR with API, and thought this txindex option was breaking the regtest BSQ wallet. The TX Index has been moved to another database, and the -txindex option is still a valid option. $ bitcoind --version Bitcoin Core version v23.0.0 $ bitcoind --help ... -txindex Maintain a full transaction index, used by the getrawtransaction rpc call (default: 0)
It's not related to the not related to the CJDNS enum fix; it was related to making Bisq compatible with bitcoin-core 23. But oops you're right, the txindex flag can stay in the seed node conf file. I reverted commit 3fe72b7, and Bisq API regtest test suite passes for bitcoin-core v23. |
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
There seem to be at least two minor adjustments we have to make for bitcoin v23:
CJDNS
enum toDtoNetworkInfo.NetworkType
, or json parsing will fail.-txindex=1
from seednode'sbitcoin.conf
.This change needs special attention from reviewers.
More detail about these two changes are in the commits.
The API test suites work with these changes, against both bitcoin-core v22 and v23, but have not been tested against bitcoin-core v21, 20, 19.
This PR needs more thorough testing with the desktop UI before merging.
Based on #6214, branch
remove-bitcoind-txindex-param
.