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
|
Return-Path: <ahmedzsales18@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 48A3714A6
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 1 Sep 2015 22:11:58 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-vk0-f49.google.com (mail-vk0-f49.google.com
[209.85.213.49])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 79CF51B9
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 1 Sep 2015 22:11:57 +0000 (UTC)
Received: by vkbc123 with SMTP id c123so65297792vkb.3
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 01 Sep 2015 15:11:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type;
bh=iXtpMhJw4H9YjiMdzFCxH1f36PutaWIzSHTMdvlvPAc=;
b=lc8wNlgB37L5eLhWkZMDbtONQ++VOlgsSW/+Jy6V6zcb0MES4vigZQNDBlmKp0R5/D
UlaGn8Kf6yz+HjY0mVV9oeKBFIA5z9t79VCsrtkoFosJgRKoCqMX8sZbAHrErpF2fxYc
IJwdjPRmw1ftbUMsdfHS4KJvUrOKxhsLMD9F5hgLYKriArUKXLdF1LlCzEamtqq/q+fl
sus++0J9x2Obco6e0Fl48IDpmLeLlV4lThvBs9oomZuJi5AE8phwj4lziYQTws/g21Gx
jFX2MsUpWRTQLSE/jQe2vhtXWA38hO5Y7arEQx4OZNWocJIt7b1NSwsHYjNsw00aztES
VIfw==
MIME-Version: 1.0
X-Received: by 10.52.243.232 with SMTP id xb8mr31877453vdc.40.1441145516747;
Tue, 01 Sep 2015 15:11:56 -0700 (PDT)
Received: by 10.31.109.134 with HTTP; Tue, 1 Sep 2015 15:11:56 -0700 (PDT)
In-Reply-To: <CADJgMzvBCiHJo++zrZtA4XuMnNd8D8fHEiS4E2OfoKm4j8sY1w@mail.gmail.com>
References: <CADr=VrRT2tdN0jjkZ7HjjeyqonrHG=j+uh8m1L2nhew7c1gnng@mail.gmail.com>
<CADJgMztScEsDEy277Jksy2RckbpzeRw6RbQzyVrdkjJSS=hHPA@mail.gmail.com>
<CADr=VrQ42Gqv7fUFVpaburw0=08SNXb0TUCBWd3arREbpdfCkA@mail.gmail.com>
<CADJgMzvBCiHJo++zrZtA4XuMnNd8D8fHEiS4E2OfoKm4j8sY1w@mail.gmail.com>
Date: Tue, 1 Sep 2015 23:11:56 +0100
Message-ID: <CADr=VrTAUdfOOYzY8b7OGWphzcwTbJAE7M860ZajmGt1tVpzLA@mail.gmail.com>
From: Ahmed Zsales <ahmedzsales18@gmail.com>
To: Btc Drak <btcdrak@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c1d63e987272051eb6d60f
X-Spam-Status: No, score=-2.4 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,DKIM_VALID_AU,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,
HTML_MESSAGE,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Open Block Chain Licence, BIP[xxxx] Draft
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development 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, 01 Sep 2015 22:11:58 -0000
--001a11c1d63e987272051eb6d60f
Content-Type: text/plain; charset=UTF-8
To avoid repetition, we have actually covered the general points and
questions you have raised in the draft BIP, which includes a draft licence
to assist discussions:
https://drive.google.com/file/d/0BwEbhrQ4ELzBMVFxajNZa2hzMTg/view?usp=sharing
Regards,
Ahmed
On Tue, Sep 1, 2015 at 11:02 PM, Btc Drak <btcdrak@gmail.com> wrote:
> I think it gets worse. Who are the copyright owners (if this actually
> applies). You've got people publishing transaction messages, you've
> got miners reproducing them and publishing blocks. Who are all the
> parties involved? Then to take pedantry to the next level, does a
> miner have permission to republish messages? How do you know? What if
> the messages are reproducing others copyright/licensed material? It's
> not possible to license someone else's work. There are plenty rabbit
> holes to go down with this train of thought.
>
> On Tue, Sep 1, 2015 at 8:36 PM, Ahmed Zsales via bitcoin-dev
> <bitcoin-dev@lists.linuxfoundation.org> wrote:
> > That is a very good point.
> >
> > We considered whether data existing before a licence change would be
> > covered, but we hadn't factored the potential need for gaining
> permissions
> > for a change to be considered effective.
> >
> > We have proposed that miners be the main beneficiaries of licensing and
> > there is a consideration on whether they should vote to adopt the new
> terms.
> > While not the preferred route, that would overcome any issues to what is
> an
> > otherwise honest 'error and omission.' There doesn't seem to be anyone
> who
> > could claim to have suffered any economic losses so this may not be an
> > issue. It merits further investigation.
> >
> > The block chain is in perpetual change, so the sooner a change is agreed
> > upon, if at all, the more data it will cover without any reservations. At
> > any rate, we believe the changes would be considered effective on a
> > retrospective basis.
> >
> >
> > On Tue, Sep 1, 2015 at 7:12 PM, Btc Drak <btcdrak@gmail.com> wrote:
> >>
> >> Without commenting on your proposal at all, the general problem with
> >> licensing after the fact is you require the permission of every
> >> copyright holder in order to make the change.
> >>
> >>
> >>
> >> On Tue, Sep 1, 2015 at 2:30 PM, Ahmed Zsales via bitcoin-dev
> >> <bitcoin-dev@lists.linuxfoundation.org> wrote:
> >> > Hello,
> >> >
> >> > We believe the network requires a block chain licence to supplement
> the
> >> > existing MIT Licence which we believe only covers the core reference
> >> > client
> >> > software.
> >> >
> >> > Replacing or amending the existing MIT Licence is beyond the scope of
> >> > this
> >> > draft BIP.
> >> >
> >> > Rationale and details of our draft BIP for discussion and evaluation
> are
> >> > here:
> >> >
> >> >
> >> >
> https://drive.google.com/file/d/0BwEbhrQ4ELzBMVFxajNZa2hzMTg/view?usp=sharing
> >> >
> >> > Regards,
> >> >
> >> > Ahmed
> >> >
> >> > _______________________________________________
> >> > bitcoin-dev mailing list
> >> > bitcoin-dev@lists.linuxfoundation.org
> >> > 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
> >
>
--001a11c1d63e987272051eb6d60f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div style=3D"font-size:12.8000001907349px"><span style=3D=
"font-size:12.8000001907349px">To avoid repetition, we have actually covere=
d the general points and questions you have raised in the draft BIP, which =
includes a draft licence to assist discussions:</span><br></div><div style=
=3D"font-size:12.8000001907349px"><br></div><div style=3D"font-size:12.8000=
001907349px"><a href=3D"https://drive.google.com/file/d/0BwEbhrQ4ELzBMVFxaj=
NZa2hzMTg/view?usp=3Dsharing" target=3D"_blank">https://drive.google.com/fi=
le/d/0BwEbhrQ4ELzBMVFxajNZa2hzMTg/view?usp=3Dsharing</a><br></div><div styl=
e=3D"font-size:12.8000001907349px"><br></div><div style=3D"font-size:12.800=
0001907349px">Regards,</div><div style=3D"font-size:12.8000001907349px"><br=
></div><div style=3D"font-size:12.8000001907349px">Ahmed</div></div><div cl=
ass=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue, Sep 1, 2015 at 1=
1:02 PM, Btc Drak <span dir=3D"ltr"><<a href=3D"mailto:btcdrak@gmail.com=
" target=3D"_blank">btcdrak@gmail.com</a>></span> wrote:<br><blockquote =
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid=
;padding-left:1ex">I think it gets worse. Who are the copyright owners (if =
this actually<br>
applies). You've got people publishing transaction messages, you've=
<br>
got miners reproducing them and publishing blocks. Who are all the<br>
parties involved? Then to take pedantry to the next level, does a<br>
miner have permission to republish messages? How do you know? What if<br>
the messages are reproducing others copyright/licensed material? It's<b=
r>
not possible to license someone else's work. There are plenty rabbit<br=
>
holes to go down with this train of thought.<br>
<br>
On Tue, Sep 1, 2015 at 8:36 PM, Ahmed Zsales via bitcoin-dev<br>
<div class=3D"HOEnZb"><div class=3D"h5"><<a href=3D"mailto:bitcoin-dev@l=
ists.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org</a>> wro=
te:<br>
> That is a very good point.<br>
><br>
> We considered whether data existing before a licence change would be<b=
r>
> covered, but we hadn't factored the potential need for gaining per=
missions<br>
> for a change to be considered effective.<br>
><br>
> We have proposed that miners be the main beneficiaries of licensing an=
d<br>
> there is a consideration on whether they should vote to adopt the new =
terms.<br>
> While not the preferred route, that would overcome any issues to what =
is an<br>
> otherwise honest 'error and omission.' There doesn't seem =
to be anyone who<br>
> could claim to have suffered any economic losses so this may not be an=
<br>
> issue. It merits further investigation.<br>
><br>
> The block chain is in perpetual change, so the sooner a change is agre=
ed<br>
> upon, if at all, the more data it will cover without any reservations.=
At<br>
> any rate, we believe the changes would be considered effective on a<br=
>
> retrospective basis.<br>
><br>
><br>
> On Tue, Sep 1, 2015 at 7:12 PM, Btc Drak <<a href=3D"mailto:btcdrak=
@gmail.com">btcdrak@gmail.com</a>> wrote:<br>
>><br>
>> Without commenting on your proposal at all, the general problem wi=
th<br>
>> licensing after the fact is you require the permission of every<br=
>
>> copyright holder in order to make the change.<br>
>><br>
>><br>
>><br>
>> On Tue, Sep 1, 2015 at 2:30 PM, Ahmed Zsales via bitcoin-dev<br>
>> <<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitco=
in-dev@lists.linuxfoundation.org</a>> wrote:<br>
>> > Hello,<br>
>> ><br>
>> > We believe the network requires a block chain licence to supp=
lement the<br>
>> > existing MIT Licence which we believe only covers the core re=
ference<br>
>> > client<br>
>> > software.<br>
>> ><br>
>> > Replacing or amending the existing MIT Licence is beyond the =
scope of<br>
>> > this<br>
>> > draft BIP.<br>
>> ><br>
>> > Rationale and details of our draft BIP for discussion and eva=
luation are<br>
>> > here:<br>
>> ><br>
>> ><br>
>> > <a href=3D"https://drive.google.com/file/d/0BwEbhrQ4ELzBMVFxa=
jNZa2hzMTg/view?usp=3Dsharing" rel=3D"noreferrer" target=3D"_blank">https:/=
/drive.google.com/file/d/0BwEbhrQ4ELzBMVFxajNZa2hzMTg/view?usp=3Dsharing</a=
><br>
>> ><br>
>> > Regards,<br>
>> ><br>
>> > Ahmed<br>
>> ><br>
>> > _______________________________________________<br>
>> > bitcoin-dev mailing list<br>
>> > <a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitc=
oin-dev@lists.linuxfoundation.org</a><br>
>> > <a href=3D"https://lists.linuxfoundation.org/mailman/listinfo=
/bitcoin-dev" rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfound=
ation.org/mailman/listinfo/bitcoin-dev</a><br>
>> ><br>
><br>
><br>
><br>
> _______________________________________________<br>
> bitcoin-dev mailing list<br>
> <a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@l=
ists.linuxfoundation.org</a><br>
> <a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-=
dev" rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org=
/mailman/listinfo/bitcoin-dev</a><br>
><br>
</div></div></blockquote></div><br></div>
--001a11c1d63e987272051eb6d60f--
|
