summaryrefslogtreecommitdiff
path: root/63/5545e6b9ab267e0f973a242999de1f0f3cb4c2
blob: 1e5a1544ebac1972809c74f3f2a0a1755a052d7e (plain)
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
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 78DEF10ED
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue,  1 Sep 2015 19:37:01 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-vk0-f46.google.com (mail-vk0-f46.google.com
	[209.85.213.46])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id E144714E
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue,  1 Sep 2015 19:37:00 +0000 (UTC)
Received: by vkbf67 with SMTP id f67so57905775vkb.0
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue, 01 Sep 2015 12:37:00 -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
	:content-type; bh=iDvpOdgfHfeuJq+h3bqbW9R8W3kU1O8ppfExx+l0Nl0=;
	b=duZQ5QWHtskWCKfe0bDgugjP5ELARDjLsoRpUYieQXgBMWeCEB8+7nzYnkPw3UIjGN
	J+vflHqeUwTJX3DFOTg/07wAp5b3NnUSs5UawNV9KWtXhhG/2LiBCnHykeqsqgg7UUk9
	OngIsapqZcU1PKytSBqTKYp10VFsl/PSxApipr6IawiDWHHawLZC47d1D8vCgzVfqWUI
	8f56VNVyF16VpZpDrhjEBOnntxNnxVVCI92sUTIeaASt/RtZygkZACrlL2z1cy7xFVKz
	VcVow+ad7cuMrC2/NPGyZxxUW1xlhssRo9FuucQTv0t6kqT6cgbl0LR7SSTwFTbRakz5
	S2rg==
MIME-Version: 1.0
X-Received: by 10.52.76.232 with SMTP id n8mr21935504vdw.20.1441136219836;
	Tue, 01 Sep 2015 12:36:59 -0700 (PDT)
Received: by 10.31.109.134 with HTTP; Tue, 1 Sep 2015 12:36:59 -0700 (PDT)
In-Reply-To: <CADJgMztScEsDEy277Jksy2RckbpzeRw6RbQzyVrdkjJSS=hHPA@mail.gmail.com>
References: <CADr=VrRT2tdN0jjkZ7HjjeyqonrHG=j+uh8m1L2nhew7c1gnng@mail.gmail.com>
	<CADJgMztScEsDEy277Jksy2RckbpzeRw6RbQzyVrdkjJSS=hHPA@mail.gmail.com>
Date: Tue, 1 Sep 2015 20:36:59 +0100
Message-ID: <CADr=VrQ42Gqv7fUFVpaburw0=08SNXb0TUCBWd3arREbpdfCkA@mail.gmail.com>
From: Ahmed Zsales <ahmedzsales18@gmail.com>
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=bcaec501c59474db01051eb4ac5c
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
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 19:37:01 -0000

--bcaec501c59474db01051eb4ac5c
Content-Type: text/plain; charset=UTF-8

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
> >
>

--bcaec501c59474db01051eb4ac5c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>That is a very good point.=C2=A0<br></div><div><br></=
div><div>We considered whether data existing before a licence change would =
be covered, but we hadn&#39;t factored the potential need for gaining permi=
ssions for a change to be considered effective.</div><div><br></div><div>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. Whi=
le not the preferred route, that would overcome any issues to what is an ot=
herwise honest &#39;error and omission.&#39; There doesn&#39;t seem to be a=
nyone who could claim to have suffered any economic losses so this may not =
be an issue. It merits further investigation.</div><div><br></div><div>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 rat=
e, we believe the changes would be considered effective on a retrospective =
basis.</div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra"=
><br><div class=3D"gmail_quote">On Tue, Sep 1, 2015 at 7:12 PM, Btc Drak <s=
pan dir=3D"ltr">&lt;<a href=3D"mailto:btcdrak@gmail.com" target=3D"_blank">=
btcdrak@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote=
" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">W=
ithout commenting on your proposal at all, the general problem with<br>
licensing after the fact is you require the permission of every<br>
copyright holder in order to make the change.<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
<br>
On Tue, Sep 1, 2015 at 2:30 PM, Ahmed Zsales via bitcoin-dev<br>
&lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@li=
sts.linuxfoundation.org</a>&gt; wrote:<br>
&gt; Hello,<br>
&gt;<br>
&gt; We believe the network requires a block chain licence to supplement th=
e<br>
&gt; existing MIT Licence which we believe only covers the core reference c=
lient<br>
&gt; software.<br>
&gt;<br>
&gt; Replacing or amending the existing MIT Licence is beyond the scope of =
this<br>
&gt; draft BIP.<br>
&gt;<br>
&gt; Rationale and details of our draft BIP for discussion and evaluation a=
re<br>
&gt; here:<br>
&gt;<br>
&gt; <a href=3D"https://drive.google.com/file/d/0BwEbhrQ4ELzBMVFxajNZa2hzMT=
g/view?usp=3Dsharing" rel=3D"noreferrer" target=3D"_blank">https://drive.go=
ogle.com/file/d/0BwEbhrQ4ELzBMVFxajNZa2hzMTg/view?usp=3Dsharing</a><br>
&gt;<br>
&gt; Regards,<br>
&gt;<br>
&gt; Ahmed<br>
&gt;<br>
</div></div><div class=3D"HOEnZb"><div class=3D"h5">&gt; __________________=
_____________________________<br>
&gt; bitcoin-dev mailing list<br>
&gt; <a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@l=
ists.linuxfoundation.org</a><br>
&gt; <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>
&gt;<br>
</div></div></blockquote></div><br></div></div>

--bcaec501c59474db01051eb4ac5c--