eric at voskuil.org [ARCHIVE] on Nostr: 📅 Original date posted:2022-01-18 📝 Original message:> -----Original ...
📅 Original date posted:2022-01-18
📝 Original message:> -----Original Message-----
> From: Luke Dashjr <luke at dashjr.org>
> Sent: Tuesday, January 18, 2022 2:10 PM
> To: eric at voskuil.org
> Cc: 'Bitcoin Protocol Discussion' <bitcoin-dev at lists.linuxfoundation.org>
> Subject: Re: [bitcoin-dev] CTV BIP review
>
> On Tuesday 18 January 2022 22:02:24 eric at voskuil.org wrote:
> > The only material distinction between BIP9 and BIP8 is that the latter
> > may activate without signaled support of hash power enforcement.
> >
> > As unenforced soft forks are not "backward compatible" they produce a
> > chain split.
>
> Enforcement of the Bitcoin consensus protocol is by users, not miners.
Given that I stated "hash power enforcement" it is quite clear that this is
in fact only produced by mining. You are misrepresenting my statement to
make an emotional appeal. Without "hash power enforcement", a soft fork is
NOT backward compatible.
"[enforcement of] consensus protocol" is of course by merchants, but that is
not the question at hand. The question is explicitly compatibility. Anyone
can activate a soft fork at any time, but without "hash power enforcement"
soft forks are NOT backward compatible.
> Softforks never produce a chain split. Miners can, and might try to do it
to cause disruption in retaliation, but the softfork itself does not.
Maybe you are trying to split hairs given the fact that blocks are produced
only by miners, so only miners can "cause" a split.
But through not intention ("disruption in retaliation") whatsoever by
mining, a soft fork will result in those activating the rule being split off
the original chain unless majority hash power enforces the rule. The fact
that doing nothing apart from deploying the rule will result in a split is
the very definition of NOT compatible.
I assume you will argue that the original chain is not "valid" and therefore
irrelevant (as if no chain split occurred). But again the point is about
compatibility. The appearance of multiple chains, which appear valid
according to either the previous or new rules, is obviously the
incompatibility.
I shouldn't have to point this out, but observed chain splits have occurred
in more the one large scale soft fork deployment. These splits have only
been resolved through hash power enforcement. In 2010 it took 51 blocks
before the current chain took the lead. In 2012 minority chains persisted
for months. The deployment of soft forks caused these splits, NOT the
actions of miners. And unless majority hash power eventually enforces it,
the soft fork branch necessarily dies.
> > It was for this reason alone that BIP8 never gained sufficient
> > support.
>
> BIP 8 in fact achieved consensus for Taproot activation.
Please define "achieved consensus", because by any definition I can imagine,
this is simply untrue.
> > This is one of the most misleading statements I've seen here. It's not
> > technically a lie, because it states what "should" happen. But it is
> > clearly intended to lead people to believe that BIP8 was actually used
> > ("again") - it was not. ST was some technical tweaks to BIP9.
>
> BIP 8 was used to activate Taproot.
No, it wasn't. I find it hard to imaging how you rationalize such grossly
misleading statements.
> > The outright deception around this one topic has led to significant
> > unnecessary conflict in the community. Make your argument, but make it
> > honestly.
>
> You are the one attempting to deceive here.
That is for others to decide. I appreciate your responses above, since they
certainly help clarify what is happening here.
e
📝 Original message:> -----Original Message-----
> From: Luke Dashjr <luke at dashjr.org>
> Sent: Tuesday, January 18, 2022 2:10 PM
> To: eric at voskuil.org
> Cc: 'Bitcoin Protocol Discussion' <bitcoin-dev at lists.linuxfoundation.org>
> Subject: Re: [bitcoin-dev] CTV BIP review
>
> On Tuesday 18 January 2022 22:02:24 eric at voskuil.org wrote:
> > The only material distinction between BIP9 and BIP8 is that the latter
> > may activate without signaled support of hash power enforcement.
> >
> > As unenforced soft forks are not "backward compatible" they produce a
> > chain split.
>
> Enforcement of the Bitcoin consensus protocol is by users, not miners.
Given that I stated "hash power enforcement" it is quite clear that this is
in fact only produced by mining. You are misrepresenting my statement to
make an emotional appeal. Without "hash power enforcement", a soft fork is
NOT backward compatible.
"[enforcement of] consensus protocol" is of course by merchants, but that is
not the question at hand. The question is explicitly compatibility. Anyone
can activate a soft fork at any time, but without "hash power enforcement"
soft forks are NOT backward compatible.
> Softforks never produce a chain split. Miners can, and might try to do it
to cause disruption in retaliation, but the softfork itself does not.
Maybe you are trying to split hairs given the fact that blocks are produced
only by miners, so only miners can "cause" a split.
But through not intention ("disruption in retaliation") whatsoever by
mining, a soft fork will result in those activating the rule being split off
the original chain unless majority hash power enforces the rule. The fact
that doing nothing apart from deploying the rule will result in a split is
the very definition of NOT compatible.
I assume you will argue that the original chain is not "valid" and therefore
irrelevant (as if no chain split occurred). But again the point is about
compatibility. The appearance of multiple chains, which appear valid
according to either the previous or new rules, is obviously the
incompatibility.
I shouldn't have to point this out, but observed chain splits have occurred
in more the one large scale soft fork deployment. These splits have only
been resolved through hash power enforcement. In 2010 it took 51 blocks
before the current chain took the lead. In 2012 minority chains persisted
for months. The deployment of soft forks caused these splits, NOT the
actions of miners. And unless majority hash power eventually enforces it,
the soft fork branch necessarily dies.
> > It was for this reason alone that BIP8 never gained sufficient
> > support.
>
> BIP 8 in fact achieved consensus for Taproot activation.
Please define "achieved consensus", because by any definition I can imagine,
this is simply untrue.
> > This is one of the most misleading statements I've seen here. It's not
> > technically a lie, because it states what "should" happen. But it is
> > clearly intended to lead people to believe that BIP8 was actually used
> > ("again") - it was not. ST was some technical tweaks to BIP9.
>
> BIP 8 was used to activate Taproot.
No, it wasn't. I find it hard to imaging how you rationalize such grossly
misleading statements.
> > The outright deception around this one topic has led to significant
> > unnecessary conflict in the community. Make your argument, but make it
> > honestly.
>
> You are the one attempting to deceive here.
That is for others to decide. I appreciate your responses above, since they
certainly help clarify what is happening here.
e