public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Michael Folkson <michaelfolkson@gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: [bitcoin-dev] Taproot activation meeting on IRC - Tuesday 2nd February 19:00 UTC
Date: Fri, 22 Jan 2021 12:01:37 +0000	[thread overview]
Message-ID: <CAFvNmHS4s_MbXP8o3kWmaUZ5Xks1b76jSDymp1Bjr--4R8_v3Q@mail.gmail.com> (raw)

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

There has been an incredible community effort to make progress towards
consensus on an activation method for the proposed Taproot soft fork.


Special mentions go to David Harding, AJ Towns, Aaron van Wirdum, Jonathan
Bier, Ben Carman, Alejandro De La Torre whose resources are linked below
but there have been many others, too many to name, who have all made an
impact on moving the needle in recent months.


Taproot activation proposals:
https://en.bitcoin.it/wiki/Taproot_activation_proposals


Activating Soft Forks in Bitcoin:
http://www.erisian.com.au/wordpress/2020/10/26/activating-soft-forks-in-bitcoin


BIP 8, BIP 9 or Modern Soft Fork Activation: How Bitcoin Could Upgrade
Next:
https://bitcoinmagazine.com/articles/bip-8-bip-9-or-modern-soft-fork-activation-how-bitcoin-could-upgrade-next


Bitcoin Softfork Activation Methodology:
https://blog.bitmex.com/bitcoin-softfork-activation-methodology/


Activating Taproot: https://suredbits.com/activating-taproot/


Taproot activation website: https://taprootactivation.com/


In an effort to get this closer to the finish line we are organizing a
meeting on IRC on the ##taproot-activation channel on Tuesday 2nd February
at 19:00 UTC. The primary objective will be to finalize the revised BIP 8
activation method but general questions or discussion on Taproot activation
are welcome too. There is lots of prior context so please do sufficient
pre-reading in advance of attending if you would like to participate.


The relevant pull requests relating to revised BIP 8 are:


Replace unused BIP 9 logic with draft BIP 8 (Bitcoin Core PR)


https://github.com/bitcoin/bitcoin/pull/19573


BIP 8: Make signalling during LOCKED_IN recommended rather than mandatory
(BIP PR)


https://github.com/bitcoin/bips/pull/1020


BIP 8: allow some MUST_SIGNAL blocks to not signal (BIP PR)


https://github.com/bitcoin/bips/pull/1021


Feel free to post comments or questions at any time on the
##taproot-activation channel IRC in advance or following the meeting.

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

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

                 reply	other threads:[~2021-01-22 12:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAFvNmHS4s_MbXP8o3kWmaUZ5Xks1b76jSDymp1Bjr--4R8_v3Q@mail.gmail.com \
    --to=michaelfolkson@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox