Luke Dashjr [ARCHIVE] on Nostr: 📅 Original date posted:2021-03-02 📝 Original message:On Tuesday 02 March 2021 ...
📅 Original date posted:2021-03-02
📝 Original message:On Tuesday 02 March 2021 18:22:35 Ariel Lorenzo-Luaces via bitcoin-dev wrote:
> I'm realizing that a clear advantage of LOT=false is that it can happen
> without the need for a social movement. All that is really needed is the
> convincing of 95% miners. Apathetic users will never notice any kind of
> service disruption no matter the success or failure of the activation. This
> is obviously why it naturally became the default activation method.
No. Miners enforcing rules without the social support is a 51% attack, not a
softfork.
> While LOT=true, on the other hand, must be able to 51% the blockchain to
> win the apathetic users. But then the reorgs will not be pretty. Or if it
> ever clearly gets over the 51% hurdle then all apathetic users now need to
> scramble to use the rogue client to be safe from reorgs. Either way it's
> disruptive.
No, LOT=True doesn't do this. It only happens if miners choose to create an
invalid chain, which they could do at any time with or without a softfork
involved.
Luke
📝 Original message:On Tuesday 02 March 2021 18:22:35 Ariel Lorenzo-Luaces via bitcoin-dev wrote:
> I'm realizing that a clear advantage of LOT=false is that it can happen
> without the need for a social movement. All that is really needed is the
> convincing of 95% miners. Apathetic users will never notice any kind of
> service disruption no matter the success or failure of the activation. This
> is obviously why it naturally became the default activation method.
No. Miners enforcing rules without the social support is a 51% attack, not a
softfork.
> While LOT=true, on the other hand, must be able to 51% the blockchain to
> win the apathetic users. But then the reorgs will not be pretty. Or if it
> ever clearly gets over the 51% hurdle then all apathetic users now need to
> scramble to use the rogue client to be safe from reorgs. Either way it's
> disruptive.
No, LOT=True doesn't do this. It only happens if miners choose to create an
invalid chain, which they could do at any time with or without a softfork
involved.
Luke