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
|
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 AB1FC67
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 2 Aug 2015 22:07:24 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wi0-f170.google.com (mail-wi0-f170.google.com
[209.85.212.170])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 8EB09143
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 2 Aug 2015 22:07:23 +0000 (UTC)
Received: by wicgj17 with SMTP id gj17so81113384wic.1
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 02 Aug 2015 15:07:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:sender:in-reply-to:references:date:message-id:subject
:from:to:content-type;
bh=im63or+wkfGUxxoNJcfcfxBCZa37NIq+NBhNt4Vp9mA=;
b=Amuc1+yYxOiW1dTZiN3lFZzFzHX8Obj+tV8CXAs8ou73y3+VQucYF3LOl96gbVMLIg
VDyVBsSCyPAdIGGr15iECEzTkNNzus2ehiiqBc109p3ZI/ypoXzgVKfvcLc5lz8wX57B
sR48j6wUKnbPNUPjLft8P1cpZ/9kzFs5NFWVg//Nv8isyKf/xXp/wG/+h2hdNERQTZsh
8C3mBlosafceW9tXfcDOg6p0bFJ8OPV3vqnItb1Vk0K7J4Dt648erFRuSsKENPTfFcRN
P1VwFz3TLvz19wtTa3cN1VIvyhfisyP3XVUJW9oeuwR9aNiY3IPQUPqU1gF5J/mcYSdA
2wTQ==
MIME-Version: 1.0
X-Received: by 10.180.96.230 with SMTP id dv6mr27945105wib.23.1438553242129;
Sun, 02 Aug 2015 15:07:22 -0700 (PDT)
Sender: dscotese@gmail.com
Received: by 10.27.184.134 with HTTP; Sun, 2 Aug 2015 15:07:22 -0700 (PDT)
In-Reply-To: <55BDF31D.1010803@mail.bihthai.net>
References: <20150731083943.Horde.68uT9J78H_PdIgIwQP5frA1@server47.web-hosting.com>
<CAPg+sBhFYJudy+m8+FqxTczj6W8Uc1pH1BsOqP0kgxmv-FMW0w@mail.gmail.com>
<bbdbc08925ca3416f0f9982466b98413@xbt.hk>
<CAPg+sBhQV7ymm3sDW44DWr1FEfgoGoTfMva1iTbZXHcf==mYbw@mail.gmail.com>
<55BDF31D.1010803@mail.bihthai.net>
Date: Sun, 2 Aug 2015 15:07:22 -0700
X-Google-Sender-Auth: 23AB0JB7G7Abn3LFfA9xRWAWg3I
Message-ID: <CAGLBAheCCuz+co3ZVqrVQyxiaPm399k+mvznrgGM4yghrgQ9zw@mail.gmail.com>
From: Dave Scotese <dscotese@litmocracy.com>
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=f46d04374917fcdd9f051c5b46f0
X-Spam-Status: No, score=-1.2 required=5.0 tests=BAYES_05,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] A compromise between BIP101 and Pieter's proposal
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: Sun, 02 Aug 2015 22:07:24 -0000
--f46d04374917fcdd9f051c5b46f0
Content-Type: text/plain; charset=UTF-8
It will help to assume that there is at least one group of evil people who
are investing in Bitcon's demise. Not because there are, but because there
might be. So let's assume they are making a set of a billion transactions,
or a trillion, and maintaining currently-being-legitimately-used hashing
power. When block size is large enough to frustrate other miners, this
hash power (or some piece of it) will be experimentally shifted to solving
a block containing an internally consistent subset of the prepared
trasnsactions to fill it - experimentally at first, but on the active
Bitcoin network. One seemingly random, bloated, useless (except for the
universal timestamp) block will be created and the evil group will measure
the effect on the mining community - client takedowns, market exits, and
whatever else interests them. Then they lie in wait, perhaps let out one
more to do another experiment, but with the goal of eventually catching us
unawares and doing as much damage to morale as possible.
Good concrete descriptions of the threats against which we want to guard
will be very helpful. Maybe there are already unit tests for such things
or requests for miners' reactions to them (as opposed to just the
software's behavior). My description might be a bit too long and perhaps
not a very good example, but do we have a place where such examples can be
constructed?
While we will do our best to guard against such nightmares, it's also
helpful to imagine what we will do if and when one of them ever actually
occurs. Yes, I'm paranoid; because those who like to control everything
are losing it.
Dave
On Sun, Aug 2, 2015 at 3:38 AM, Venzen Khaosan via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> +1 on every point, sipa
>
--f46d04374917fcdd9f051c5b46f0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div><div><div><div>It will help to assume that there is a=
t least one group of evil people who are investing in Bitcon's demise.=
=C2=A0 Not because there are, but because there might be.=C2=A0 So let'=
s assume they are making a set of a billion transactions, or a trillion, an=
d maintaining currently-being-legitimately-used hashing power.=C2=A0 When b=
lock size is large enough to frustrate other miners, this hash power (or so=
me piece of it) will be experimentally shifted to solving a block containin=
g an internally consistent subset of the prepared trasnsactions to fill it =
- experimentally at first, but on the active Bitcoin network.=C2=A0 One see=
mingly random, bloated, useless (except for the universal timestamp) block =
will be created and the evil group will measure the effect on the mining co=
mmunity - client takedowns, market exits, and whatever else interests them.=
=C2=A0 Then they lie in wait, perhaps let out one more to do another experi=
ment, but with the goal of eventually catching us unawares and doing as muc=
h damage to morale as possible.<br></div><br></div>Good concrete descriptio=
ns of the threats against which we want to guard will be very helpful.=C2=
=A0 Maybe there are already unit tests for such things or requests for mine=
rs' reactions to them (as opposed to just the software's behavior).=
=C2=A0 My description might be a bit too long and perhaps not a very good e=
xample, but do we have a place where such examples can be constructed?<br><=
br></div>While we will do our best to guard against such nightmares, it'=
;s also helpful to imagine what we will do if and when one of them ever act=
ually occurs.=C2=A0 Yes, I'm paranoid; because those who like to contro=
l everything are losing it.<br><br></div>Dave<br><div class=3D"gmail_extra"=
><br><div class=3D"gmail_quote">On Sun, Aug 2, 2015 at 3:38 AM, Venzen Khao=
san via bitcoin-dev <span dir=3D"ltr"><<a href=3D"mailto:bitcoin-dev@lis=
ts.linuxfoundation.org" target=3D"_blank">bitcoin-dev@lists.linuxfoundation=
.org</a>></span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D=
"">-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
</span>+1 on every point, sipa<br>
<div><div class=3D"h5"></div></div></blockquote></div><br></div></div>
--f46d04374917fcdd9f051c5b46f0--
|
