Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Xecgc-0002BD-JE for bitcoin-development@lists.sourceforge.net; Thu, 16 Oct 2014 04:29:14 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of bluematt.me designates 192.241.179.72 as permitted sender) client-ip=192.241.179.72; envelope-from=bitcoin-list@bluematt.me; helo=mail.bluematt.me; Received: from mail.bluematt.me ([192.241.179.72]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1Xecgb-0007Wf-H8 for bitcoin-development@lists.sourceforge.net; Thu, 16 Oct 2014 04:29:14 +0000 Received: from [172.17.0.2] (gw.vpn.bluematt.me [162.243.132.6]) by mail.bluematt.me (Postfix) with ESMTPSA id B258E4FA42 for ; Thu, 16 Oct 2014 04:29:07 +0000 (UTC) Message-ID: <543F4992.4000509@bluematt.me> Date: Thu, 16 Oct 2014 04:29:06 +0000 From: Matt Corallo User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: bitcoin-development@lists.sourceforge.net References: In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Spam-Score: -1.5 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -0.0 SPF_PASS SPF: sender matches SPF record X-Headers-End: 1Xecgb-0007Wf-H8 Subject: Re: [Bitcoin-development] Proposed BIP status changes X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Oct 2014 04:29:14 -0000 On 10/15/14 08:47, Wladimir wrote: > These BIPs should go to Final state - they are implemented all over > the place, and are thus entirely fixed in place now. Any changes would > require a new BIP as amandment: > > - BIP 14 (BIP Protocol Version and User Agent) > > - BIP 21 (URI Scheme) ACK. > - BIP 22 (getblocktemplate - Fundamentals) > > - BIP 31 (Pong Message) > > - BIP 34 (Block v2, Height in coinbase) > > - BIP 35 (mempool message) > > - BIP 37 (Bloom filtering) > > Let me know if you (don't) agree. > > Wladimir > > ------------------------------------------------------------------------------ > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > http://p.sf.net/sfu/Zoho > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development >