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
236
237
238
239
240
241
242
|
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 <jgarzik@bitpay.com>) id 1YDJmA-0000CJ-Hr
for bitcoin-development@lists.sourceforge.net;
Mon, 19 Jan 2015 21:22:22 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of bitpay.com
designates 209.85.214.171 as permitted sender)
client-ip=209.85.214.171; envelope-from=jgarzik@bitpay.com;
helo=mail-ob0-f171.google.com;
Received: from mail-ob0-f171.google.com ([209.85.214.171])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YDJm8-0003Yq-FD
for bitcoin-development@lists.sourceforge.net;
Mon, 19 Jan 2015 21:22:22 +0000
Received: by mail-ob0-f171.google.com with SMTP id va2so20992508obc.2
for <bitcoin-development@lists.sourceforge.net>;
Mon, 19 Jan 2015 13:22:15 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to:cc:content-type;
bh=QcEEXl/rOYHGlgkQKEq8ZKNr/kOFtDHe3ZVoHsJnLaQ=;
b=eX9GDWBDCo6P+rn3zWJsVTDUUMk+nZqW2W1kKhCuw0WpiTUEHK5XBiVacZw6PqE3ah
eM/Pt+WJk5vbQuFEvICfnEtYyBaylDh9xz3LxfkSIXpMVd/nrkFDG4GX8FrZViLnO490
tq3d3jw+dvHeIV+hmXrGn1UCk52rl7AHA/KN/BPYIwvukkRTdx5tEG8SulhjAOTEKqFE
z5tWDgtVm4DVMSvVCjBpo5tLA27Pshpw93Aukl2FCI1z/wx2CXAwK4cRv0PaSQ/4EI5M
qAh8JLHmaCXGPSD4kmfVgu/UqbIpdydmM9u86WpxvSJxqzGaPfTVLDw2IySEgFT8Qkue
JsrQ==
X-Gm-Message-State: ALoCoQmRd3XaRpRVAOxJk6TkLOh0A8s71M8i9SGHGaXzpjkv8s79F+jS7siGxGJnnrELLWm7NPxc
X-Received: by 10.60.131.203 with SMTP id oo11mr19776376oeb.15.1421702535024;
Mon, 19 Jan 2015 13:22:15 -0800 (PST)
MIME-Version: 1.0
Received: by 10.202.219.196 with HTTP; Mon, 19 Jan 2015 13:21:54 -0800 (PST)
In-Reply-To: <54BD6314.60607@gmail.com>
References: <CAN5esQJe0uUm0NyctaBa6WH7_JjeE_OLR=FY_XQWnSr50VRDyA@mail.gmail.com>
<CAJHLa0OTynX4oiQoyanpRKE2tpAuS4L5X-2j20328725J9RrvQ@mail.gmail.com>
<2C7D6208-1921-4DDC-90FE-DB1ABE1D61DB@petertodd.org>
<CAN5esQLCV=L0kYxDGhK2F=qZ8OqMxyYS+-Pn17U_M+nV4Sj3Og@mail.gmail.com>
<54BD6314.60607@gmail.com>
From: Jeff Garzik <jgarzik@bitpay.com>
Date: Mon, 19 Jan 2015 16:21:54 -0500
Message-ID: <CAJHLa0NA357Fa2CjBPopKvDs1T0FFOsPjnizsVWPNWX46LfgyA@mail.gmail.com>
To: Alan Reiner <etotheipi@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b4179b593a1cd050d07ea1e
X-Spam-Score: -0.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 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-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: 1YDJm8-0003Yq-FD
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] BIP70: why Google Protocol Buffers for
encoding?
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, 19 Jan 2015 21:22:22 -0000
--047d7b4179b593a1cd050d07ea1e
Content-Type: text/plain; charset=UTF-8
Correct. I should have said "more likely to be deterministic" Bitcoin
Core does not *rely* on determinism in BIP70; I was referring to recent
upstream efforts to make protobufs usable in a deterministic fashion by
default.
On Mon, Jan 19, 2015 at 3:03 PM, Alan Reiner <etotheipi@gmail.com> wrote:
> I'm a bit confused. It's been a long time since I looked at protobuf
> (and will have to dig into it soon), but I seem to recall it doesn't have
> any of the determinism properties you guys just said. It is intended to
> allow you to skip details of the on-the-wire representations and just send
> a bunch of named fields between systems. I thought there was no guarantee
> that two identical protobuf structures will get serialized identically...?
>
>
>
>
>
> On 01/19/2015 02:57 PM, Richard Brady wrote:
>
> Thanks guys, great answers.
>
> The design choice certainly makes a lot more sense now regardless of
> whether one agrees with it or not.
>
> Regards,
> Richard
>
>
>
> ------------------------------------------------------------------------------
> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
> GigeNET is offering a free month of service with a new server in Ashburn.
> Choose from 2 high performing configs, both with 100TB of bandwidth.
> Higher redundancy.Lower latency.Increased capacity.Completely compliant.http://p.sf.net/sfu/gigenet
>
>
>
> _______________________________________________
> Bitcoin-development mailing listBitcoin-development@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
>
>
> ------------------------------------------------------------------------------
> New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
> GigeNET is offering a free month of service with a new server in Ashburn.
> Choose from 2 high performing configs, both with 100TB of bandwidth.
> Higher redundancy.Lower latency.Increased capacity.Completely compliant.
> http://p.sf.net/sfu/gigenet
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
--047d7b4179b593a1cd050d07ea1e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Correct.=C2=A0 I should have said "more likely to be =
deterministic"=C2=A0 Bitcoin Core does not <i>rely</i> on determinism =
in BIP70; I was referring to recent upstream efforts to make protobufs usab=
le in a deterministic fashion by default.<br></div><div class=3D"gmail_extr=
a"><br><div class=3D"gmail_quote">On Mon, Jan 19, 2015 at 3:03 PM, Alan Rei=
ner <span dir=3D"ltr"><<a href=3D"mailto:etotheipi@gmail.com" target=3D"=
_blank">etotheipi@gmail.com</a>></span> wrote:<br><blockquote class=3D"g=
mail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-l=
eft:1ex">
=20
=20
=20
<div bgcolor=3D"#FFFFFF" text=3D"#000000">
I'm a bit confused.=C2=A0 It's been a long time since I looked =
at
protobuf (and will have to dig into it soon), but I seem to recall
it doesn't have any of the determinism properties you guys just
said.=C2=A0 It is intended to allow you to skip details of the
on-the-wire representations and just send a bunch of named fields
between systems.=C2=A0 I thought there was no guarantee that two
identical protobuf structures will get serialized identically...?<div><=
div class=3D"h5"><br>
<br>
<br>
<br>
<br>
<div>On 01/19/2015 02:57 PM, Richard Brady
wrote:<br>
</div>
</div></div><blockquote type=3D"cite"><div><div class=3D"h5">
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div>
<div>Thanks guys, great answers.=C2=A0</div>
<div><br>
</div>
<div>The design choice certainly
makes a lot more sense now regardless of whether one
agrees with it or not.</div>
</div>
<div><br>
</div>
<div>Regards,</div>
<div>Richard</div>
<br>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
</div></div><span class=3D""><pre>-----------------------------------=
-------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
<a href=3D"http://p.sf.net/sfu/gigenet" target=3D"_blank">http://p.sf.net/s=
fu/gigenet</a></pre>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
Bitcoin-development mailing list
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net" target=3D"_bla=
nk">Bitcoin-development@lists.sourceforge.net</a>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a>
</pre>
</span></blockquote>
<br>
</div>
<br>-----------------------------------------------------------------------=
-------<br>
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.<br>
GigeNET is offering a free month of service with a new server in Ashburn.<b=
r>
Choose from 2 high performing configs, both with 100TB of bandwidth.<br>
Higher redundancy.Lower latency.Increased capacity.Completely compliant.<br=
>
<a href=3D"http://p.sf.net/sfu/gigenet" target=3D"_blank">http://p.sf.net/s=
fu/gigenet</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><br clear=3D"all"><br>-- <br><div class=3D"gmail=
_signature">Jeff Garzik<br>Bitcoin core developer and open source evangelis=
t<br>BitPay, Inc. =C2=A0 =C2=A0 =C2=A0<a href=3D"https://bitpay.com/" targe=
t=3D"_blank">https://bitpay.com/</a></div>
</div>
--047d7b4179b593a1cd050d07ea1e--
|
