From: Luke Dashjr <luke@dashjr.org>
To: Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>,
libbitcoin@lists.dyne.org,
"lightning-dev@lists.linuxfoundation.org"
<lightning-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] BIP status updates & BIP 2 activation
Date: Wed, 30 Nov 2016 10:20:30 +0000 [thread overview]
Message-ID: <201611301020.31747.luke@dashjr.org> (raw)
To conclude discussion on BIP 2, I have opened a pull request to implement it
and mark it active. Note this implies activation and implementation of BIP 123
as well: https://github.com/bitcoin/bips/pull/478
I plan to merge this on December 14th. If there are any hard objections to
this change, please bring it up on the bitcoin-dev mailing list before then.
Further reviews of the implementation are welcome in the meantime. Please
refrain from requesting further changes to the BIPs themselves unless it is a
blocker/show-stopper or trivial (not changing the meaning).
In the process of implementing BIP 2, I came across a number of BIPs which
managed to get into the repository without a proper license. Authors of any of
these BIPs should open a pull request adding the necessary Copyright section
and License header(s). (If there are other contributors to the document in the
BIP git logs, I will try to reach out to them to get permission. If you have
accepted contributions from anyone not documented in git as an Author, please
mention this in the PR explicitly.)
These BIPs need a license:
001 BIP Purpose and Guidelines
010 Multi-Sig Transaction Distribution
011 M-of-N Standard Transactions
012 OP_EVAL
013 Address Format for pay-to-script-hash
014 Protocol Version and User Agent
015 Aliases
016 Pay to Script Hash
021 URI Scheme
030 Duplicate transactions
031 Pong message
032 Hierarchical Deterministic Wallets
033 Stratized Nodes
034 Block v2, Height in Coinbase
035 mempool message
039 Mnemonic code for generating deterministic keys
043 Purpose Field for Deterministic Wallets
044 Multi-Account Hierarchy for Deterministic Wallets
045 Structure for Deterministic P2SH Multisignature Wallets
047 Reusable Payment Codes for Hierarchical Deterministic Wallets
061 Reject P2P message
062 Dealing with malleability
064 getutxo message
066 Strict DER signatures
067 Deterministic Pay-to-script-hash multi-signature addresses through
public key sorting
068 Relative lock-time using consensus-enforced sequence numbers
070 Payment Protocol
071 Payment Protocol MIME types
072 bitcoin: uri extensions for Payment Protocol
073 Use "Accept" header for response type negotiation with Payment Request
URLs
075 Out of Band Address Exchange using Payment Protocol Encryption
101 Increase maximum block size
102 Block size increase to 2MB
103 Block size following technological growth
106 Dynamically Controlled Bitcoin Block Size Max Cap
120 Proof of Payment
121 Proof of Payment URI scheme
123 BIP Classification
Thanks,
Luke
reply other threads:[~2016-11-30 10:20 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=201611301020.31747.luke@dashjr.org \
--to=luke@dashjr.org \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=libbitcoin@lists.dyne.org \
--cc=lightning-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