Taproot activation meeting on IRC - Tuesday 13th April 19:00 UTC

Taproot activation meeting on IRC - Tuesday 13th April 19:00 UTC
2021-04-12 19:39 ` Billy Tetrud
  
From: BitcoinMechanic @ 2021-04-10  2:40 UTC (permalink / raw)
  To: bitcoin-dev

[-- Attachment #1: Type: text/plain, Size: 1025 bytes --]

Taproot activation meeting on IRC - Tuesday 13th April 19:00 UTC

The focus of the meeting will be ratifying the Taproot activation plan previously discussed at the March 16th meeting (aka 2021-03 Plan Y as summarized here):

https://docs.google.com/spreadsheets/d/1K3pmH09yXLTHGV3wqFZGR3ei7QVwtdEwo0PjI2NHD3w/edit#gid=0

While there was never any consensus reached on the LOT parameter, there appears to be consensus on BIP8 and the remaining parameters, and more than sufficient support for LOT=True to proceed safely.

Miners will have 18 months in which to signal and accelerate activation. If not, taproot will activate regardless.

With a majority of the economy running this it will guarantee eventual lock-in of taproot with the smallest chance of a chain split.

As a reminder, the channel is also open for ongoing discussion 24/7, and there is a web chat client here:

https://webchat.freenode.net/?channel=##taproot-activation

Best,

Bitcoin Mechanic

Sent with [ProtonMail](https://protonmail.com/) Secure Email.

[-- Attachment #2.1: Type: text/html, Size: 1852 bytes --]

[-- Attachment #2.2: image1618022427865 --]
[-- Type: image/png, Size: 6217 bytes --]

 permalink raw reply	[|nested]
2021-04-10 16:59 ` Jeremy
  
From: Michael Folkson @ 2021-04-10 16:06 UTC (permalink / raw)
  To: bitcoinmechanicca, Bitcoin Protocol Discussion

Hi Bitcoin Mechanic

I will attend but I will be looking at Core PR #21377 over the next
couple of days and I would encourage other reviewers to review that PR
too. If that PR is merged into Core I would strongly recommend any
alternative release be fully compatible with the activation parameters
in Core.

We can discuss in the meeting what we think the cut off date should be
for when Core should no longer be a consideration. Personally I think
(and hope) we will see progress on #21377 in the coming days.

For the sake of the mailing list Bitcoin Mechanic has set up a meeting
to discuss an alternative release to Core with Taproot activation
code.

Thanks
Michael

> Taproot activation meeting on IRC - Tuesday 13th April 19:00 UTC

> The focus of the meeting will be ratifying the Taproot activation plan previously discussed at the March 16th meeting (aka 2021-03 Plan Y as summarized here):

https://docs.google.com/spreadsheets/d/1K3pmH09yXLTHGV3wqFZGR3ei7QVwtdEwo0PjI2NHD3w/edit#gid=0

> While there was never any consensus reached on the LOT parameter, there appears to be consensus on BIP8 and the remaining parameters, and more than sufficient support for LOT=True to proceed safely.

> Miners will have 18 months in which to signal and accelerate activation. If not, taproot will activate regardless.

> With a majority of the economy running this it will guarantee eventual lock-in of taproot with the smallest chance of a chain split.

> As a reminder, the channel is also open for ongoing discussion 24/7, and there is a web chat client here:

> https://webchat.freenode.net/?channel=##taproot-activation

> Best,

> Bitcoin Mechanic

> Sent with [ProtonMail](https://protonmail.com/) Secure Email.


-- 
Michael Folkson
Email: michaelfolkson@gmail•com
Keybase: michaelfolkson
PGP: 43ED C999 9F85 1D40 EAF4 9835 92D6 0159 214C FEE3


 permalink raw reply	[|nested]
2021-04-10 16:06 Michael Folkson

  
From: Jeremy @ 2021-04-10 16:59 UTC (permalink / raw)
  To: Michael Folkson, Bitcoin Protocol Discussion;  bitcoinmechanicca

[-- Attachment #1: Type: text/plain, Size: 2688 bytes --]

I concur that reviewing #21377 is the best path at this time.

However, I want to draw attention to the middle road here:

If Core chooses to not release activation params (which has been discussed
as a general concept previously), #21377 can also be used to safely issue a
community release.

It's a false dichotomy between ST released by Core and a BIP8 UASF.
--
@JeremyRubin <https://twitter.com/JeremyRubin>
<https://twitter.com/JeremyRubin>


On Sat, Apr 10, 2021 at 9:48 AM Michael Folkson via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org> wrote:

> Hi Bitcoin Mechanic
>
> I will attend but I will be looking at Core PR #21377 over the next
> couple of days and I would encourage other reviewers to review that PR
> too. If that PR is merged into Core I would strongly recommend any
> alternative release be fully compatible with the activation parameters
> in Core.
>
> We can discuss in the meeting what we think the cut off date should be
> for when Core should no longer be a consideration. Personally I think
> (and hope) we will see progress on #21377 in the coming days.
>
> For the sake of the mailing list Bitcoin Mechanic has set up a meeting
> to discuss an alternative release to Core with Taproot activation
> code.
>
> Thanks
> Michael
>
> > Taproot activation meeting on IRC - Tuesday 13th April 19:00 UTC
>
> > The focus of the meeting will be ratifying the Taproot activation plan
> previously discussed at the March 16th meeting (aka 2021-03 Plan Y as
> summarized here):
>
>
> https://docs.google.com/spreadsheets/d/1K3pmH09yXLTHGV3wqFZGR3ei7QVwtdEwo0PjI2NHD3w/edit#gid=0
>
> > While there was never any consensus reached on the LOT parameter, there
> appears to be consensus on BIP8 and the remaining parameters, and more than
> sufficient support for LOT=True to proceed safely.
>
> > Miners will have 18 months in which to signal and accelerate activation.
> If not, taproot will activate regardless.
>
> > With a majority of the economy running this it will guarantee eventual
> lock-in of taproot with the smallest chance of a chain split.
>
> > As a reminder, the channel is also open for ongoing discussion 24/7, and
> there is a web chat client here:
>
> > https://webchat.freenode.net/?channel=##taproot-activation
>
> > Best,
>
> > Bitcoin Mechanic
>
> > Sent with [ProtonMail](https://protonmail.com/) Secure Email.
>
>
> --
> Michael Folkson
> Email: michaelfolkson@gmail•com
> Keybase: michaelfolkson
> PGP: 43ED C999 9F85 1D40 EAF4 9835 92D6 0159 214C FEE3
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

[-- Attachment #2: Type: text/html, Size: 4710 bytes --]

 permalink raw reply	[|nested]
2021-04-10  2:40 [bitcoin-dev] Taproot activation meeting on IRC - Tuesday 13th April 19:00 UTC BitcoinMechanic

  
From: Billy Tetrud @ 2021-04-12 19:39 UTC (permalink / raw)
  To: BitcoinMechanic, Bitcoin Protocol Discussion


[-- Attachment #1.1: Type: text/plain, Size: 1562 bytes --]

> more than sufficient support for LOT=True to proceed safely

This seems to contradict what you said about "there was never any consensus
reached on the LOT parameter". Can you clarify?

On Sat, Apr 10, 2021 at 4:13 AM BitcoinMechanic via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org> wrote:

> Taproot activation meeting on IRC - Tuesday 13th April 19:00 UTC
>
> The focus of the meeting will be ratifying the Taproot activation plan
> previously discussed at the March 16th meeting (aka 2021-03 Plan Y as
> summarized here):
>
>
> https://docs.google.com/spreadsheets/d/1K3pmH09yXLTHGV3wqFZGR3ei7QVwtdEwo0PjI2NHD3w/edit#gid=0
>
> While there was never any consensus reached on the LOT parameter, there
> appears to be consensus on BIP8 and the remaining parameters, and more than
> sufficient support for LOT=True to proceed safely.
>
> Miners will have 18 months in which to signal and accelerate activation.
> If not, taproot will activate regardless.
>
> With a majority of the economy running this it will guarantee eventual
> lock-in of taproot with the smallest chance of a chain split.
>
> As a reminder, the channel is also open for ongoing discussion 24/7, and
> there is a web chat client here:
>
> https://webchat.freenode.net/?channel=##taproot-activation
>
> Best,
>
> Bitcoin Mechanic
>
>
> Sent with ProtonMail <https://protonmail.com/> Secure Email.
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

[-- Attachment #1.2: Type: text/html, Size: 2748 bytes --]

[-- Attachment #2: image1618022427865 --]
[-- Type: image/png, Size: 6217 bytes --]

 permalink raw reply	[|nested]