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
|
Return-Path: <vitteaymeric@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 80E1BFA6
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 13 Feb 2018 15:45:18 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wm0-f41.google.com (mail-wm0-f41.google.com [74.125.82.41])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 76C2718A
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 13 Feb 2018 15:45:17 +0000 (UTC)
Received: by mail-wm0-f41.google.com with SMTP id j199so4750658wmj.2
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 13 Feb 2018 07:45:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=subject:to:cc:references:from:message-id:date:user-agent
:mime-version:in-reply-to:content-language;
bh=ZCcLzlU8ygiAiykuam+5bRYGkJeJ/7VtdMQ4LkK+8e8=;
b=cV/usUTI2kgVvRxMN9BcJXGcT26d5x4GG33JvkE7W3Sz948yoMBAhRLVCX35Hlk9+h
DLn8r0rfIQPI1haoiz01RUgH/SE08ecOsNVT6OL6vn3qPbIn6hpqvi3r2+wR6z5v3vmm
AbXfxjzCAcxgzdrTJtdHcdt9hhCmXvY1RcDGyKBIDA+FwKmwEa4z0NJlnpLNQe11dwS9
JnV0xtT/S0ZRsvIJ08ytMHOOBhkRe/lRvpyPyHQkDnot4CZQ9gQoqlx5NFQsXswOKl9C
74/kPAKUlz5cII1sQlfC6HCFhyZuCa4t/2wumIcJrPEJbS90geMJHeVOM2s+QLnCkpsy
2FCg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:subject:to:cc:references:from:message-id:date
:user-agent:mime-version:in-reply-to:content-language;
bh=ZCcLzlU8ygiAiykuam+5bRYGkJeJ/7VtdMQ4LkK+8e8=;
b=ND8gADbG+csGKEK5oTDWsUo66E+YcJSPN+0nlTCwnWOyDELUiNOLlntmbILFyDoeSQ
v474RyS+foTJHXi0lBtJ04IXJ6hHiiJ2q/xBBeXwEGXfrK9GZdJyI4l+goC2DGjxGWmN
uRoLNwMGdj6JbzOaxU0KbyhE7gfFeI/b4X290erM0KqsCs3RSAIt7+pKXVAnvL+r0f6F
0EERnE3qJzLwM/hvj5xoZeGaydKQL29as63re+a8GfjOGuH4oFMdU0UoPcMiRP18mh/Y
y5aFQRI+2880yeozMBxo6krwSkaD8T7yKVN+NZbTvRo+9ZFBDoI/LBBzON+/QxVp23Ds
Egfg==
X-Gm-Message-State: APf1xPAUNb5zAwtKAVAIc4//8k+iLFMr5ohjvnRxoTbmOr+7gGaHBKdS
w51UGoM2YQR5Ep/HU8TiGk/aTA==
X-Google-Smtp-Source: AH8x227vqhI86MuT4sjIbmG0by3yNJrkj0oQGKnsc/kFrM5lRyl37nXO9c9RnSFdgyCyqOMNwb7l1w==
X-Received: by 10.80.148.49 with SMTP id p46mr2622642eda.237.1518536716056;
Tue, 13 Feb 2018 07:45:16 -0800 (PST)
Received: from ?IPv6:2a01:cb1d:5c:1600:9d6d:71b2:cb71:cb17?
([2a01:cb1d:5c:1600:9d6d:71b2:cb71:cb17])
by smtp.googlemail.com with ESMTPSA id
z8sm6291958edi.11.2018.02.13.07.45.14
(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Tue, 13 Feb 2018 07:45:15 -0800 (PST)
To: Jameson Lopp <jameson.lopp@gmail.com>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>,
Natanael <natanael.l@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>
From: Aymeric Vitte <vitteaymeric@gmail.com>
Message-ID: <267a18b8-707d-8f78-1cff-ba3ed57684c3@gmail.com>
Date: Tue, 13 Feb 2018 16:45:17 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.3; rv:52.0) Gecko/20100101
Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <CADL_X_cNdhydrn0D0vXSXK1s42dC7-n_7oW2TQJcpvkG6Oa0ow@mail.gmail.com>
Content-Type: multipart/alternative;
boundary="------------B8669FE51FBC253660A0603E"
Content-Language: fr
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: =?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:18 -0000
This is a multi-part message in MIME format.
--------------B8669FE51FBC253660A0603E
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
No, the problem is not bitcoin being under any kind of attack by the
forks for me, but the forks fooling people because, again, reusing the
bitcoin core code is too easy
I don't know if there can be a legal solution to this which would keep
some open source aspect of the code, but at least it deserves to be studied
Le 13/02/2018 à 16:24, Jameson Lopp via bitcoin-dev a écrit :
> 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
> <mailto:bitcoin-dev@lists.linuxfoundation.org>> wrote:
>
>
>
> Den 13 feb. 2018 15:07 skrev "JOSE FEMENIAS CAÑUELO via
> bitcoin-dev" <bitcoin-dev@lists.linuxfoundation.org
> <mailto: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 BITCOIN (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
> <mailto:bitcoin-dev@lists.linuxfoundation.org>
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> <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
--
Bitcoin transactions made simple: https://github.com/Ayms/bitcoin-transactions
Zcash wallets made simple: https://github.com/Ayms/zcash-wallets
Bitcoin wallets made simple: https://github.com/Ayms/bitcoin-wallets
Get the torrent dynamic blocklist: http://peersm.com/getblocklist
Check the 10 M passwords list: http://peersm.com/findmyass
Anti-spies and private torrents, dynamic blocklist: http://torrent-live.org
Peersm : http://www.peersm.com
torrent-live: https://github.com/Ayms/torrent-live
node-Tor : https://www.github.com/Ayms/node-Tor
GitHub : https://www.github.com/Ayms
--------------B8669FE51FBC253660A0603E
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>No, the problem is not bitcoin being under any kind of attack by
the forks for me, but the forks fooling people because, again,
reusing the bitcoin core code is too easy</p>
<p>I don't know if there can be a legal solution to this which would
keep some open source aspect of the code, but at least it deserves
to be studied<br>
</p>
<br>
<div class="moz-cite-prefix">Le 13/02/2018 à 16:24, Jameson Lopp via
bitcoin-dev a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:CADL_X_cNdhydrn0D0vXSXK1s42dC7-n_7oW2TQJcpvkG6Oa0ow@mail.gmail.com">
<div dir="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="gmail_extra"><br>
<div class="gmail_quote">On Tue, Feb 13, 2018 at 9:25 AM,
Natanael via bitcoin-dev <span dir="ltr"><<a
href="mailto:bitcoin-dev@lists.linuxfoundation.org"
target="_blank" moz-do-not-send="true">bitcoin-dev@lists.linuxfoundation.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="auto"><span class="">
<div><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">Den 13 feb. 2018 15:07
skrev "JOSE FEMENIAS CAÑUELO via bitcoin-dev" <<a
href="mailto:bitcoin-dev@lists.linuxfoundation.org" target="_blank"
moz-do-not-send="true">bitcoin-dev@lists.<wbr>linuxfoundation.org</a>>:
<blockquote class="m_4333531158757201305quote"
style="margin:0 0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">
***<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>
</blockquote>
</div>
</div>
</div>
<div dir="auto"><br>
</div>
</span>
<div dir="auto">That's better solved with trademarks.
(whoever would be the trademark holder - Satoshi?) </div>
<div dir="auto"><br>
</div>
<div dir="auto">This would also prohibit any
reimplementation that's not formally verified to be
perfectly compatible from using the name. </div>
<div dir="auto"><br>
</div>
<div dir="auto">It also adds legal uncertainty. </div>
<div dir="auto"><br>
</div>
<div dir="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. </div>
<div dir="auto"><br>
</div>
<div dir="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? </div>
<div dir="auto"><br>
</div>
<div dir="auto">Also, being unable to even mention Bitcoin
is overkill. </div>
<div dir="auto"><br>
</div>
<div dir="auto">The software license also don't affect the
blockchain data. </div>
<div dir="auto"><br>
</div>
</div>
<br>
______________________________<wbr>_________________<br>
bitcoin-dev mailing list<br>
<a href="mailto:bitcoin-dev@lists.linuxfoundation.org"
moz-do-not-send="true">bitcoin-dev@lists.<wbr>linuxfoundation.org</a><br>
<a
href="https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.linuxfoundation.<wbr>org/mailman/listinfo/bitcoin-<wbr>dev</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
bitcoin-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org</a>
<a class="moz-txt-link-freetext" href="https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev">https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Bitcoin transactions made simple: <a class="moz-txt-link-freetext" href="https://github.com/Ayms/bitcoin-transactions">https://github.com/Ayms/bitcoin-transactions</a>
Zcash wallets made simple: <a class="moz-txt-link-freetext" href="https://github.com/Ayms/zcash-wallets">https://github.com/Ayms/zcash-wallets</a>
Bitcoin wallets made simple: <a class="moz-txt-link-freetext" href="https://github.com/Ayms/bitcoin-wallets">https://github.com/Ayms/bitcoin-wallets</a>
Get the torrent dynamic blocklist: <a class="moz-txt-link-freetext" href="http://peersm.com/getblocklist">http://peersm.com/getblocklist</a>
Check the 10 M passwords list: <a class="moz-txt-link-freetext" href="http://peersm.com/findmyass">http://peersm.com/findmyass</a>
Anti-spies and private torrents, dynamic blocklist: <a class="moz-txt-link-freetext" href="http://torrent-live.org">http://torrent-live.org</a>
Peersm : <a class="moz-txt-link-freetext" href="http://www.peersm.com">http://www.peersm.com</a>
torrent-live: <a class="moz-txt-link-freetext" href="https://github.com/Ayms/torrent-live">https://github.com/Ayms/torrent-live</a>
node-Tor : <a class="moz-txt-link-freetext" href="https://www.github.com/Ayms/node-Tor">https://www.github.com/Ayms/node-Tor</a>
GitHub : <a class="moz-txt-link-freetext" href="https://www.github.com/Ayms">https://www.github.com/Ayms</a></pre>
</body>
</html>
--------------B8669FE51FBC253660A0603E--
|
