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
|
Return-Path: <gmaxwell@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 5843FD82
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 30 Aug 2015 03:25:09 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-io0-f178.google.com (mail-io0-f178.google.com
[209.85.223.178])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 8B17D185
for <bitcoin-dev@lists.linuxfoundation.org>;
Sun, 30 Aug 2015 03:25:08 +0000 (UTC)
Received: by iog7 with SMTP id 7so5021022iog.2
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 29 Aug 2015 20:25:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type:content-transfer-encoding;
bh=sLUjtaKqQvZDHc+gQ3L34rHAcpANQpVpuEjNo00Hr4E=;
b=0eottNd3G+DQGvyHo7ACVBJlFlav/IpPemZNg2pDs3Y3BcNzW16R8fGrnk5pjk0fvm
vr2G6reKJKAg3b2XaJAEA21/BQL632FYwSOnSp4dXkWe63N/Lc2E9zBjDKypA+yjuztH
Ji46zLMmTMUevYf/KbIIlPDSCL8vLWBvEfGZ10rWIcqdjADJVyVfTZg4w/fbJ4WiDpaH
5GExK/ki1aYa7uTTdBMG4kcf/GFRimMhy7rQSOu0OEQI6kso1kL4IZ2wH7oMOFksw+/A
BzSkZIN/slfsCWmIcQNI6Z91+iO7P9WvDk2p3E/wlJhkAI+q5HGimlgmzE3KmdI68Npt
8eNQ==
MIME-Version: 1.0
X-Received: by 10.107.32.76 with SMTP id g73mr3210613iog.134.1440905108016;
Sat, 29 Aug 2015 20:25:08 -0700 (PDT)
Received: by 10.107.19.86 with HTTP; Sat, 29 Aug 2015 20:25:07 -0700 (PDT)
In-Reply-To: <AD284610-4F40-445C-A074-CC94EDFFCBA8@gmx.com>
References: <CAEgR2PFB3h_8fr=d8HegRSD0XdooimhFKtLR4vKr2QXv+EwBfQ@mail.gmail.com>
<AD284610-4F40-445C-A074-CC94EDFFCBA8@gmx.com>
Date: Sun, 30 Aug 2015 03:25:07 +0000
Message-ID: <CAAS2fgRs5NVM2nHKNXbgMJa51tDq-6ZBc6XfaScyP45UPWTW_g@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Peter R <peter_r@gmx.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-Spam-Status: No, score=-0.8 required=5.0 tests=BAYES_40,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM,
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
Cc: "bitcoin-dev@lists.linuxfoundation.org Dev"
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Your Gmaxwell exchange
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, 30 Aug 2015 03:25:09 -0000
On Sun, Aug 30, 2015 at 1:43 AM, Peter R <peter_r@gmx.com> wrote:
> Dear Greg,
>
> I am moving our conversation into public as I've recently learned that
> you've been forwarding our private email conversation verbatim without
> my permission [I received permission from dpinna to share the email
> below that proves this fact].
Unfortunately, your work extensive as it was made at least two
non-disclosed or poorly-disclosed simplifying assumptions and a significant
system understanding error which, I believe, undermined it completely.
In short these were:
* You assume miners do not have the ability to change their level
centralization.
-- In fact they do, not just in theory but in pratice have responded
to orphaning this way in the past; and it is one of the major
concerns in this space.
* You assume the supply of bitcoin is infinite (that subsidy never
declines)
-- It declines geometrically, and must if the 21m limit is to be upheld.
(Though I think this is not equally important as the other concerns)
* You argue, incorrectly, that amount of information which must be
transmitted at the moment a block is discovered is proportional to the
block's size.
-- Instead the same information can be transmitted _in advance_, as
has been previously proposed, and various techniques can make doing
so arbitrarily efficient.
[I would encourage anyone who is interested to read the posted off-list
discussion]
I contacted you in private as a courtesy in the hope that it would be
a more productive pathway to improving our collective understanding; as wel=
l
as a courtesy to the readers of the list in consideration of traffic levels=
.
In one sense, this was a success: Our conversation concluded with you
enumerating a series of corrective actions that you would take:
--------
> 1. I will make it more clear that the results of the paper hinge on
> the assumption that block solutions are propagated across channels,
> and that the quantity of pure information communicated per solution
> is proportional to the amount of information contained within the block.
>
> 2. I will add a note [unless you ask me not to] something to the effect
> of "Greg Maxwell challenges the claim that the coding gain cannot
> be infinite=E2=80=A6" followed by a summary of the scenario you described=
.
> I will reference "personal communication." I will also run the note
> by you before I make the next revision public.
>
> 3. I will point out that if the coding gain can be made spectacularly
> high, that the propagation impedance in my model will become very small,
> and that although a fee market may strictly exist in the asymptotic
> sense, such a fee market may not be relevant (the phenomena in the paper
> would be negligible compared to the dynamics from some other effect).
>
> 4. [UNRELATED] I also plan to address Dave Hudson's objections in my
> next revision (the "you don't orphan your own block" point).
>
> Lastly, thank you for the note about what might happen when fees >
> rewards. I've have indeed been thinking about this. I believe it is
> outside the scope of the present paper, although I am doing some work
> on the topic. (Perhaps I'll add a bit more discussion on this topic
> to the present paper to get the reader thinking in this direction).
--------
To the best of my knowledge, you've taken none of these corrective
actions in the nearly month that has passed. I certainly understand being
backlogged, but you've also continued to make public comments about your
work seemingly (to me) in contradiction with the above corrective actions.
Today I discovered that another author spent their time extending your
work and wasn't made aware of these points. A result was that the other
author's work may require significant revisions.
I complained about this to you, again privately, and your (apparent)
response was to post to that thread stating that there was a
details-unspecified academic disagreement with me and "I look forward
to a white paper demonstrating otherwise!", in direct contradiction to
your remarks to me three weeks ago in private correspondence: In private
you said that your model may only hold in an asymptotic sense and that
"the phenomena in the paper (may) be negligible compared to the dynamics
from some other effect"; but in public you said /my/ position was
"academic".
At this point I thought continuing to withhold this information from
the other author was unreasonable and no longer justified by courtesy
to you, and I forwarded our complete discussion to the other author
with the comment "I'll forward you a set of private correspondence
that I've had with Peter R. I would recommend you take the time to
read it and consider it.".
I apologize if in doing so I've breached your confidence, none of the
material we discussed was a sort that I would have ordinarily considered
private, and you had already talked about making the product of our
communication published as part of your corrective actions.
I do not think it would be reasonable to demand that I spent time
repeating the same discussion again with the other author, or deprive
them of your side of it and/or the corrective actions which you had
said you would take but have not yet taken.
(In fact, I would argue that you were already obligated to share at least t=
he
substance of the discussion with the other author, both as part of your
commitment to me as well it being necessiary for intellectual progress.)
As you say, 'we are all here trying to learn about this new amazing
thing called Bitcoin'; and I'm not embarrassed to error towards doing
that and aiding others in doing so, but at the same time I am sorry
to have done so in a way which caused you some injury.
In any case, your prior proposed corrective actions seemed sufficient to me=
.
It surprises me, greatly, that you are failing to see the extreme
practicality of what I described to you, and that it does not meaningfully
diminish miner control of transaction selection-- but even without it your
remark that the proportionality could be arbitrarily small (Rather than
0, as I argue) is an adequate correction to your work, in my view.
I believe my time would be better spent actually _implementing_ improved
relaying described (and describe what was implemented) than continue
a purely academic debate with you over the (IMO) inconsequential difference
between epsilon and zero.
Cheers,
|
