Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Up1tW-0001i1-V1 for bitcoin-development@lists.sourceforge.net; Tue, 18 Jun 2013 19:48:47 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.214.178 as permitted sender) client-ip=209.85.214.178; envelope-from=mh.in.england@gmail.com; helo=mail-ob0-f178.google.com; Received: from mail-ob0-f178.google.com ([209.85.214.178]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Up1tU-0005dK-If for bitcoin-development@lists.sourceforge.net; Tue, 18 Jun 2013 19:48:45 +0000 Received: by mail-ob0-f178.google.com with SMTP id fb19so5060236obc.37 for ; Tue, 18 Jun 2013 12:48:39 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.182.215.133 with SMTP id oi5mr13143195obc.83.1371584919079; Tue, 18 Jun 2013 12:48:39 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.76.23.36 with HTTP; Tue, 18 Jun 2013 12:48:38 -0700 (PDT) In-Reply-To: <1371577555.61696.YahooMailNeo@web162703.mail.bf1.yahoo.com> References: <1371577555.61696.YahooMailNeo@web162703.mail.bf1.yahoo.com> Date: Tue, 18 Jun 2013 21:48:38 +0200 X-Google-Sender-Auth: _2N9C4vdmLTPqRKAfw7TA8apGM8 Message-ID: From: Mike Hearn To: Turkey Breast Content-Type: multipart/alternative; boundary=001a11c25434e1990104df72ff79 X-Spam-Score: -0.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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (mh.in.england[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message 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: 1Up1tU-0005dK-If Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Missing fRelayTxes in version message 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: Tue, 18 Jun 2013 19:48:47 -0000 --001a11c25434e1990104df72ff79 Content-Type: text/plain; charset=UTF-8 It's not a bug (although there was recently a change to make bitcoind/qt always send this field anyway). I don't know where Amir is going with BIP 60. Version messages have always been variable length. There's nothing inherent in the Bitcoin protocol that says all messages are fixed length, indeed, tx messages are allowed to have arbitrary data appended after them that gets relayed. On Tue, Jun 18, 2013 at 7:45 PM, Turkey Breast wrote: > See this BIP. I'm not sure if this is a bug or what, but it would be good > if messages always had a fixed number of fields per protocol version. > > https://en.bitcoin.it/wiki/BIP_0060#Code_Updates > > This BIP details everything that needs to be done and proposes a protocol > upgrade. > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Windows: > > Build for Windows Store. > > http://p.sf.net/sfu/windows-dev2dev > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > > --001a11c25434e1990104df72ff79 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
It's not a bug (although there was recently a change t= o make bitcoind/qt always send this field anyway).=C2=A0

I don't know where Amir is going with BIP 60. Version messages h= ave always been variable length. There's nothing inherent in the Bitcoi= n protocol that says all messages are fixed length, indeed, tx messages are= allowed to have arbitrary data appended after them that gets relayed.


On Tue,= Jun 18, 2013 at 7:45 PM, Turkey Breast <turkeybreast@yahoo.com&g= t; wrote:
See this BIP. I'm not sure= if this is a bug or what, but it would be good if messages always had a fi= xed number of fields per protocol version.


This BIP details everything that needs to be done and proposes a protocol u= pgrade.

------------------------------------------= ------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.= sf.net/sfu/windows-dev2dev
_________________________________________= ______
Bitcoin-development mailing list
Bitcoin-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment


--001a11c25434e1990104df72ff79--