summaryrefslogtreecommitdiff
path: root/52/d50f174a8325db6245407cb2689ab317b94584
blob: 55cf2e670e6dabf09e455f37536481b86ea2b596 (plain)
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
Return-Path: <brianlockhart@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 34A95E25
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue, 13 Feb 2018 15:37:12 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-oi0-f41.google.com (mail-oi0-f41.google.com
	[209.85.218.41])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 5B7C1D0
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue, 13 Feb 2018 15:37:11 +0000 (UTC)
Received: by mail-oi0-f41.google.com with SMTP id t135so1494071oif.8
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue, 13 Feb 2018 07:37:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
	h=from:in-reply-to:references:mime-version:date:message-id:subject:to
	:cc; bh=x8QaDRHehropbXGBrTR0rDFAe0F3p7Hr4JNURHj2irU=;
	b=l+YYL4U6WwbB95BjFLosVeH0c3dg5j/DacT1epVPbWApKrNuD1gxBPIYk902vhrJrD
	DOWcp7rPt0+DfDAooZx1dt1xmF9BP9kE3vSKH0o/Zp49c/a8eG61qASPZaePmxdm9Fi1
	V76qdBtA6iT9g44WiQ4rGfM9q4UTt8MZfpBCCjNMTOkCivVspOr3RX9eQWMfW2vdyRJh
	zNuNqlfGwxVIY9UuattxWBBkUBNuTIF/AVyqOEHshyXhx1kUqgXiv8Ua9g5h5HYBbsia
	3nMDz61ekqjOI2NLnmURHGiehaTAN67nI6pITfz0JuxK1eh16ZV7H6JLeQh3ZUeDTwpz
	Ho+g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:from:in-reply-to:references:mime-version:date
	:message-id:subject:to:cc;
	bh=x8QaDRHehropbXGBrTR0rDFAe0F3p7Hr4JNURHj2irU=;
	b=AkoSxr6VaqQCJnR6qgu6lIDnGzwsKjG0rd2hLcsWB7OPbn1bSQjIEnCLv/UYbaAhSm
	ljY8SwsdxUfONpu1R/jjyqow+awKP/ZSWTOmn+EEWKk5/jmMFZNpgKA6zUmq8qMzkr/d
	1ZlhKKq2NUkygGwynk4PCs71WCpkZd7vK9u98Lvs1qBmwIEn3DOD1QDjEoOIHdRQ6Mbg
	uC69WYrmTE+rdqtCfPYgkC4saW/tDZcobpfFyjm+p8ZO3ocGMJkbX5+oYQhvYZjYalJJ
	V5qN6rQV20qXW2IxOF5S/d1QcYPrcsnkNNvjP7MW7rUrIeAbHxx1N9meq155TdjnGpsB
	RCCg==
X-Gm-Message-State: APf1xPCX1D61zXlK8I0hHBlawLyOccDmb44v3/bh/k/VuYBE0wp9MHVN
	sLS8y0wBnsHADMW2yRPY/HkUuKtKtvsQ59iUX7s=
X-Google-Smtp-Source: AH8x224f8tbUyMYGBk9gQxfp1+vNHOjSYSi8WEnEST4r0GLs/ZTfwpzIp39A+7KGgBbGRXDHvry+kbPrGiRaotBOxeM=
X-Received: by 10.202.184.130 with SMTP id i124mr1102485oif.197.1518536230478; 
	Tue, 13 Feb 2018 07:37:10 -0800 (PST)
Received: from 1058052472880 named unknown by gmailapi.google.com with
	HTTPREST; Tue, 13 Feb 2018 07:37:09 -0800
From: Brian Lockhart <brianlockhart@gmail.com>
In-Reply-To: <CADL_X_cNdhydrn0D0vXSXK1s42dC7-n_7oW2TQJcpvkG6Oa0ow@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>
X-Mailer: Airmail (467)
MIME-Version: 1.0
Date: Tue, 13 Feb 2018 07:37:09 -0800
Message-ID: <CAJQ0i9vDWqryxni6sEx1NDHjLpUCCH=F=t0s2p-seYYtyhuosw@mail.gmail.com>
To: Jameson Lopp <jameson.lopp@gmail.com>, Natanael <natanael.l@gmail.com>, 
	Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="001a113ce0f298aa11056519c41b"
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, 
	UNPARSEABLE_RELAY autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
X-Mailman-Approved-At: Tue, 13 Feb 2018 16:22:39 +0000
Cc: =?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:37:12 -0000

--001a113ce0f298aa11056519c41b
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

> 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 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? <ducks
and runs for cover>

In any case, it=E2=80=99s frustrating to watch the ongoing FUD and scammery=
 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 should
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 UNLESS
> THE SOFTWARE PRODUCED BY THAT PROJECT IS FULLY COMPATIBLE WITH THE BITCOI=
N
> (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 verifie=
d
> 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

--001a113ce0f298aa11056519c41b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style>=
</head><body style=3D"word-wrap:break-word;line-break:after-white-space"><d=
iv id=3D"bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size:1=
3px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">&gt; I don&#39;t thi=
nk that Bitcoin should be reliant upon courts or governments to defend itse=
lf against attacks of any form.</div><div id=3D"bloop_customfont" 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"bloop_customfont" style=3D"font-fam=
ily:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-he=
ight:auto">Agree 100%. Plus yeah, lotsa luck getting any success via those =
channels...</div><div id=3D"bloop_customfont" style=3D"font-family:Helvetic=
a,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto"><=
br></div><div id=3D"bloop_customfont" style=3D"font-family:Helvetica,Arial;=
font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">But assum=
ing 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 questi=
on, wouldn=E2=80=99t that ostensibly be something the Bitcoin Foundation wo=
uld lead on here? &lt;ducks and runs for cover&gt;</div><div id=3D"bloop_cu=
stomfont" 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"bloop_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=99s frustrating to watc=
h the ongoing FUD and scammery going unanswered in any =E2=80=9Cofficial=E2=
=80=9D capacity.</div> <br> <div class=3D"bloop_sign" id=3D"bloop_sign_1518=
536036721418752"></div> <br><p class=3D"airmail_on">On February 13, 2018 at=
 7:25:35 AM, Jameson Lopp via bitcoin-dev (<a href=3D"mailto:bitcoin-dev@li=
sts.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org</a>) wrote:<=
/p> <blockquote type=3D"cite" class=3D"clean_bq"><span><div><div></div><div=
>


<title></title>


<div dir=3D"ltr">If I&#39;m understanding the problem being stated
correctly:<br>
<br>
&quot;Bitcoin is under a branding attack by fork coins.&quot;
<div><br></div>
<div>The proposed solution is to disincentivize fork coins from
using the word Bitcoin by altering the license terms. I&#39;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&#39;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">&lt;<a href=3D"mailto:bitcoin-dev@lists.l=
inuxfoundation.org" target=3D"_blank">bitcoin-dev@lists.linuxfoundation.org=
</a>&gt;</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 class=3D""><br></span>
<div class=3D"gmail_extra"><span class=3D""><br></span>
<div class=3D"gmail_quote"><span class=3D"">Den 13 feb. 2018 15:07
skrev &quot;JOSE FEMENIAS CA=C3=91UELO via bitcoin-dev&quot; &lt;<a href=3D=
"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">bitcoin-de=
v@lists.<wbr>linuxfoundation.org</a>&gt;:</span>
<blockquote class=3D"m_4333531158757201305quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex">
<span class=3D"">***<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 class=3D""><br></span></div>
<div dir=3D"auto">That&#39;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&#39;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&#39;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_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">bitcoin-dev@lists.=
<wbr>linuxfoundation.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-<wbr>dev</a><br>

<br></blockquote>
</div>
<br></div>


_______________________________________________
<br>bitcoin-dev mailing list
<br><a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@li=
sts.linuxfoundation.org</a>
<br><a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-d=
ev">https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev</a>
<br></div></div></span></blockquote></body></html>

--001a113ce0f298aa11056519c41b--