Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1SEj69-0006Xu-BK for bitcoin-development@lists.sourceforge.net; Mon, 02 Apr 2012 15:23:13 +0000 X-ACL-Warn: Received: from vps7135.xlshosting.net ([178.18.90.41]) by sog-mx-4.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1SEj63-0000n5-Li for bitcoin-development@lists.sourceforge.net; Mon, 02 Apr 2012 15:23:13 +0000 Received: by vps7135.xlshosting.net (Postfix, from userid 1000) id 971F9244516; Mon, 2 Apr 2012 17:23:00 +0200 (CEST) Date: Mon, 2 Apr 2012 17:23:00 +0200 From: Pieter Wuille To: bitcoin-development@lists.sourceforge.net Message-ID: <20120402152259.GA19853@vps7135.xlshosting.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-PGP-Key: http://sipa.ulyssis.org/pubkey.asc User-Agent: Mutt/1.5.20 (2009-06-14) X-Spam-Score: 1.2 (+) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (pieter.wuille[at]gmail.com) 0.0 DKIM_ADSP_CUSTOM_MED No valid author signature, adsp_override is CUSTOM_MED -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 1.2 NML_ADSP_CUSTOM_MED ADSP custom_med hit, and not from a mailing list X-Headers-End: 1SEj63-0000n5-Li Subject: [Bitcoin-development] Network version increase 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: Mon, 02 Apr 2012 15:23:13 -0000 Hello all, Mike Hearn has submitted a pull request to add a pong message in reply to a ping. This warrants an upgrade of the network protocol version number, which is since BIP14 independent from the version numbers of the reference client. Any opinions about a numbering scheme? Currently the value 60000 is used. We could simply start increasing the number one by one now for every change, or we could do a "cleanup" to 100000 first, and start incrementing from there. -- Pieter