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; 
MIME-Version: 1.0
Sender: mh.in.england@gmail.com
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
Message-ID: <CANEZrP0ViJSQr_UUxLqM-eFTir=-FGwZ2cSxuPgaVi=KiM8gsA@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Turkey Breast <turkeybreast@yahoo.com>
Content-Type: multipart/alternative; boundary=001a11c25434e1990104df72ff79
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Missing fRelayTxes in version message
Precedence: list

--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 <turkeybreast@yahoo.com>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

<div dir=3D"ltr">It&#39;s not a bug (although there was recently a change t=
o make bitcoind/qt always send this field anyway).=C2=A0<div><br></div><div=
 style>I don&#39;t know where Amir is going with BIP 60. Version messages h=
ave always been variable length. There&#39;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.</div=
>
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Tue,=
 Jun 18, 2013 at 7:45 PM, Turkey Breast <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:turkeybreast@yahoo.com" target=3D"_blank">turkeybreast@yahoo.com</a>&g=
t;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div><div style=3D"font-size:12pt;font-famil=
y:times new roman,new york,times,serif"><div>See this BIP. I&#39;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.</div>
<div><br></div><div style=3D"font-style:normal;font-size:16px;background-co=
lor:transparent;font-family:times new roman,new york,times,serif"><a href=
=3D"https://en.bitcoin.it/wiki/BIP_0060#Code_Updates" target=3D"_blank">htt=
ps://en.bitcoin.it/wiki/BIP_0060#Code_Updates</a></div>
<div style=3D"font-style:normal;font-size:16px;background-color:transparent=
;font-family:times new roman,new york,times,serif"><br></div><div style=3D"=
font-style:normal;font-size:16px;background-color:transparent;font-family:t=
imes new roman,new york,times,serif">
This BIP details everything that needs to be done and proposes a protocol u=
pgrade.<br></div></div></div><br>------------------------------------------=
------------------------------------<br>
This SF.net email is sponsored by Windows:<br>
<br>
Build for Windows Store.<br>
<br>
<a href=3D"http://p.sf.net/sfu/windows-dev2dev" target=3D"_blank">http://p.=
sf.net/sfu/windows-dev2dev</a><br>_________________________________________=
______<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
<br></blockquote></div><br></div>

--001a11c25434e1990104df72ff79--