Update Bitcoin core?

[panicfarm]

As I understand, the bitcoin core version in the dependencies is currently 0.20? That is pre-taproot. When do you plan to update to a more modern version, such as 0.25, that includes taproot?

[tcharding]

I can push this up my todo list for you. I can't remember what happened before when I tried but I know I got stuck

#42

[panicfarm]

I can push this up my todo list for you. I can't remember what happened before when I tried but I know I got stuck

#42

It would be great to get this updated, but I do not understand why the latest bitcoinconsensus lib still doesn't have Taproot (we need taproot). Aren't they compiling it from the same bitcoin core code, that has had taproot since 0.22?

[tcharding]

cc #68

[panicfarm]

Question: It seems that the current libconsensus doesn't have taproot support, they are still working on it. Isn't libconsensus from bitcoin core compiled from the same code as the core itself? Core had taproot since 0.22. Which version are you going to vendor?

cc #68

[tcharding]

I can't talk for how Bitcoin Core dev works, no clue why bitcoin/bitcoin#21133 has a merge date of October 17 this year?

Which version are you going to vendor?

My intention, and I don't speak for the whole project but just what I have in mind, is to upgrade this lib to the newest version of Core and then, on the way, maintain an LTS for the last 4 versions.

[apoelstra]

I don't speak for the whole project

This sounds great to me. Thank you for spearheading this and let me know how I can support.

[tcharding]

If you can just review and smash out the releases then I think we can get there pretty quick (assuming the vendoring script in #70 is correct).

[panicfarm]

I can't talk for how Bitcoin Core dev works, no clue why bitcoin/bitcoin#21133 has a merge date of October 17 this year?

Here's the answer . Looks like it's finally there?

[tcharding]

Thanks man, lets keep pushing then to get this lib up to the current version of Core quick as we can.

[Davidson-Souza]

26 released taproot on libbitcoinconsensus. If we want taproot we need to go straight to 26. Any reason why we need to do previous releases?

My intention, and I don't speak for the whole project but just what I have in mind, is to upgrade this lib to the newest version of Core and then, on the way, maintain an LTS for the last 4 versions.

Strong Concept ACK. Let-me know if you need some help.

Edit: link to 26's release notes with:

A new bitcoinconsensus_SCRIPT_FLAGS_VERIFY_TAPROOT flag is available in libconsensus that will verify scripts with the Taproot spending rules.

[panicfarm]

I would suggest going straight to 0.26 with Taproot . This is the main reason why we, for example , need the crate update. Evidently 0.25 did not include taproot

[apoelstra]

26 released taproot on libbitcoinconsensus. If we want taproot we need to go straight to 26. Any reason why we need to do previous releases?

For completeness, and to practice our new vendoring scheme.

We should be able to bang out every release within a day or two once we get our process working and when it stops being the Christmas/New Year week.

[panicfarm]

Do you guys have any ETA on the release vendoring v26 core with taproot support?

[tcharding]

No ETA but we can push a bit harder. It should be trivial now to get to v25 then the 26 release will take a bit of work to add the two new arguments to verify_script.