Post A4kDgsa2yyecAzwuSO by GunnarStoedle@bitcoinhackers.org
 (DIR) More posts by GunnarStoedle@bitcoinhackers.org
 (DIR) Post #A4k9wOGV3uTIyJwlpA by lukedashjr@bitcoinhackers.org
       2021-02-28T20:20:05Z
       
       0 likes, 1 repeats
       
       "LOT=False is dangerous and shouldn't be used"https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-February/018498.html
       
 (DIR) Post #A4kDgsa2yyecAzwuSO by GunnarStoedle@bitcoinhackers.org
       2021-02-28T21:02:07Z
       
       0 likes, 0 repeats
       
       @lukedashjr Hmm interesting. Thanks for this Luke! Good practical point ""Yep, I upgraded for Taproot(eg). Wait, you mean I have to do it AGAIN?" The added mess and confusion of LOT=false as default may defeat the purpose.
       
 (DIR) Post #A4kYXIm0qC4LYPouwK by stevenroose@x0f.org
       2021-03-01T00:55:38Z
       
       0 likes, 0 repeats
       
       @GunnarStoedle @lukedashjr The setup of lot=true in BIP 8 would mean that if enough people run lot=true, they will force activation signaling so that lot=false users will also see taproot activated on the same chain.What you're saying about potentially having a rough 2 weeks (or 4 if hashrate is split) of swapping between forks also counts for all un-upgraded nodes. There's a simple remedy: don't use taproot yet. For all other usages, your txs will confirm on either chain.#bitcoin #taproot
       
 (DIR) Post #A4krcGhhrQLViFt6vY by lukedashjr@bitcoinhackers.org
       2021-03-01T04:29:30Z
       
       0 likes, 0 repeats
       
       @stevenroose @GunnarStoedle The chaos only happens if miners attack the old+False nodes. In the normal activation path, all the nodes work fine.