Strategy on Bitcoin consensus forks
taxmeifyoucan opened this issue · comments
With the current discussion about deploying Taproot, I am interested how Umbrel will handle policy for consensus. I believe your users are already significant part of the network and might have different preferences. Will you include Taproot? Will it be LOT=true or LOT=false, or maybe possibility to choose between them?
Thanks for you work guys!
I would suggest ASAP inform users of node what Taproot is, what is LOT signalization good for and how to use it.
I think a simple plugin or feature in the main interface signaling LOT as user wants will be nice.
Also a way to update the node in the way user want to run his node will be fair.
Looks like there's a lot of support to drop LOT=true/false entirely in favor of Speedy Trial (bitcoin/bitcoin#21377) for the Taproot upgrade.
In the long term, we don't want to be in a position to call shots on behalf of our users in case of a network fork/upgrade. Today, Bitcoin Core is tightly coupled with Umbrel and all of its updates are shipped as a part of Umbrel updates. But eventually, Bitcoin Core will move to the Umbrel App Store as an individual app and receive its own updates independently from the Umbrel updates, and it will be on the user to tweak its configuration options.
We'll also encourage multiple Bitcoin Core apps maintained by different developers in the Umbrel App Store to provide more implementation choices (so there could potentially be an official Bitcoin Core app from the core devs, co-existing with community-packaged Bitcoin Core apps, etc).