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
|
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 7F0DEEA9
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 13 Feb 2018 15:22:44 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wr0-f173.google.com (mail-wr0-f173.google.com
[209.85.128.173])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 3EAB7D0
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 13 Feb 2018 15:22:43 +0000 (UTC)
Received: by mail-wr0-f173.google.com with SMTP id t94so18960203wrc.5
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 13 Feb 2018 07:22:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=subject:to:references:from:message-id:date:user-agent:mime-version
:in-reply-to:content-transfer-encoding:content-language;
bh=aSPzoyfbluEw5bQDznkjOLxJ6pQmis1kG0Sl4R0jJIE=;
b=XKELX8+95iFKpDz4CfmUtM0e6m1puF8QHslYD84l9iERX5P+IHhog7PyWJUqCiZa/G
Ao4bGlokGwWzz+QaME7SFVIEKIz1faoqUlloMRdAY0WSfCx89drTtiCb+tVevJsnYHIY
3wEei5DkEF+342tT4l0g2xkGLcWtY1r/pt969J4/RdJqwVJsGT+ic/4Fstx7BUA1+mW3
rfT0ENeeATnRJgYLneOmRZxSFaJXnHtuHfEendQVRf8Mbn7Ch2A4lPB65zZPDE8Zmpso
oxzfd/xPv3vLFmzfeTuvP9Y8v/uWJnCYDUMqjZrGmF+ArTWm6SUGT2sb8cznCeMblGKT
4aJw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:subject:to:references:from:message-id:date
:user-agent:mime-version:in-reply-to:content-transfer-encoding
:content-language;
bh=aSPzoyfbluEw5bQDznkjOLxJ6pQmis1kG0Sl4R0jJIE=;
b=A7mlZ4p6/IeFPV4KaVLPtYmHcyQh6zhXfEcxAKUWlKtGCnRJH+5COoMqz1TzOA8RPL
FcRDrjnMQjwCwrXyhg6CXlAMLsHYmdbHIkYJcM3uBbkKiZm16thIbkUNuAHgyhRFjyFr
5NDBlmPAo73hKw7aWRyCnrQJ3nW3PkEcEMozlRAEBDtqW5LtsLXLtiGuUPEP2RhK2ath
jNNsMbBh7mGRvGV2UUKc9qE87PXMazsGQjWFMI2nSiOZBD74hOQAcf96M62hS1AbKtvq
qRtjKGklAw/Q3YQgbXmSGyG/Te727d3aKMB86DBXoKibM8Kl/olnGPHc71jxuq7lCUV3
V5Qg==
X-Gm-Message-State: APf1xPDdoSBCxelFSQk8tLG/2WkNHP9x7jKQODR/6V/23sE61gjR4IwP
soKPsZHNJmXLWaldnPYh0H3FAA==
X-Google-Smtp-Source: AH8x2264qQ0fwSywtnc86dKqkQ6eb1xxJ643v2Mpt3kHYRx3jZv3pC/UW4WTPVR1cdL7KANFMofybA==
X-Received: by 10.223.188.144 with SMTP id g16mr1629225wrh.258.1518535361214;
Tue, 13 Feb 2018 07:22:41 -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
k34sm2410418wrk.95.2018.02.13.07.22.40
(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Tue, 13 Feb 2018 07:22:40 -0800 (PST)
To: =?UTF-8?Q?JOSE_FEMENIAS_CA=c3=91UELO?= <jose.femenias@gmail.com>,
Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
References: <65F92B37-48C1-4CD5-8F17-47BF9BD231A9@gmail.com>
From: Aymeric Vitte <vitteaymeric@gmail.com>
Message-ID: <cad15d4e-3e66-7e30-967c-7ecb20a54ca8@gmail.com>
Date: Tue, 13 Feb 2018 16:22:43 +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: <65F92B37-48C1-4CD5-8F17-47BF9BD231A9@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
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,
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
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:22:44 -0000
I was thinking to post something very similar on this list but not sure
that it would get some kind of interest
Not sure how and if it can be done (ie license modification) but the
reuse of the bitcoin core code can allow even a child to launch a fork
and this mess should stop, maybe people like to get "free" coins but
they are misleaded, they can lose everything and there are some more
vicious side effects like replay protection collisions between forks,
this is already happening, nobody seems to care but I wrote:
Bitcoin Tartuffe, the ultimate fork - User guide: How to create your
bitcoin fork in 5mn, fool everybody and become rich
https://www.linkedin.com/pulse/user-guide-how-create-your-bitcoin-fork-5mn-fool-everybody-vitte
--> this is a parody of course but very close to the reality, some info
are intentionally wrong
The madness of bitcoin forks: risk, reward and ruin
https://www.linkedin.com/pulse/madness-bitcoin-forks-risk-reward-ruin-aymeric-vitte/
I don't think that it really impacts bitcoin itself but this is
definitely too easy for people to fork the bitcoin core code and launch
some shxtty fork
Probably nobody here follow this, as an example (among plenty) see this
https://bitcointalk.org/index.php?topic=2515675.msg30173307#msg30173307
completely absurd mess
Le 13/02/2018 à 13:25, JOSE FEMENIAS CAÑUELO via bitcoin-dev a écrit :
> 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.
> 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’d 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,…)
>
> 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 “Bitcoin Whatever” fork and keep using this software as the basis for it. I could also fork the bitcoin blockchain to create “Bcoin lightspeed” but not “Bitcoin lightspeed” 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
> _______________________________________________
> 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
|
