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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <ryacko@gmail.com>) id 1VvMYe-0008L6-3g
for bitcoin-development@lists.sourceforge.net;
Tue, 24 Dec 2013 07:37:40 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.82.178 as permitted sender)
client-ip=74.125.82.178; envelope-from=ryacko@gmail.com;
helo=mail-we0-f178.google.com;
Received: from mail-we0-f178.google.com ([74.125.82.178])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1VvMYc-0004Zu-TI
for bitcoin-development@lists.sourceforge.net;
Tue, 24 Dec 2013 07:37:40 +0000
Received: by mail-we0-f178.google.com with SMTP id u57so5630735wes.37
for <bitcoin-development@lists.sourceforge.net>;
Mon, 23 Dec 2013 23:37:32 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.194.142.142 with SMTP id rw14mr409760wjb.87.1387870652703;
Mon, 23 Dec 2013 23:37:32 -0800 (PST)
Sender: ryacko@gmail.com
Received: by 10.194.188.6 with HTTP; Mon, 23 Dec 2013 23:37:32 -0800 (PST)
In-Reply-To: <52B8EB37.2080006@monetize.io>
References: <CAO7N=i1_ZyGBAsOGdCvPwJNhARbe-MuWzi9MYLsa3WS_PO25hg@mail.gmail.com>
<52B7AC86.9010808@monetize.io>
<CAO7N=i1avBNy9wfQSAyDH19ywJ__C_A9XSVBbufa42=Lu4MjRg@mail.gmail.com>
<52B8EB37.2080006@monetize.io>
Date: Mon, 23 Dec 2013 23:37:32 -0800
X-Google-Sender-Auth: 3yw3HIRFLLvSQJBU0-T-wsaXkts
Message-ID: <CAO7N=i1DpGnfjgAX6GHNC-yVq_9P38vb_1MszcRcRhEA8nnLcA@mail.gmail.com>
From: Ryan Carboni <ryan.jc.pc@gmail.com>
To: Mark Friedenbach <mark@monetize.io>,
bitcoin-development@lists.sourceforge.net
Content-Type: multipart/alternative; boundary=089e013a16a43faaca04ee42d122
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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(ryacko[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
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: gpgtools.org]
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: 1VvMYc-0004Zu-TI
Subject: Re: [Bitcoin-development] Bitcoin difficulty sanity check suggestion
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, 24 Dec 2013 07:37:40 -0000
--089e013a16a43faaca04ee42d122
Content-Type: text/plain; charset=ISO-8859-1
It does take a state-level actor to apparently disconnect *multiple *miners
from the rest of the network.
How many Bitcoin miners hash an entire percent or more of the Bitcoin
network? What you're proposing is an attack at the highest levels of the
internet infrastructure.
On Mon, Dec 23, 2013 at 6:02 PM, Mark Friedenbach <mark@monetize.io> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Which would leave you entirely in the hands of your dialup provider.
> Or the manufacturer of your switch. Or your ISP's backbone provider.
> It does not take a state-level actor to do network attacks.
>
> BTW, what does "difficulty would be reset" mean? There are multiple
> ways to interpret that statement. In the most straightforward way, my
> objections apply.
>
> On 12/23/2013 05:51 PM, Ryan Carboni wrote:
> > I think you misunderstood my statement. If time > 3 days, and after
> > 4 blocks have been mined, then difficulty would be reset.
> >
> > In theory, one would have to isolate roughly one percent of the
> > Bitcoin network's hashing power to do so. Which would indicate an
> > attack by a state actor as opposed to anything else. Arguably, the
> > safest way to run Bitcoin is through a proprietary dial-up
> > network.
> >
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.14 (GNU/Linux)
> Comment: GPGTools - http://gpgtools.org
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQIcBAEBAgAGBQJSuOs3AAoJEAdzVfsmodw4BwAP/0Ynq/SxNIBFFdL7RaSiE5KM
> zNRtlZJCYvmCXgKKtMyO+Ron+YGqY8yg8r0ifb6oqlJCG5t0msExym/CA9CYMV6V
> UnVaGaNkFrLSF1q8Dt6X4I9OSeCiBstahQOjPaerUycLTY2W/cKPblhCC0rvXrfI
> 3Fz3p6SHbCcNHw89w6ry3QG420+UNroFCpNu+Oa2YfWoZY2p91JLbuiUwXL5KEac
> PDskHGsb9q1vyAkCJ6eOp3MJfFP/Dy7mASVwPql/nzf2ceSDtO4dpngo0uNsCwFo
> QSWIRdWv4OiJk1OM6fjEj/51mebczgO0ShczRKk9QkX4FEFEqP/ARdbl8bSC4IsT
> /3s2HHiYDahEOMiXV5ao3kmBpyUR8p4erRbtwRzdZzOgGL37yxj8VGmY93bkVQNB
> zi2n3WCCju0a+gqREyaEFAM8kPIhx9++YNIddwQxK38njUSe2CzqM8t+28ZfseYl
> YnQeNFUfcmvzhxTXxgyoCuGF5HbFRTn/AallkYSPxYtxGq4WuLN36BS3cTv8wCLz
> sYTyuxWxjZ7CS8fx8MWilw72tQf9torwmrWJtjgRLFE3OvQxRjN+ppDV8cfC8UAB
> p0CGzBgVaw5yZ5LzCawQVTGWJdzs+ZPlQu8SO53dHhEtRAmdbFa0mMD2FrS/5Ih/
> YcwdP6Xm69HTgzCenu5F
> =HtRS
> -----END PGP SIGNATURE-----
>
--089e013a16a43faaca04ee42d122
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">It does take a state-level actor to apparently disconnect =
<i>multiple </i>miners from the rest of the network.<div><br></div><div>How=
many Bitcoin miners hash an entire percent or more of the Bitcoin network?=
What you're proposing is an attack at the highest levels of the intern=
et infrastructure.</div>
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Mon,=
Dec 23, 2013 at 6:02 PM, Mark Friedenbach <span dir=3D"ltr"><<a href=3D=
"mailto:mark@monetize.io" target=3D"_blank">mark@monetize.io</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"><div class=3D"im">-----BEGIN PGP SIGNED MESS=
AGE-----<br>
Hash: SHA1<br>
<br>
</div>Which would leave you entirely in the hands of your dialup provider.<=
br>
Or the manufacturer of your switch. Or your ISP's backbone provider.<br=
>
It does not take a state-level actor to do network attacks.<br>
<br>
BTW, what does "difficulty would be reset" mean? There are multip=
le<br>
ways to interpret that statement. In the most straightforward way, my<br>
objections apply.<br>
<div class=3D"im"><br>
On 12/23/2013 05:51 PM, Ryan Carboni wrote:<br>
> I think you misunderstood my statement. If time > 3 days, and after=
<br>
> 4 blocks have been mined, then difficulty would be reset.<br>
><br>
> In theory, one would have to isolate roughly one percent of the<br>
> Bitcoin network's hashing power to do so. Which would indicate an<=
br>
> attack by a state actor as opposed to anything else. Arguably, the<br>
> safest way to run Bitcoin is through a proprietary dial-up<br>
> network.<br>
><br>
</div><div class=3D"im">-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.14 (GNU/Linux)<br>
Comment: GPGTools - <a href=3D"http://gpgtools.org" target=3D"_blank">http:=
//gpgtools.org</a><br>
Comment: Using GnuPG with Thunderbird - <a href=3D"http://www.enigmail.net/=
" target=3D"_blank">http://www.enigmail.net/</a><br>
<br>
</div>iQIcBAEBAgAGBQJSuOs3AAoJEAdzVfsmodw4BwAP/0Ynq/SxNIBFFdL7RaSiE5KM<br>
zNRtlZJCYvmCXgKKtMyO+Ron+YGqY8yg8r0ifb6oqlJCG5t0msExym/CA9CYMV6V<br>
UnVaGaNkFrLSF1q8Dt6X4I9OSeCiBstahQOjPaerUycLTY2W/cKPblhCC0rvXrfI<br>
3Fz3p6SHbCcNHw89w6ry3QG420+UNroFCpNu+Oa2YfWoZY2p91JLbuiUwXL5KEac<br>
PDskHGsb9q1vyAkCJ6eOp3MJfFP/Dy7mASVwPql/nzf2ceSDtO4dpngo0uNsCwFo<br>
QSWIRdWv4OiJk1OM6fjEj/51mebczgO0ShczRKk9QkX4FEFEqP/ARdbl8bSC4IsT<br>
/3s2HHiYDahEOMiXV5ao3kmBpyUR8p4erRbtwRzdZzOgGL37yxj8VGmY93bkVQNB<br>
zi2n3WCCju0a+gqREyaEFAM8kPIhx9++YNIddwQxK38njUSe2CzqM8t+28ZfseYl<br>
YnQeNFUfcmvzhxTXxgyoCuGF5HbFRTn/AallkYSPxYtxGq4WuLN36BS3cTv8wCLz<br>
sYTyuxWxjZ7CS8fx8MWilw72tQf9torwmrWJtjgRLFE3OvQxRjN+ppDV8cfC8UAB<br>
p0CGzBgVaw5yZ5LzCawQVTGWJdzs+ZPlQu8SO53dHhEtRAmdbFa0mMD2FrS/5Ih/<br>
YcwdP6Xm69HTgzCenu5F<br>
=3DHtRS<br>
-----END PGP SIGNATURE-----<br>
</blockquote></div><br></div>
--089e013a16a43faaca04ee42d122--
|
