How can we support activation of Taproot through out Umbrel bitcoin node?
8 Likes
I have exactly the same question. Is there anything we can do with our Umbrel Bitcoin Full Node ? Do we have the ability to choose which software version we want to run ?
No you can’t. The team behind Umbrel will probably just go with the last version of Core so that mean you will support the activation of Taproot by default.
4 Likes
Thanks for your answer. Would be great to have a confirmation from the team.
yep, @Seccour is right. the client used in umbrel is bitcoin core so we’ll continue to stick with it and update it to bitcoin core v0.21.1 when it’s out (which uses speedy trial)
12 Likes
Thank you ! Very good news ! You guys really rock !
2 Likes
6 Likes
@lukechilds out of curiosity: where do you get the sha256 checksum from? if I compare the sums on dockerhub with the one added in the commit (docker-compose.yml) there’s no match. the checksums are arch-dependent on the hub.
1 Like
Each image has it’s own checksum, of which there are one for each arch.
Then there is a multi-arch manifest, which links to each image, which also has it’s own checksum.
We pin against the checksum of the manifest, otherwise Umbrel would only run on a single arch.
You can check this by just doing docker pull $image and it’ll log the manifest checksum on completion:
$ docker pull lncm/bitcoind:v0.21.1
v0.21.1: Pulling from lncm/bitcoind
Digest: sha256:5bedb46d698de16c59e9e43d31485d0d82239bd437d62ac7cf47ebb633214f37
Status: Image is up to date for lncm/bitcoind:v0.21.1
docker.io/lncm/bitcoind:v0.21.1
3 Likes
5 Likes
Were you able ti send from umbrel to taproot address ?