From: Luke Dashjr <luke@dashjr•org>
To: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>,
Stephen Pair <stephen@bitpay•com>,
Gavin Andresen <gavinandresen@gmail•com>,
Amir Taaki <genjix@riseup•net>, Mike Hearn <hearn@vinumeris•com>,
Pieter Wuille <pieter.wuille@gmail•com>
Subject: [bitcoin-dev] BIP Final status
Date: Mon, 8 Feb 2016 22:17:55 +0000 [thread overview]
Message-ID: <201602082217.57146.luke@dashjr.org> (raw)
https://github.com/bitcoin/bips/pull/314 proposes updating the status of many
Accepted BIPs to Final:
BIP 11: M-of-N Standard Transactions
BIP 14: Protocol Version and User Agent
BIP 21: URI Scheme
BIP 22: getblocktemplate - Fundamentals
BIP 23: getblocktemplate - Pooled Mining
BIP 31: Pong message
BIP 32: Hierarchical Deterministic Wallets
BIP 34: Block v2, Height in Coinbase
BIP 35: mempool message
BIP 37: Connection Bloom filtering
BIP 65: OP_CHECKLOCKTIMEVERIFY
This PR has been open for a week, and I plan to merge it within the next week
unless there are objections.
Additionally, https://github.com/bitcoin/bips/pull/315 proposes to upgrade
five additional from Draft to Final status, and preferably needs ACKs from the
champions of the BIPs:
BIP 50: March 2013 Chain Fork Post-Mortem, by Gavin Andresen
BIP 60: Fixed Length "version" Message (Relay-Transactions Field), by Amir
Taaki
BIP 64: getutxo message, by Mike Hearn
BIP 66: Strict DER signatures, by Pieter Wuille
BIP 73: Use "Accept" header for response type negotiation with Payment Request
URLs, by Stephen Pair
Thanks,
Luke
next reply other threads:[~2016-02-08 22:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 22:17 Luke Dashjr [this message]
2016-02-08 22:41 ` Peter Todd
2016-02-08 22:57 ` Luke Dashjr
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=201602082217.57146.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=gavinandresen@gmail$(echo .)com \
--cc=genjix@riseup$(echo .)net \
--cc=hearn@vinumeris$(echo .)com \
--cc=pieter.wuille@gmail$(echo .)com \
--cc=stephen@bitpay$(echo .)com \
/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