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
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
|
Return-Path: <jameson.lopp@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 231651088
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 13 Feb 2018 15:45:58 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-oi0-f45.google.com (mail-oi0-f45.google.com
[209.85.218.45])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 6CF5B413
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 13 Feb 2018 15:45:57 +0000 (UTC)
Received: by mail-oi0-f45.google.com with SMTP id j188so14186560oib.6
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 13 Feb 2018 07:45:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to
:cc; bh=lyOQbVHOTUohRZXpRkU+CravQLuqRY+Xjr5b/ViiHjc=;
b=ZfIqw+b+tXk/wRWGosD9AAWaBbZoAu/pfk176TFIHfyQ1Y+6vHvoU6AVtIB/bNS7ZM
Sngoy6EKb21hcVeOEptvHtZzh4EsOl8NHtoairhZQn2d/fTl3c3KpH/Ag3wrMfZNXpOQ
8Xs3+cFRKdkmbfoXJFIj9OeNjKyZw3n4br6Dk6NjkfxkDEwCPj/QG/vp30qKorEKm010
tCbFAUvz2EvCUdQLpbuA7r8sGbHU/qVEiDuwUz971Lcn0h7Nm0MGVJpTRzmY1SrWqqQR
GI5RdG6bmrjN7jpy9uGplYkZ4MrpnKIJyQsGugrpV4AXuBTzaEny20WAtrtfsd7aMeLA
DWnA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to:cc;
bh=lyOQbVHOTUohRZXpRkU+CravQLuqRY+Xjr5b/ViiHjc=;
b=i6SmH0r/dAkeZ2mjrJMsINDx5hw10jlOy8yv7I+uNj2NdqIa4jKiO5xFcTpZxvF0qx
/mkbXR5VHs1uhGiXdh5NonNUYKUjykdwR5x28olwxRlfMfSlepqbpfaWLcgN9h7DzWJq
v3qmsAC7Bj1DZT5mqGKLwsYB1qdyrzOMfg5YPPN6R3vdllgLI7x4T1GJueqLSmNGSkCh
wuBlzE/VuC9wRnR86k50vz5mAjnSRDkvbjWKDCxdMrJm/td3C4l+Pj7JSPEybm/8ks4j
IMxixXdEWozafrVMMxPNnaA7+vYtn6xo+x8GA5IKq/6k3D2ThZOWuh2stHHTCMi/ZNSf
liMA==
X-Gm-Message-State: APf1xPBliU9guW8u+CWOyKETjFqqsXHOOyQvJEdHKBBIVxCXxoFCbEGH
wXMw9O0+CWjemnNZG41IRxvy6nc5/7dHwYMSsqWi3g==
X-Google-Smtp-Source: AH8x226RCAaR/2xsiwN2Qg1eHw1pWoN1w3GA0OviZHdEYrMqt739qkFzJkhH2PZCPFnrn8OdyWUYvUaCXup/vdnTkqM=
X-Received: by 10.202.204.212 with SMTP id c203mr1123417oig.156.1518536756524;
Tue, 13 Feb 2018 07:45:56 -0800 (PST)
MIME-Version: 1.0
Received: by 10.74.129.89 with HTTP; Tue, 13 Feb 2018 07:45:55 -0800 (PST)
In-Reply-To: <CAJQ0i9vDWqryxni6sEx1NDHjLpUCCH=F=t0s2p-seYYtyhuosw@mail.gmail.com>
References: <65F92B37-48C1-4CD5-8F17-47BF9BD231A9@gmail.com>
<CAAt2M1-fEnQxjX40c-sjUYpfLpJtS-fy5t244vUOZSb8Pm=MrQ@mail.gmail.com>
<CADL_X_cNdhydrn0D0vXSXK1s42dC7-n_7oW2TQJcpvkG6Oa0ow@mail.gmail.com>
<CAJQ0i9vDWqryxni6sEx1NDHjLpUCCH=F=t0s2p-seYYtyhuosw@mail.gmail.com>
From: Jameson Lopp <jameson.lopp@gmail.com>
Date: Tue, 13 Feb 2018 10:45:55 -0500
Message-ID: <CADL_X_c=+YtLfyOn3fucyQEc5wtpmpXMNaJzvCPOc+cw-POOkw@mail.gmail.com>
To: Brian Lockhart <brianlockhart@gmail.com>
Content-Type: multipart/alternative; boundary="001a1134f72ef37b02056519e32d"
X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HTML_MESSAGE,
RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>,
=?UTF-8?Q?JOSE_FEMENIAS_CA=C3=91UELO?= <jose.femenias@gmail.com>
Subject: Re: [bitcoin-dev] Possible change to the MIT license
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol 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: Tue, 13 Feb 2018 15:45:58 -0000
--001a1134f72ef37b02056519e32d
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Anyone who feels so inclined is free to "pick up the mantle" and defend
Bitcoin against perceived social attacks. I don't think that Bitcoin
protocol developers have any particular responsibility to do so, and as
such this particular discussion is likely going to quickly veer off-topic
for this mailing list.
On Tue, Feb 13, 2018 at 10:37 AM, Brian Lockhart <brianlockhart@gmail.com>
wrote:
> > I don't think that Bitcoin should be reliant upon courts or governments
> to defend itself against attacks of any form.
>
> Agree 100%. Plus yeah, lotsa luck getting any success via those channels.=
..
>
> But assuming the answer to the perceived problem is to =E2=80=9Cfight fir=
e with
> fire=E2=80=9D (using social / marketing based efforts) who =E2=80=9Cshoul=
d=E2=80=9D pick up the
> mantle here? Without inciting riots by asking the question, wouldn=E2=80=
=99t that
> ostensibly be something the Bitcoin Foundation would lead on here? <ducks
> and runs for cover>
>
> In any case, it=E2=80=99s frustrating to watch the ongoing FUD and scamme=
ry going
> unanswered in any =E2=80=9Cofficial=E2=80=9D capacity.
>
>
> On February 13, 2018 at 7:25:35 AM, Jameson Lopp via bitcoin-dev (
> bitcoin-dev@lists.linuxfoundation.org) wrote:
>
> If I'm understanding the problem being stated correctly:
>
> "Bitcoin is under a branding attack by fork coins."
>
> The proposed solution is to disincentivize fork coins from using the word
> Bitcoin by altering the license terms. I'm not a lawyer, but it seems to =
me
> that the words of the license are basically useless unless there is an
> entity that intends to make use of court systems to threaten noncompliant
> projects into submission.
>
> In my opinion, the perceived attack on Bitcoin here is social /
> marketing-based, thus it makes sense that any defense against said attack
> should also be social / marketing-based. I don't think that Bitcoin shoul=
d
> be reliant upon courts or governments to defend itself against attacks of
> any form.
>
> On Tue, Feb 13, 2018 at 9:25 AM, Natanael via bitcoin-dev <
> bitcoin-dev@lists.linuxfoundation.org> wrote:
>
>>
>>
>> Den 13 feb. 2018 15:07 skrev "JOSE FEMENIAS CA=C3=91UELO via bitcoin-dev=
" <
>> bitcoin-dev@lists.linuxfoundation.org>:
>>
>> ***
>> NO PART OF THIS SOFTWARE CAN BE INCLUDED IN ANY OTHER PROJECT THAT USES
>> THE NAME BITCOIN AS PART OF ITS NAME AND/OR ITS MARKETING MATERIAL UNLES=
S
>> THE SOFTWARE PRODUCED BY THAT PROJECT IS FULLY COMPATIBLE WITH THE BITCO=
IN
>> (CORE) BLOCKCHAIN
>> ***
>>
>>
>> That's better solved with trademarks. (whoever would be the trademark
>> holder - Satoshi?)
>>
>> This would also prohibit any reimplementation that's not formally
>> verified to be perfectly compatible from using the name.
>>
>> It also adds legal uncertainty.
>>
>> Another major problem is that it neither affects anybody forking older
>> versions of Bitcoin, not people using existing independent blockchain
>> implementations and renaming them Bitcoin-Whatsoever.
>>
>> And what happens when an old version is technically incompatible with a
>> future version by the Core team due to not understanding various new
>> softforks? Which version wins the right to the name?
>>
>> Also, being unable to even mention Bitcoin is overkill.
>>
>> The software license also don't affect the blockchain data.
>>
>>
>> _______________________________________________
>> bitcoin-dev mailing list
>> bitcoin-dev@lists.linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>>
>>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
--001a1134f72ef37b02056519e32d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Anyone who feels so inclined is free to "pick up the =
mantle" and defend Bitcoin against perceived social attacks. I don'=
;t think that Bitcoin protocol developers have any particular responsibilit=
y to do so, and as such this particular discussion is likely going to quick=
ly veer off-topic for this mailing list.</div><div class=3D"gmail_extra"><b=
r><div class=3D"gmail_quote">On Tue, Feb 13, 2018 at 10:37 AM, Brian Lockha=
rt <span dir=3D"ltr"><<a href=3D"mailto:brianlockhart@gmail.com" target=
=3D"_blank">brianlockhart@gmail.com</a>></span> wrote:<br><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p=
adding-left:1ex"><div style=3D"word-wrap:break-word;line-break:after-white-=
space"><span class=3D""><div id=3D"m_459735694557790465bloop_customfont" st=
yle=3D"font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);mar=
gin:0px;line-height:auto">> I don't think that Bitcoin should be rel=
iant upon courts or governments to defend itself against attacks of any for=
m.</div><div id=3D"m_459735694557790465bloop_customfont" style=3D"font-fami=
ly:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-hei=
ght:auto"><br></div></span><div id=3D"m_459735694557790465bloop_customfont"=
style=3D"font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);=
margin:0px;line-height:auto">Agree 100%. Plus yeah, lotsa luck getting any =
success via those channels...</div><div id=3D"m_459735694557790465bloop_cus=
tomfont" style=3D"font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0=
,0,1.0);margin:0px;line-height:auto"><br></div><div id=3D"m_459735694557790=
465bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size:13px;co=
lor:rgba(0,0,0,1.0);margin:0px;line-height:auto">But assuming the answer to=
the perceived problem is to =E2=80=9Cfight fire with fire=E2=80=9D (using =
social / marketing based efforts) who =E2=80=9Cshould=E2=80=9D pick up the =
mantle here? Without inciting riots by asking the question, wouldn=E2=80=99=
t that ostensibly be something the Bitcoin Foundation would lead on here? &=
lt;ducks and runs for cover></div><div id=3D"m_459735694557790465bloop_c=
ustomfont" style=3D"font-family:Helvetica,Arial;font-size:13px;color:rgba(0=
,0,0,1.0);margin:0px;line-height:auto"><br></div><div id=3D"m_4597356945577=
90465bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size:13px;=
color:rgba(0,0,0,1.0);margin:0px;line-height:auto">In any case, it=E2=80=99=
s frustrating to watch the ongoing FUD and scammery going unanswered in any=
=E2=80=9Cofficial=E2=80=9D capacity.</div><div><div class=3D"h5"> <br> <di=
v class=3D"m_459735694557790465bloop_sign" id=3D"m_459735694557790465bloop_=
sign_1518536036721418752"></div> <br><p class=3D"m_459735694557790465airmai=
l_on">On February 13, 2018 at 7:25:35 AM, Jameson Lopp via bitcoin-dev (<a =
href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">bit=
coin-dev@lists.<wbr>linuxfoundation.org</a>) wrote:</p> <blockquote type=3D=
"cite" class=3D"m_459735694557790465clean_bq"><span><div><div></div><div>
<div dir=3D"ltr">If I'm understanding the problem being stated
correctly:<br>
<br>
"Bitcoin is under a branding attack by fork coins."
<div><br></div>
<div>The proposed solution is to disincentivize fork coins from
using the word Bitcoin by altering the license terms. I'm not a
lawyer, but it seems to me that the words of the license are
basically useless unless there is an entity that intends to make
use of court systems to threaten noncompliant projects into
submission.</div>
<div><br></div>
<div>In my opinion, the perceived attack on Bitcoin here is social
/ marketing-based, thus it makes sense that any defense against
said attack should also be social / marketing-based. I don't think
that Bitcoin should be reliant upon courts or governments to defend
itself against attacks of any form.</div>
</div>
<div class=3D"gmail_extra"><br>
<div class=3D"gmail_quote">On Tue, Feb 13, 2018 at 9:25 AM, Natanael
via bitcoin-dev <span dir=3D"ltr"><<a href=3D"mailto:bitcoin-dev@lists.l=
inuxfoundation.org" target=3D"_blank">bitcoin-dev@lists.<wbr>linuxfoundatio=
n.org</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 dir=3D"auto">
<div><span><br></span>
<div class=3D"gmail_extra"><span><br></span>
<div class=3D"gmail_quote"><span>Den 13 feb. 2018 15:07
skrev "JOSE FEMENIAS CA=C3=91UELO via bitcoin-dev" <<a href=3D=
"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">bitcoin-de=
v@lists.linuxfounda<wbr>tion.org</a>>:</span>
<blockquote class=3D"m_459735694557790465m_4333531158757201305quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span>***<br>
NO PART OF THIS SOFTWARE CAN BE INCLUDED IN ANY OTHER PROJECT THAT
USES THE NAME BITCOIN AS PART OF ITS NAME AND/OR ITS MARKETING
MATERIAL UNLESS THE SOFTWARE PRODUCED BY THAT PROJECT IS FULLY
COMPATIBLE WITH THE BITCOIN (CORE) BLOCKCHAIN<br>
***<br></span></blockquote>
</div>
</div>
</div>
<div dir=3D"auto"><span><br></span></div>
<div dir=3D"auto">That's better solved with trademarks. (whoever
would be the trademark holder - Satoshi?)=C2=A0=C2=A0</div>
<div dir=3D"auto"><br></div>
<div dir=3D"auto">This would also prohibit any reimplementation
that's not formally verified to be perfectly compatible from using
the name.=C2=A0</div>
<div dir=3D"auto"><br></div>
<div dir=3D"auto">It also adds legal uncertainty.=C2=A0</div>
<div dir=3D"auto"><br></div>
<div dir=3D"auto">Another major problem is that it neither affects
anybody forking older versions of Bitcoin, not people using
existing independent blockchain implementations and renaming them
Bitcoin-Whatsoever.=C2=A0</div>
<div dir=3D"auto"><br></div>
<div dir=3D"auto">And what happens when an old version is technically
incompatible with a future version by the Core team due to not
understanding various new softforks? Which version wins the right
to the name?=C2=A0</div>
<div dir=3D"auto"><br></div>
<div dir=3D"auto">Also, being unable to even mention Bitcoin is
overkill.=C2=A0</div>
<div dir=3D"auto"><br></div>
<div dir=3D"auto">The software license also don't affect the
blockchain data.=C2=A0</div>
<div dir=3D"auto"><br></div>
<div dir=3D"auto">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote">
<blockquote class=3D"m_459735694557790465m_4333531158757201305quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
</blockquote>
</div>
</div>
</div>
</div>
<br>
______________________________<wbr>_________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">=
bitcoin-dev@lists.linuxfoundat<wbr>ion.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.<wbr>org=
/mailman/listinfo/bitcoin-d<wbr>ev</a><br>
<br></blockquote>
</div>
<br></div>
______________________________<wbr>_________________
<br>bitcoin-dev mailing list
<br><a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_bla=
nk">bitcoin-dev@lists.<wbr>linuxfoundation.org</a>
<br><a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-d=
ev" target=3D"_blank">https://lists.linuxfoundation.<wbr>org/mailman/listin=
fo/bitcoin-<wbr>dev</a>
<br></div></div></span></blockquote></div></div></div>
</blockquote></div><br></div>
--001a1134f72ef37b02056519e32d--
|