Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <ayeowch@gmail.com>) id 1UZGHt-0002xZ-E2
	for bitcoin-development@lists.sourceforge.net;
	Mon, 06 May 2013 07:56:45 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.214.53 as permitted sender)
	client-ip=209.85.214.53; envelope-from=ayeowch@gmail.com;
	helo=mail-bk0-f53.google.com; 
Received: from mail-bk0-f53.google.com ([209.85.214.53])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1UZGHs-0000Rt-CW
	for bitcoin-development@lists.sourceforge.net;
	Mon, 06 May 2013 07:56:45 +0000
Received: by mail-bk0-f53.google.com with SMTP id i18so1484959bkv.12
	for <bitcoin-development@lists.sourceforge.net>;
	Mon, 06 May 2013 00:56:38 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.204.166.11 with SMTP id k11mr7027927bky.6.1367826997949;
	Mon, 06 May 2013 00:56:37 -0700 (PDT)
Received: by 10.204.203.15 with HTTP; Mon, 6 May 2013 00:56:37 -0700 (PDT)
Date: Mon, 6 May 2013 17:56:37 +1000
Message-ID: <CAA3bHnxg3BuaVXMqZ2G7G0CiKFAgQFArd2HPW08JFMbEdTFFZw@mail.gmail.com>
From: Addy Yeow <ayeowch@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Content-Type: text/plain; charset=ISO-8859-1
X-Spam-Score: -1.6 (-)
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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(ayeowch[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
	author's domain
	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
	not necessarily valid
	-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1UZGHs-0000Rt-CW
Subject: [Bitcoin-development] Requirement for relay field in version packet
	(protocol version >= 70001)
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Mon, 06 May 2013 07:56:45 -0000

From https://en.bitcoin.it/wiki/Protocol_specification#version, is the
relay field (bool/1 byte) required in all version packets coming from
client with protocol version >= 70001?