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
lib: add taproot support to libconsensus #28539
lib: add taproot support to libconsensus #28539
Conversation
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers. Code CoverageFor detailed information about the code coverage, see the test coverage report. ReviewsSee the guideline for information on the review process.
If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update. ConflictsReviewers, this pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first. |
2f500da
to
a5edeca
Compare
cc @darosior |
Yay, concept ACK. Thanks for picking this up. Do you plan to address #21158 (comment)? Is this why you opened this as a draft? |
Yes! |
a5edeca
to
8b3ca44
Compare
8b3ca44
to
47f96cc
Compare
47f96cc
to
83ac8c7
Compare
Ready for review! |
83ac8c7
to
61cf259
Compare
Force-pushed addressing #28539 (comment) and changed the type of |
61cf259
to
f5cd559
Compare
Addressed #28539 (comment) |
8c3bf6e
to
36d77cb
Compare
CI failure seems unrelated: Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package linux-headers-6.2.0-32-generic
E: Couldn't find any package by glob 'linux-headers-6.2.0-32-generic'
E: Couldn't find any package by regex 'linux-headers-6.2.0-32-generic'
Retries exhausted
Error: building at STEP "RUN bash -c cd /ci_container_base/ && set -o errexit && source ./ci/test/00_setup_env.sh && ./ci/test/01_base_install.sh": while running runtime: exit status 100
Exit status: 100 |
Jup, this particular CI failure can be ignored. It should also fix itself on the next push. |
Co-authored-by: Bruno Garcia <brunoely.gc@gmail.com>
Co-authored-by: Bruno Garcia <brunoely.gc@gmail.com>
…puts` Co-authored-by: Antonie Poinsot <darosior@protonmail.com>
36d77cb
to
ff8e2fc
Compare
Force-pushed: rebased and addressed #28539 (comment). |
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.
ACK ff8e2fc
Some follow-up thoughts: on the long-term, I think it would be very nice to have a test that interacts with the libbitcoinconsensus shared library (i.e. .so
/.dylib
/.dll
file, depending on the OS used). This should be doable in form of a functional test without any extra dependencies using Python's ctypes
module, IIUC: https://docs.python.org/3/library/ctypes.html
However, I didn't manage to even build a shared library so far. Do we still support this in the build system? ./configure --enable-shared
doesn't do anything on my side (tested on Ubuntu 22.04), I keep getting checking whether to build shared libraries... no
from the configure script.
ACK ff8e2fc |
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.
re-ACK ff8e2fc
@@ -0,0 +1,5 @@ | |||
Tools and Utilities |
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.
Probably better to use the actual PR number next time?
A naive question (I am a Rust developer, not a C++ Core dev): taproot soft fork has been in the bitcoin core code since 0.22. But even at the 0.25 release, libconsensus still does not have taproot support. Isn't libconsensus compiled from the same source as the core binary itself, albeit as a shared library? If this is so, I am confused why it has not had taproot support since 0.22? |
@panicfarm libconsensus had certainly contained all the logic for taproot validation ever since Bitcoin Core had it, but it was not exposed through the library interface, for two reasons:
|
Grabbed from #21158. Closes #21133.