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
|
Return-Path: <jose.femenias@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id BB3F2F58
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 13 Feb 2018 12:25:59 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wm0-f65.google.com (mail-wm0-f65.google.com [74.125.82.65])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id E83FE477
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 13 Feb 2018 12:25:57 +0000 (UTC)
Received: by mail-wm0-f65.google.com with SMTP id f3so15725671wmc.1
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 13 Feb 2018 04:25:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=from:content-transfer-encoding:mime-version:subject:message-id:date
:to; bh=hF4saOb3YNJ6hMFSWUyQ6Fxtz2NQGkTgup8dwMZs8v0=;
b=XyGKOKJIUkpFCjyBb3GPlWXAZIoEvmNGPlLDxcuI7Ybrr0b35/S9d/Kf1dgj8PzFSZ
/Lh3o9xKj8uWDgayA4CzC6xMhWHwnkJOf3huaeoRTn5eSKldbXi0Lufyf7OGUDP89e14
NBLMpPkrTYG3B3rftb/XudFqI4Cr3e5zlsVYytsIpOb86vOjs0A/w8Pjw19fbxV1W9fn
PWnSYcNXreK9/LrSos3weN75wo1CIwmpR8jPCDxNPguI6PUJguBpU119lutBzujynAOd
3gCBpjTMzPzBFlJIayI/qLvpCrwh9HEE7+NAGCujlOHhQcmB4N4soCl/tKzKPQ26nTz9
v4WQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:from:content-transfer-encoding:mime-version
:subject:message-id:date:to;
bh=hF4saOb3YNJ6hMFSWUyQ6Fxtz2NQGkTgup8dwMZs8v0=;
b=HFFpUV565+2/JCUMmIjmhy1SS3GmfXR5ZMgGBmvpSW7yd+nQuDAMKcspdBbi/yc/57
rgBAscq6kxxA6/qF2ln9L6qvHOJzb7zloDaz7W3YrX0cMnbMP6yX7Y/yWo6CJTPd2n2K
mojDD0EtgUx7dwIBNw7qQDPGBa3p8JlQAMlvPY9hjqUUJoJo4M9wc+kKRZuhk9C5Ahly
gNXWM0IghMhYL1kZ47F/J0DESiH5u2bcfvc61Xxa9Pq4d4+Gnkssthe3r/t0SmJY7X+w
XBsf/aWr1863VxiDckHPeTHop1cP/zU+ePdWS+0ztU38vJI804A/XMQNXJtjJbcNLjUq
D8bQ==
X-Gm-Message-State: APf1xPAN1q1zfTOyhWupdGNTPLy+GSF1fquvv993atLHVsYcgftVZMmb
sw0kkeCBbJdqQL+dZ2XmBCZCvlyf
X-Google-Smtp-Source: AH8x225a0Eny9L3P/TnsWAhox7JWMqPVMzthoNcUEYmZNvm7j0c46JjZ9xa48dRb96kcnJKwXv0xVQ==
X-Received: by 10.28.155.66 with SMTP id d63mr1103620wme.7.1518524755578;
Tue, 13 Feb 2018 04:25:55 -0800 (PST)
Received: from [192.168.1.32] ([178.60.38.49])
by smtp.gmail.com with ESMTPSA id
k7sm12856103wrg.68.2018.02.13.04.25.54
for <bitcoin-dev@lists.linuxfoundation.org>
(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Tue, 13 Feb 2018 04:25:54 -0800 (PST)
From: =?utf-8?Q?JOSE_FEMENIAS_CA=C3=91UELO?= <jose.femenias@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Message-Id: <65F92B37-48C1-4CD5-8F17-47BF9BD231A9@gmail.com>
Date: Tue, 13 Feb 2018 13:25:53 +0100
To: bitcoin-dev@lists.linuxfoundation.org
X-Mailer: Apple Mail (2.3259)
X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM,
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
X-Mailman-Approved-At: Tue, 13 Feb 2018 14:06:40 +0000
Subject: [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 12:25:59 -0000
Hi,
Bitcoin is licensed under the MIT license =
(https://github.com/bitcoin/bitcoin/blob/master/COPYING =
<https://github.com/bitcoin/bitcoin/blob/master/COPYING>) which is one =
of the most permissive licenses widely in use.
While this almost restriction-less license has proved useful to many =
software projects, I think it could be wise to question its current =
suitability for this project, given the recent history.
The difficulty among the general population to distinguish between =
Bitcoin (the protocol and software) and bitcoin (the currency) arises =
spontaneously from the intimate entanglement of both.=20
The current list of Bitcoin lookalikes includes: Bitcoin Cash, Bitcoin =
Gold, Bitcoin Diamond, Bitcoin God, Bitcoin Clashic, Super Bitcoin, =
Bitcoin Hot, Bitcoin X, Oil Bitcoin, Bitcoin World, Lightning Bitcoin...
This recent flurry of hard forks is, IMHO, exacerbating the confusion =
about the very nature of the project, and harming it in many ways.
Although the liberal MIT license is (rightfully) beneficial to many =
other projects, companies and individuals, it is my belief that several =
projects are unfairly taking advantage of this generous license to =
attack Bitcoin (both the software and the currency), confuse the public, =
and gain personal profit in a way that is severely harming the Bitcoin =
ecosystem.
Therefore, I=E2=80=99d like to raise the possibility of amending the MIT =
license in a simple way, by adding a line such as:
***
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
***
(This is just an approximation. A final version would probably have to =
include a restriction to some soundalikes like BITKOIN, BIITCOIN,=E2=80=A6=
)
This way, I could legitimate use this software to create my own crypto =
coin, or use it in Ethereum, Litecoin or any of the other legitimate =
cryptos, but I could not make my =E2=80=9CBitcoin Whatever=E2=80=9D fork =
and keep using this software as the basis for it. I could also fork the =
bitcoin blockchain to create =E2=80=9CBcoin lightspeed=E2=80=9D but not =
=E2=80=9CBitcoin lightspeed=E2=80=9D for instance.
I know this would probably not prevent the explosion of forks in the =
future, but maybe it could help mitigate the confusion among the users =
and the harm to this community. Even if its enforceability is dubious, =
at least any infringing project would be exposed to some liability. I =
see myself some possible loopholes the way the license addendum is =
written. My intention is not to arrive immediately to a final wording =
but to know if there is some value to the idea of changing the license =
with this purpose.
Jose Femenias=
|
