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
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1VaROq-0000XK-Rg
for bitcoin-development@lists.sourceforge.net;
Sun, 27 Oct 2013 14:33:04 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.219.51 as permitted sender)
client-ip=209.85.219.51; envelope-from=mh.in.england@gmail.com;
helo=mail-oa0-f51.google.com;
Received: from mail-oa0-f51.google.com ([209.85.219.51])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VaROp-0005V9-2B
for bitcoin-development@lists.sourceforge.net;
Sun, 27 Oct 2013 14:33:04 +0000
Received: by mail-oa0-f51.google.com with SMTP id h1so2621288oag.38
for <bitcoin-development@lists.sourceforge.net>;
Sun, 27 Oct 2013 07:32:57 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.60.52.101 with SMTP id s5mr211801oeo.56.1382884377655; Sun,
27 Oct 2013 07:32:57 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.156.42 with HTTP; Sun, 27 Oct 2013 07:32:57 -0700 (PDT)
In-Reply-To: <526B45DB.2030200@jerviss.org>
References: <274a1888-276c-4aa6-a818-68f548fbe0fa@me.com>
<9DCDB8F6-E3B2-426B-A41E-087E66B3821A@gmail.com>
<526B45DB.2030200@jerviss.org>
Date: Sun, 27 Oct 2013 15:32:57 +0100
X-Google-Sender-Auth: qLegQTQOF6ZH510viJwHBcOVWIU
Message-ID: <CANEZrP2dQT6Evgm0UwvSKdgVsSnb_VF6fovVo0n0eKDM5ARZpw@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: kjj <bitcoin-devel@jerviss.org>
Content-Type: multipart/alternative; boundary=001a11330d5418805f04e9b9dcbe
X-Spam-Score: -0.5 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked.
See
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
for more information. [URIs: doubleclick.net]
-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: 1VaROp-0005V9-2B
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Feedback requested: "reject" p2p 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: Sun, 27 Oct 2013 14:33:05 -0000
--001a11330d5418805f04e9b9dcbe
Content-Type: text/plain; charset=UTF-8
Yeah, something like HTTP would work well.
I'm really looking forward to this. Currently bitcoinj gets a small but
steady stream of bug reports of the form "my transaction did not
propagate". It's flaky because the library picks one peer to send the
transaction to, and then watches it propagate across the network. But if
that selected peer refuses the tx for whatever reason, that propagation
never comes, and there's currently no timeout to make it retry with a
different node. The transactions as created usually look fine, so it's not
clear to me why some nodes would accept it others wouldn't given the
absence of double spends, and there's no way to debug and find out :(
On Sat, Oct 26, 2013 at 6:32 AM, kjj <bitcoin-devel@jerviss.org> wrote:
> The HTTP status code system seems to work well enough, and seems to give
> the best of both worlds. A 3 digit numeric code that is
> machine-readable, and a freeform text note for humans.
>
> The clever part about that system was in realizing that the numeric
> codes didn't need to account for every possible error. They just need to
> give the other node the most useful information, like "try that again
> later, I'm having a temporary problem" vs. "That is just plain wrong and
> it will still be wrong next time too, so don't bother to retry".
>
> We can leave it to the humans to puzzle out the meaning of "403: values
> of txid gives rise to dom!"
>
> Gavin wrote:
> >
> > On Oct 26, 2013, at 11:01 AM, Jean-Paul Kogelman <
> jeanpaulkogelman@me.com> wrote:
> >
> >> Would it make sense to use either fixed length strings or maybe even
> enums?
> > No. Enums or fixed length strings just make it harder to extend, for no
> benefit (bandwidth of 'reject' messages doesn't matter, they will be rare
> and are not relayed).
> >
> >
> >
> ------------------------------------------------------------------------------
> > October Webinars: Code for Performance
> > Free Intel webinars can help you accelerate application performance.
> > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most
> from
> > the latest Intel processors and coprocessors. See abstracts and register
> >
> >
> http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
> > _______________________________________________
> > Bitcoin-development mailing list
> > Bitcoin-development@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
>
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most
> from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--001a11330d5418805f04e9b9dcbe
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Yeah, something like HTTP would work well.<div><br></div><=
div>I'm really looking forward to this. Currently bitcoinj gets a small=
but steady stream of bug reports of the form "my transaction did not =
propagate". It's flaky because the library picks one peer to send =
the transaction to, and then watches it propagate across the network. But i=
f that selected peer refuses the tx for whatever reason, that propagation n=
ever comes, and there's currently no timeout to make it retry with a di=
fferent node. The transactions as created usually look fine, so it's no=
t clear to me why some nodes would accept it others wouldn't given the =
absence of double spends, and there's no way to debug and find out :(</=
div>
<div><br></div><div><br></div></div><div class=3D"gmail_extra"><br><br><div=
class=3D"gmail_quote">On Sat, Oct 26, 2013 at 6:32 AM, kjj <span dir=3D"lt=
r"><<a href=3D"mailto:bitcoin-devel@jerviss.org" target=3D"_blank">bitco=
in-devel@jerviss.org</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">The HTTP status code system seems to work we=
ll enough, and seems to give<br>
the best of both worlds. =C2=A0A 3 digit numeric code that is<br>
machine-readable, and a freeform text note for humans.<br>
<br>
The clever part about that system was in realizing that the numeric<br>
codes didn't need to account for every possible error. They just need t=
o<br>
give the other node the most useful information, like "try that again<=
br>
later, I'm having a temporary problem" vs. "That is just plai=
n wrong and<br>
it will still be wrong next time too, so don't bother to retry".<b=
r>
<br>
We can leave it to the humans to puzzle out the meaning of "403: value=
s<br>
of txid gives rise to dom!"<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
Gavin wrote:<br>
><br>
> On Oct 26, 2013, at 11:01 AM, Jean-Paul Kogelman <<a href=3D"mailto=
:jeanpaulkogelman@me.com">jeanpaulkogelman@me.com</a>> wrote:<br>
><br>
>> Would it make sense to use either fixed length strings or maybe ev=
en enums?<br>
> No. Enums or fixed length strings just make it harder to extend, for n=
o benefit (bandwidth of 'reject' messages doesn't matter, they =
will be rare and are not relayed).<br>
><br>
><br>
> ----------------------------------------------------------------------=
--------<br>
> October Webinars: Code for Performance<br>
> Free Intel webinars can help you accelerate application performance.<b=
r>
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the mo=
st from<br>
> the latest Intel processors and coprocessors. See abstracts and regist=
er ><br>
> <a href=3D"http://pubads.g.doubleclick.net/gampad/clk?id=3D60135991&am=
p;iu=3D/4140/ostg.clktrk" target=3D"_blank">http://pubads.g.doubleclick.net=
/gampad/clk?id=3D60135991&iu=3D/4140/ostg.clktrk</a><br>
> _______________________________________________<br>
> Bitcoin-development mailing list<br>
> <a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-d=
evelopment@lists.sourceforge.net</a><br>
> <a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-develo=
pment" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitco=
in-development</a><br>
<br>
<br>
---------------------------------------------------------------------------=
---<br>
October Webinars: Code for Performance<br>
Free Intel webinars can help you accelerate application performance.<br>
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most fr=
om<br>
the latest Intel processors and coprocessors. See abstracts and register &g=
t;<br>
<a href=3D"http://pubads.g.doubleclick.net/gampad/clk?id=3D60135991&iu=
=3D/4140/ostg.clktrk" target=3D"_blank">http://pubads.g.doubleclick.net/gam=
pad/clk?id=3D60135991&iu=3D/4140/ostg.clktrk</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>
</div></div></blockquote></div><br></div>
--001a11330d5418805f04e9b9dcbe--
|
