1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
|
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 <mh.in.england@gmail.com>) 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 <bitcoin-development@lists.sourceforge.net>;
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: <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
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 <bitcoin-development@lists.sourceforge.net>
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: <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: 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 <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'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'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.</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"><<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'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--
|
