Promote Draft->Final BIPs: 50, 60, 64, 66, and 73 #315

1. 
   luke-jr commented at 9:18 pm on February 1, 2016: member

   The following BIPs appear to meet the criteria for Final status, but have not been promoted to Accepted by their author yet, so need ACKs from the authors. Since at least @genjix is MIA, we probably also need to discuss how to handle such actions when BIP champions disappear - BIP 1 allows for me to assign an additional champion to take over, but I’m not sure anyone would necessarily want to do so in this case.

   BIP 50: Proposed action items, including the hardfork, are completed. @gavinandresen

   BIP 60: BIP 37 was apparently not clear on whether the new “relay transactions” flag was mandatory or optional. BIP 60 sought to explicitly make it mandatory. In parallel, Jeff Garzik interpreted BIP 37’s field as mandatory in https://github.com/bitcoin/bitcoin/issues/2534 and Pieter Wuille implemented the changes required for that (and BIP 60) in https://github.com/bitcoin/bitcoin/pull/2763 . Numerous forks of Bitcoin Core since then have also picked up this change. @genjix

   BIP 64: The getutxo message was implemented for use between (pre-contentious hardforks) Bitcoin XT and Lighthouse. Both of these are unmaintained now, but this does not seem relevant. @mikehearn

   BIP 66: Softfork accepted by a supermajority of miners. @sipa

   BIP 73: Implemented by at least Bitcoin Core and BitPay. @gasteve

2. Promote Draft->Final BIPs: 50, 60, 64, 66, and 73

   BIP 50: Proposed action items, including the hardfork, are completed.
   
   BIP 60: BIP 37 was apparently not clear on whether the new "relay transactions" flag was mandatory or optional. BIP 60 sought to explicitly make it mandatory. In parallel, Jeff Garzik interpreted BIP 37's field as mandatory in https://github.com/bitcoin/bitcoin/issues/2534 and Pieter Wuille implemented the changes required for that (and BIP 60) in https://github.com/bitcoin/bitcoin/pull/2763 . Numerous forks of Bitcoin Core since then have also picked up this change.
   
   BIP 64: The getutxo message was implemented for use between (pre-contentious hardforks) Bitcoin XT and Lighthouse. Both of these are unmaintained now, but this does not seem relevant.
   
   BIP 66: Softfork accepted by a supermajority of miners.
   
   BIP 73: Implemented by at least Bitcoin Core and BitPay.

   4ca705ac04
3. 
   gasteve commented at 10:26 pm on February 8, 2016: none

   ACK BIP 73
4. 
   sipa commented at 10:36 pm on February 8, 2016: member

   ACK BIP 66
5. 
   gavinandresen commented at 11:29 pm on February 8, 2016: contributor

   ACK BIP 50
6. 
   luke-jr commented at 5:29 am on February 24, 2016: member

   Merged 50 & 73 via a74ea14bc66d6be699f3e3d5aae2fa308ad7adad
7. luke-jr closed this on Feb 24, 2016

   ---

8. luke-jr cross-referenced this on Feb 24, 2016 from issue Promote Draft->Final BIPs: 60 and 64 by luke-jr

Contributors
luke-jr gasteve sipa gavinandresen