From: Steve Lee <steven.j.lee@gmail•com>
To: bitcoin-dev@lists•linuxfoundation.org,
lightning-dev@lists•linuxfoundation.org
Subject: [bitcoin-dev] Sign up for Taproot BIP review by October 30
Date: Wed, 23 Oct 2019 10:44:49 -0700 [thread overview]
Message-ID: <CABu3BAePQVzGX=1ugTBqwzvbB6jEKC4LGG-Mwpki5iyTvs5d9Q@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1329 bytes --]
Hello everyone,
The schnorr/taproot/tapscript BIPs are ready for review at this point, and
we want to get as much in-depth review from as broad a range of people as
we can before we go further on implementation/deployment. Reviewing the
BIPs is hard in two ways: not many people are familiar with reviewing BIPs
in the first place, and there are a lot of concepts involved in the three
BIPs for people to get their heads around.
This is a proposal <https://github.com/ajtowns/taproot-review> for a
structured review period. The idea is that participants will be given some
guidance/structure for going through the BIPs, and at the end should be
able to either describe issues with the BIP drafts that warrant changes, or
be confident that they’ve examined the proposals thoroughly enough to give
an “ACK” that the drafts should be formalised and move forwards into
implementation/deployment phases.
Benefits of participating:
* Deeply understand schnorr and taproot
* Be a stakeholder in Bitcoin consensus development
* Support/safeguard decentralisation of Bitcoin protocol development
* Have fun!
If you are interested in participating, please sign up here
<https://forms.gle/stnJvHQHREdkaxkS8 >.
Special thanks to AJ Towns for doing most of the heavy lifting to get this
going!
Steve
[-- Attachment #2: Type: text/html, Size: 1496 bytes --]
reply other threads:[~2019-10-23 17:45 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='CABu3BAePQVzGX=1ugTBqwzvbB6jEKC4LGG-Mwpki5iyTvs5d9Q@mail.gmail.com' \
--to=steven.j.lee@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=lightning-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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