From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id EEBC910D4 for ; Tue, 13 Feb 2018 17:53:58 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from zinan.dashjr.org (zinan.dashjr.org [192.3.11.21]) by smtp1.linuxfoundation.org (Postfix) with ESMTP id C648D18A for ; Tue, 13 Feb 2018 17:53:57 +0000 (UTC) Received: from ishibashi.localnet (unknown [IPv6:2001:470:5:265::71]) (Authenticated sender: luke-jr) by zinan.dashjr.org (Postfix) with ESMTPSA id 452D238A12C3; Tue, 13 Feb 2018 17:53:43 +0000 (UTC) X-Hashcash: 1:25:180213:bitcoin-dev@lists.linuxfoundation.org::5I+N7Zb22xzTe/Al:CJMQ X-Hashcash: 1:25:180213:jose.femenias@gmail.com::AyCPmw9CYj7EQQzY:3oCE From: Luke Dashjr To: bitcoin-dev@lists.linuxfoundation.org, JOSE FEMENIAS =?utf-8?q?CA=C3=91UELO?= Date: Tue, 13 Feb 2018 17:53:40 +0000 User-Agent: KMail/1.13.7 (Linux/4.15.1-gentoo; KDE/4.14.37; x86_64; ; ) References: <65F92B37-48C1-4CD5-8F17-47BF9BD231A9@gmail.com> In-Reply-To: <65F92B37-48C1-4CD5-8F17-47BF9BD231A9@gmail.com> X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F X-PGP-Key-ID: BD02942421F4889F X-PGP-Keyserver: hkp://pgp.mit.edu MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <201802131753.41846.luke@dashjr.org> X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED, T_RP_MATCHES_RCVD 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Feb 2018 17:53:59 -0000 This would give too much power to Bitcoin Core, and implies falsely that=20 Bitcoin and Bitcoin Core are the same thing. On Tuesday 13 February 2018 12:25:53 PM JOSE FEMENIAS CA=C3=91UELO via bitc= oin-dev=20 wrote: > Hi, >=20 > Bitcoin is licensed under the MIT license > (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. >=20 > 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... >=20 > This recent flurry of hard forks is, IMHO, exacerbating the confusion abo= ut > the very nature of the project, and harming it in many ways. >=20 > 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. >=20 > 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: >=20 >=20 > *** > NO PART OF THIS SOFTWARE CAN BE INCLUDED IN ANY OTHER PROJECT THAT USES T= HE > 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 *** >=20 > (This is just an approximation. A final version would probably have to > include a restriction to some soundalikes like BITKOIN, BIITCOIN,=E2=80= =A6) >=20 > 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=9C= Bitcoin lightspeed=E2=80=9D for > instance. >=20 > 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. >=20 >=20 > Jose Femenias > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev