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
|
Return-Path: <natanael.l@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 2591AF0B
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 13 Feb 2018 14:25:13 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wm0-f66.google.com (mail-wm0-f66.google.com [74.125.82.66])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 653F335F
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 13 Feb 2018 14:25:12 +0000 (UTC)
Received: by mail-wm0-f66.google.com with SMTP id j199so4251862wmj.2
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 13 Feb 2018 06:25:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to;
bh=ds81rrgQJTjifrSIohqhKPDV96E/PswQrp0mpGGhFic=;
b=f8m/N8he1FhaGLAxOijYoBqAFwBhWEebbRiLiaQdR0RnERTeGodwZRPgvnUvLt5+cO
J+C1ys8CuMvOtNR1SI3H2vmsjLGuu2MU0AaOM1Nkg02DnEg+OO9wmbBiOfMEMvX7X6cL
uJ49axYL8smndiRX4E3fY/AZbLxYabWy4hjBt3jBu0xcKYcutJFF7hWOjjtHJATx7t+6
DAeC+zgp1Fqp9KIABGJ13ktHfQMYcLCV2Uqe145CZmHIN50EzNV+C8M4rtkc1+3oN9SS
SJYdGcsxYlo7Z1zcRF66eCNgpTn81QyKSW8QgwmBnPy/q7ZF1EZMbrcBcuVQHyW1sXqv
Dyow==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to;
bh=ds81rrgQJTjifrSIohqhKPDV96E/PswQrp0mpGGhFic=;
b=mB6vG0e/Zv7HLthyMmyjq98DRH+zLOKvYh8zr0hDmwRqUStFp4Z9ZNRJ44rsZjvj3m
wzaXv3k/h1bzpB1hm01uCMgonCVuXWA9VTNf7xc23IZLbAO+WaDXFUvnecZlRsLFsZcd
yjgZOU+VqxAyqUD4DejLIhE5uuiBoYSNx9mHtJ+RyssqnZwqgfLcIDLVv/ofoPaFhVBO
OfHDm6q28tN5Zo4oZ0+9HVJ/DlvOzVx6Ojb7bZ/6P5D1rf5/V9dNv/g7S3hDwKkOAbi1
B//Tj/Z8BOnFDCW/3PAk0CPqjjmp8JanCu8W/fnm9dBl6/qaAcloR3UCldhoiAcpsjm3
Pp5w==
X-Gm-Message-State: APf1xPBoZgbX0i9n2ONeFy+q8TNRger+EiOFI9sveSd05AADIZSCNfJe
UOs2EGsX/GV9mRaCoHsLwhtmoItHEQHdA0PG+Wg=
X-Google-Smtp-Source: AH8x224bKnMK1E8c9/UNwJ3mLAYaFbPFREDq2oWnSZLavIrMpkBDBLXTgN6/LIs/ESmmo6h1PxUTQ/tLFrseWP109UI=
X-Received: by 10.80.224.72 with SMTP id g8mr1657174edl.218.1518531910956;
Tue, 13 Feb 2018 06:25:10 -0800 (PST)
MIME-Version: 1.0
Received: by 10.80.169.103 with HTTP; Tue, 13 Feb 2018 06:25:10 -0800 (PST)
Received: by 10.80.169.103 with HTTP; Tue, 13 Feb 2018 06:25:10 -0800 (PST)
In-Reply-To: <65F92B37-48C1-4CD5-8F17-47BF9BD231A9@gmail.com>
References: <65F92B37-48C1-4CD5-8F17-47BF9BD231A9@gmail.com>
From: Natanael <natanael.l@gmail.com>
Date: Tue, 13 Feb 2018 15:25:10 +0100
Message-ID: <CAAt2M1-fEnQxjX40c-sjUYpfLpJtS-fy5t244vUOZSb8Pm=MrQ@mail.gmail.com>
To: =?UTF-8?Q?JOSE_FEMENIAS_CA=C3=91UELO?= <jose.femenias@gmail.com>,
Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="089e0822162421fc4e056518c34e"
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
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 14:25:13 -0000
--089e0822162421fc4e056518c34e
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
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 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.
--089e0822162421fc4e056518c34e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"auto"><div><br><div class=3D"gmail_extra"><br><div class=3D"gma=
il_quote">Den 13 feb. 2018 15:07 skrev "JOSE FEMENIAS CA=C3=91UELO via=
bitcoin-dev" <<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.=
org">bitcoin-dev@lists.linuxfoundation.org</a>>:<blockquote class=3D"quo=
te" style=3D"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 (COR=
E) BLOCKCHAIN<br>
***<br></blockquote></div></div></div><div dir=3D"auto"><br></div><div dir=
=3D"auto">That's better solved with trademarks. (whoever would be the t=
rademark holder - Satoshi?)=C2=A0=C2=A0</div><div dir=3D"auto"><br></div><d=
iv dir=3D"auto">This would also prohibit any reimplementation that's no=
t 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 uncert=
ainty.=C2=A0</div><div dir=3D"auto"><br></div><div dir=3D"auto">Another maj=
or problem is that it neither affects anybody forking older versions of Bit=
coin, not people using existing independent blockchain implementations and =
renaming them Bitcoin-Whatsoever.=C2=A0</div><div dir=3D"auto"><br></div><d=
iv dir=3D"auto">And what happens when an old version is technically incompa=
tible with a future version by the Core team due to not understanding vario=
us 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 mentio=
n Bitcoin is overkill.=C2=A0</div><div dir=3D"auto"><br></div><div dir=3D"a=
uto">The software license also don't affect the blockchain data.=C2=A0<=
/div><div dir=3D"auto"><br></div><div dir=3D"auto"><div class=3D"gmail_extr=
a"><div class=3D"gmail_quote"><blockquote class=3D"quote" style=3D"margin:0=
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"></blockquote></div><=
/div></div></div>
--089e0822162421fc4e056518c34e--
|
