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
|
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 CC7561321
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 1 Sep 2015 22:02:37 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-vk0-f42.google.com (mail-vk0-f42.google.com
[209.85.213.42])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 352B11B0
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 1 Sep 2015 22:02:37 +0000 (UTC)
Received: by vkbf67 with SMTP id f67so60018579vkb.0
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 01 Sep 2015 15:02:36 -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=evOFLPilh0wo8X12N1HIXjNhyFm4DV746ZN21U6G9kI=;
b=L4G5vStBnFqiSJZatjCTsZeZnPrOJtPWKbHAnPZaY3xyjMLiKkOoCr9ZQoVByEvF+2
vz9uKPTXSMTfTK6tJC3eApzhzvpd5oHkQkg5Dchq07wbM9jCTjYR+XPvjCNWGLRuHXFK
1SfiZW2t9Xk6+TCIF56q3eT58L4xHUvq6RlHFcH9Aja18CfaXbWsDuJ0GDE92BhLkC7v
uSTJ+InvlGZuCHeSPQahlPn2AS5MoSvB9PYGZJKOOHvwjkgk/vfTzFy8HsaQhWFU2qxB
Bdxi7tXunErkhDA/CjrsBjUl26A3RGHN/Y4W9vxSbIyS4Ciniadi9uB5mS44M4EhD5hX
VXGw==
MIME-Version: 1.0
X-Received: by 10.52.243.232 with SMTP id xb8mr31829995vdc.40.1441144956292;
Tue, 01 Sep 2015 15:02:36 -0700 (PDT)
Received: by 10.31.109.134 with HTTP; Tue, 1 Sep 2015 15:02:36 -0700 (PDT)
In-Reply-To: <55E61A64.2030609@bitcoins.info>
References: <CADr=VrRT2tdN0jjkZ7HjjeyqonrHG=j+uh8m1L2nhew7c1gnng@mail.gmail.com>
<CADJgMztScEsDEy277Jksy2RckbpzeRw6RbQzyVrdkjJSS=hHPA@mail.gmail.com>
<CADr=VrQ42Gqv7fUFVpaburw0=08SNXb0TUCBWd3arREbpdfCkA@mail.gmail.com>
<55E61A64.2030609@bitcoins.info>
Date: Tue, 1 Sep 2015 23:02:36 +0100
Message-ID: <CADr=VrQeQ2=Htcen-oJrJWWhf5aQ8-cjYK28ic1UWNFWMf2nDQ@mail.gmail.com>
From: Ahmed Zsales <ahmedzsales18@gmail.com>
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=001a11c1d63e309488051eb6b5e3
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 22:02:37 -0000
--001a11c1d63e309488051eb6b5e3
Content-Type: text/plain; charset=UTF-8
Russ,
The general points and questions you have raised are covered in the draft
BIP:
https://drive.google.com/file/d/0BwEbhrQ4ELzBMVFxajNZa2hzMTg/view?usp=sharing
Regards,
Ahmed
On Tue, Sep 1, 2015 at 10:36 PM, Milly Bitcoin via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> 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.
>>
>
> Like I said, you need to talk to a lawyer. What exactly would be the
> purpose of any license? How can someone be a "beneficiary" to a license
> when you can't even explain who holds the license to begin with? How do
> they "benefit?" I don't see any purpose to putting a license on the Core
> software or the blockchain because nobody can explain who actually holds
> the license and there is no mechanism to enforce any license and there is
> no revenue to be shared. The whole discussion makes no sense.
>
> Russ
>
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
--001a11c1d63e309488051eb6b5e3
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>Russ,</div><div><br></div>The general points and ques=
tions you have raised are covered in the draft BIP:<div><br></div><div><a h=
ref=3D"https://drive.google.com/file/d/0BwEbhrQ4ELzBMVFxajNZa2hzMTg/view?us=
p=3Dsharing">https://drive.google.com/file/d/0BwEbhrQ4ELzBMVFxajNZa2hzMTg/v=
iew?usp=3Dsharing</a><br></div><div><br></div><div>Regards,</div><div><br><=
/div><div>Ahmed</div><div><div class=3D"gmail_extra"><br><div class=3D"gmai=
l_quote">On Tue, Sep 1, 2015 at 10:36 PM, Milly Bitcoin via bitcoin-dev <sp=
an dir=3D"ltr"><<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org"=
target=3D"_blank">bitcoin-dev@lists.linuxfoundation.org</a>></span> wro=
te:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;=
border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:=
solid;padding-left:1ex"><span class=3D""><blockquote class=3D"gmail_quote" =
style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:r=
gb(204,204,204);border-left-style:solid;padding-left:1ex">
We considered whether data existing before a licence change would be<br>
covered, but we hadn't factored the potential need for gaining<br>
permissions for a change to be considered effective.<br>
<br>
We have proposed that miners be the main beneficiaries of licensing and<br>
there is a consideration on whether they should vote to adopt the new<br>
terms. While not the preferred route, that would overcome any issues to<br>
what is an otherwise honest 'error and omission.' There doesn't=
seem to<br>
be anyone who could claim to have suffered any economic losses so this<br>
may not be an issue. It merits further investigation.<br>
</blockquote>
<br></span>
Like I said, you need to talk to a lawyer.=C2=A0 What exactly would be the =
purpose of any license?=C2=A0 How can someone be a "beneficiary" =
to a license when you can't even explain who holds the license to begin=
with?=C2=A0 How do they "benefit?"=C2=A0 I don't see any pur=
pose to putting a license on the Core software or the blockchain because no=
body can explain who actually holds the license and there is no mechanism t=
o enforce any license and there is no revenue to be shared.=C2=A0 The whole=
discussion makes no sense.<br>
<br>
Russ<div class=3D""><div class=3D"h5"><br>
<br>
<br>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">=
bitcoin-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.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</div></div></blockquote></div><br></div></div></div>
--001a11c1d63e309488051eb6b5e3--
|
