[bitcoin-dev] Yet another Taproot activation logic

Carlo Spiller carlo at spiller.com
Sun Mar 7 09:58:30 UTC 2021

Hi everybody

I'm new to this list, but not new to Bitcoin, having skin in the game 
since 2014. I was there for the scaling war and the drama around SegWit, 
as a simple user. This time, I run my own full node and follow 
development. I hope to bring something new to the table.

Having witnessed the miner's unwillingness to activate SegWit truly 
makes me concerened for a simple LOT=false. After reading the discussion 
now for some time and thinking about it myself, I have come to the 
following proposal.

Initially deploy with LOT=false and an activation threshold of 95% of 
miner signaling.

*IFF* after 6 months Taproot is not activated by MASF, BUT at least 80% 
of hashpower signaled for the upgrade, LOT gets a lock-in date another 6 
months later and the threshold for MASF is lowered to 90%.

If after the initial 6 months of signaling with LOT=false, 80% is not 
reached, the proposal expires.

This way, a small percent of hashpower does not get to stall activation, 
rather, 80% of hashpower can activate LOT=true, and later, 90% can 
activate Taproot. If a flaw is found in Taproot in the first six months 
(unlikely anyway), miners simply don't signal and the proposal expires. 
If miners don't signal at all, only six months are lost, before a new 
activation logic can be deployed.

Don't mind this if something similar was already proposed somewhere else.



More information about the bitcoin-dev mailing list