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
|
Return-Path: <dscotese@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 85C4F308
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 25 Jul 2015 02:23:03 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wi0-f174.google.com (mail-wi0-f174.google.com
[209.85.212.174])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 15CE710A
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 25 Jul 2015 02:23:02 +0000 (UTC)
Received: by wibud3 with SMTP id ud3so52696931wib.0
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 24 Jul 2015 19:23:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:sender:date:message-id:subject:from:to:content-type;
bh=1oXCRZrCm3OabgxavwdMKCQ43aQq8IijrmVK5beWZ80=;
b=at0GNG9g+nFSPeXEgHZfdcLsKDSuZ7KJ8iyQGf/QxJ9wFm8/6y26jF5ovqIaK8Cdan
YGYw0/SgWA7TeWndaLUi+G8dW2h0ubB+qWvfDOyFgime2c67/md9t8nCahp1JwVuM1Xr
9k1bfJnqPogQzmRQXqun5lxTtr5UFbDuALPbYLqL7cGAVMxPGEwRp8S8lNzHIC4MKRxH
cMJ2Vrigwhr2ZyqE2vd8bdxDNEwSwzuVxTKrf3qhntqW4yBMZsPmfgrPmNr7QmVa0/k0
En/a0JaWNpRnza0ZxgcT/Tsv8eWl+t2M8Z4Kg4MpD3pY34VnCt4+5ryC9m1mcoaXXaml
jsLQ==
MIME-Version: 1.0
X-Received: by 10.180.96.230 with SMTP id dv6mr2350264wib.23.1437790980739;
Fri, 24 Jul 2015 19:23:00 -0700 (PDT)
Sender: dscotese@gmail.com
Received: by 10.27.184.134 with HTTP; Fri, 24 Jul 2015 19:23:00 -0700 (PDT)
Date: Fri, 24 Jul 2015 19:23:00 -0700
X-Google-Sender-Auth: lMwIqSWlgetdc332HdUlbFvd1RU
Message-ID: <CAGLBAhdggPPnxLgp+xQPWGtK1KA_QZt7eug2votak4in2DrwJA@mail.gmail.com>
From: Dave Scotese <dscotese@litmocracy.com>
To: bitcoin-dev@lists.linuxfoundation.org
Content-Type: multipart/alternative; boundary=f46d04374917ab1957051ba9cc0c
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW autolearn=ham
version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Subject: Re: [bitcoin-dev] Bitcoin Roadmap 2015,
or "If We Do Nothing" Analysis
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Jul 2015 02:23:03 -0000
--f46d04374917ab1957051ba9cc0c
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Incentivize investigations for public consumption. The people on this list
are the ones who probably care the most.
When I looked up that IP address, the Whois info names "OVH" and "Octave
Klaba" (who founded OVH, according to Wikipedia) as the owner. "
blockchain.info" appears in the HTML header as retrieved by the
"Anti-Hacker Alliance" (
http://anti-hacker-alliance.com/index.php?details=3D37.187.136.15).
Blockchain.info itself returns IP addresses managed by CloudFlare whenever
I try it.
On Fri, Jul 24, 2015 at 2:12 PM, Slurms MacKenzie via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> They do not run anything but BitcoinJ (evidenced by them blindly followin=
g
> invalid chains), so no proper consensus checking going on here at all.
> Connected to my nodes is a bad peer (doesn=E2=80=99t relay inventory but =
downloads
> everything) from 37.187.136.15, with the user agent
> /BitcoinJ:0.12SNAPHOT/Satoshi:0.2.0/ which is owned by blockchain.info.
> You can also submit an invalid transaction through their /pushtx interfac=
e
> and get a mixture of noise and BitcoinJ error messages out of it as well.
>
> If even the people who have to their claim hundreds of thousands of
> wallets are relying on their security don=E2=80=99t bother running even a=
single
> node to sanity check against, who are we really going to expect people to
> in the future if the load goes 8x, 16x, 32x higher? Like CoinBase and
> others, these are the companies which are claimed will be the ones
> supporting the network with ludicrous sized blocks because they have a
> financial incentive to.
>
> Well, they don't even do it now when it could be achieved with a $5 VPS.
>
>
> > Sent: Friday, July 24, 2015 at 8:43 PM
> > From: "Peter Todd via bitcoin-dev" <
> bitcoin-dev@lists.linuxfoundation.org>
> > To: "Thomas Zander" <thomas@thomaszander.se>
> > Cc: bitcoin-dev@lists.linuxfoundation.org
> > Subject: Re: [bitcoin-dev] Bitcoin Roadmap 2015, or "If We Do Nothing"
> Analysis
> > We can test the fact that blockchain.info's wallet and block explorer
> > has behaved in a way consistent with not running a full node - they hav=
e
> > shown invalid data that any full node would reject on multiple
> > occasions, most recently invalid confirmations during the BIP66 fork.
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
--f46d04374917ab1957051ba9cc0c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Incentivize investigations for public consumption.=C2=A0 T=
he people on this list are the ones who probably care the most.<br><br>When=
I looked up that IP address, the Whois info names "OVH" and &quo=
t;Octave Klaba" (who founded OVH, according to Wikipedia) as the owner=
.=C2=A0 "<a href=3D"http://blockchain.info">blockchain.info</a>" =
appears in the HTML header as retrieved by the "Anti-Hacker Alliance&q=
uot; (<a href=3D"http://anti-hacker-alliance.com/index.php?details=3D37.187=
.136.15">http://anti-hacker-alliance.com/index.php?details=3D37.187.136.15<=
/a>).=C2=A0 Blockchain.info itself returns IP addresses managed by CloudFla=
re whenever I try it.<br><div><div class=3D"gmail_extra"><br><div class=3D"=
gmail_quote">On Fri, Jul 24, 2015 at 2:12 PM, Slurms MacKenzie via bitcoin-=
dev <span dir=3D"ltr"><<a href=3D"mailto:bitcoin-dev@lists.linuxfoundati=
on.org" target=3D"_blank">bitcoin-dev@lists.linuxfoundation.org</a>></sp=
an> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">They do not=
run anything but BitcoinJ (evidenced by them blindly following invalid cha=
ins), so no proper consensus checking going on here at all. Connected to my=
nodes is a bad peer (doesn=E2=80=99t relay inventory but downloads everyth=
ing) from 37.187.136.15, with the user agent /BitcoinJ:0.12SNAPHOT/Satoshi:=
0.2.0/ which is owned by <a href=3D"http://blockchain.info" rel=3D"noreferr=
er" target=3D"_blank">blockchain.info</a>. You can also submit an invalid t=
ransaction through their /pushtx interface and get a mixture of noise and B=
itcoinJ error messages out of it as well.<br>
<br>
If even the people who have to their claim hundreds of thousands of wallets=
are relying on their security don=E2=80=99t bother running even a single n=
ode to sanity check against, who are we really going to expect people to in=
the future if the load goes 8x, 16x, 32x higher? Like CoinBase and others,=
these are the companies which are claimed will be the ones supporting the =
network with ludicrous sized blocks because they have a financial incentive=
to.<br>
<br>
Well, they don't even do it now when it could be achieved with a $5 VPS=
.<br>
<br>
<br>
> Sent: Friday, July 24, 2015 at 8:43 PM<br>
> From: "Peter Todd via bitcoin-dev" <<a href=3D"mailto:bit=
coin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org</=
a>><br>
> To: "Thomas Zander" <<a href=3D"mailto:thomas@thomaszande=
r.se">thomas@thomaszander.se</a>><br>
> Cc: <a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-d=
ev@lists.linuxfoundation.org</a><br>
> Subject: Re: [bitcoin-dev] Bitcoin Roadmap 2015, or "If We Do Not=
hing" Analysis<br>
> We can test the fact that <a href=3D"http://blockchain.info" rel=3D"no=
referrer" target=3D"_blank">blockchain.info</a>'s wallet and block expl=
orer<br>
<span class=3D"im">> has behaved in a way consistent with not running a =
full node - they have<br>
> shown invalid data that any full node would reject on multiple<br>
> occasions, most recently invalid confirmations during the BIP66 fork.<=
br>
</span><div class=3D""><div class=3D"h5">__________________________________=
_____________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.=
linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</div></div></blockquote></div></div></div></div>
--f46d04374917ab1957051ba9cc0c--
|
