From: Luke Dashjr <luke@dashjr•org>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] Status updates for BIP 9, 68, 112, and 113
Date: Fri, 15 Jul 2016 16:08:51 +0000 [thread overview]
Message-ID: <201607151608.52063.luke@dashjr.org> (raw)
Daniel Cousens opened the issue a few weeks ago, that BIP 9 should progress to
Accepted stage. However, as an informational BIP, it is not entirely clear on
whether it falls in the Draft/Accepted/Final classification of proposals
requiring implementation, or the Draft/Active classification like process
BIPs. Background of this discussion is at:
https://github.com/bitcoin/bips/pull/413
(Discussion on the GitHub BIPs repo is *NOT* recommended, hence bringing this
topic to the mailing list)
Reviewing the criteria for status changes, my opinion is that:
- BIPs 68, 112, 113, and 141 are themselves implementations of BIP 9
-- therefore, BIP 9 falls under the Draft/Accepted/Final class
- BIPs 68, 112, and 113 have been deployed to the network successfully
-- therefore, BIP 9 has satisfied the conditions of not only Accepted status,
but also Final status
-- therefore, BIPs 68, 112, and 113 also ought to be Final status
If there are no objections, I plan to update the status to Final for BIPs 9,
68, 112, and 113 in one month. Since all four BIPs are currently Draft, I also
need at least one author from each BIP to sign-off on promoting them to (and
beyond) Accepted.
BIP 9: Pieter Wuille <pieter.wuille@gmail•com>
Peter Todd <pete@petertodd•org>
Greg Maxwell <greg@xiph•org>
Rusty Russell <rusty@rustcorp•com.au>
BIP 68: Mark Friedenbach <mark@friedenbach•org>
BtcDrak <btcdrak@gmail•com>
Nicolas Dorier <nicolas.dorier@gmail•com>
kinoshitajona <kinoshitajona@gmail•com>
BIP 112: BtcDrak <btcdrak@gmail•com>
Mark Friedenbach <mark@friedenbach•org>
Eric Lombrozo <elombrozo@gmail•com>
BIP 113: Thomas Kerin <me@thomaskerin•io>
Mark Friedenbach <mark@friedenbach•org>
next reply other threads:[~2016-07-15 16:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 16:08 Luke Dashjr [this message]
2016-07-15 16:31 ` Peter Todd
2016-08-18 21:09 Luke Dashjr
[not found] <201607151531.00058.luke@dashjr.org>
2016-08-18 23:05 ` Btc Drak
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=201607151608.52063.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-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