From: Luke Dashjr <luke@dashjr•org>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: [bitcoin-dev] BIP Status updates (including to Active/Final Status) - BIP 39, BIP 43, BIP 44, BIP 67, BIP 111, BIP 125, BIP 130
Date: Tue, 23 Aug 2016 20:12:11 +0000 [thread overview]
Message-ID: <201608232012.12588.luke@dashjr.org> (raw)
A number of BIPs seem ready for updating to Final Status. If there are no
objections, I will update these in 2 weeks:
BIP 39: Mnemonic code for generating deterministic keys
- Used by many wallets and hundreds of thousands of users.
BIP 44: Multi-Account Hierarchy for Deterministic Wallets
- Appears to be implemented by multiple wallets.
BIP 67: Deterministic Pay-to-script-hash multi-signature addresses through
public key sorting
- Implementations in multiple wallet software exist.
BIP 125: Opt-in Full Replace-by-Fee Signaling
- Implemented in Bitcoin Core and derivatives; appears to be in regular use on
the network.
BIP 130: sendheaders message
- Implemented in Bitcoin Core and derivatives.
Also, BIP 43 (Purpose Field for Deterministic Wallets) is an informational BIP
which appears to be guiding to some extent the creation of new BIPs; therefore
I propose its Status be upgraded to Active. I will make this update in 2 weeks
also, if no objections.
Additionally, BIP 111 (NODE_BLOOM service bit) has been implemented in Bitcoin
Core and derivatives; it is unclear if used by clients yet. Can developers of
such clients please comment and let me know: 1) if their software supports
this BIP already; 2) if not, do they intend to support it in the future?
If and only if there are any clients using this service bit already, I will
update BIP 111 to Final Status in 2 weeks also.
Thanks,
Luke
next reply other threads:[~2016-08-23 20:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-23 20:12 Luke Dashjr [this message]
2016-08-23 20:54 ` Kenneth Heutmaker
2016-08-24 6:59 ` Jonas Schnelli
2016-08-24 8:34 ` Gregory Maxwell
2016-08-24 12:51 ` Thomas Voegtlin
2016-08-24 13:47 ` Andreas Schildbach
2016-08-24 18:22 ` Luke Dashjr
2016-08-24 14:18 ` Jonas Schnelli
2016-08-24 14:42 ` Jochen Hoenicke
2016-08-25 7:39 ` Jonas Schnelli
2016-08-25 7:56 ` Thomas Voegtlin
2016-08-25 8:08 ` Jonas Schnelli
2016-08-25 8:12 ` Jonas Schnelli
2016-08-25 8:50 ` Marek Palatinus
2016-08-25 9:02 ` Pieter Wuille
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=201608232012.12588.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