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
|
Return-Path: <btcdrak@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 50FE610AF
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 1 Sep 2015 22:47:32 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wi0-f180.google.com (mail-wi0-f180.google.com
[209.85.212.180])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 8880CE0
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 1 Sep 2015 22:47:31 +0000 (UTC)
Received: by wibz8 with SMTP id z8so47135705wib.1
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 01 Sep 2015 15:47:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to
:cc:content-type;
bh=Vpf1V+cCFlTgIS/fAE7ligR0KYO5ScL9dCja7ZVCASc=;
b=RY53f8q8RFKpLeznm5T1fufNoaqveECKJG5NHaOY4jA8b/P047JZJXCUpG5FRr5Rmh
Wm9zKerrT7ZCCY95WnCpUaIcMlG/SXGi9QVCM5z7OZ70uiHuD7hobnGCouu0uBST/qx+
uUgjT74310nEugzzb/h35ZzKQQLoxEKwCOOTJDj8Gxe+Awek9rmdyHkwBnblTOm7XLMI
MnIT/tm8lG1ACtgBVwqA56ed8oAsRNXerodEQ/NdLmGVRXlAC7Y8fC+halBjwi8wgPgL
vMPPeLzJDwqfqG/w/vuwtVeFjreCbtgpk8Q+LeG9yp/uaCkVIQ69RutqE0VpZhUwSjlG
8VIA==
X-Received: by 10.194.191.164 with SMTP id gz4mr36074825wjc.21.1441147650250;
Tue, 01 Sep 2015 15:47:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.211.16 with HTTP; Tue, 1 Sep 2015 15:47:10 -0700 (PDT)
In-Reply-To: <CADr=VrTAUdfOOYzY8b7OGWphzcwTbJAE7M860ZajmGt1tVpzLA@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>
<CADr=VrTAUdfOOYzY8b7OGWphzcwTbJAE7M860ZajmGt1tVpzLA@mail.gmail.com>
From: Btc Drak <btcdrak@gmail.com>
Date: Tue, 1 Sep 2015 23:47:10 +0100
Message-ID: <CADJgMzsRCTyGgP2=vn-9VMnYt3HxZL4ocR5abyKAZ81vmnbC5w@mail.gmail.com>
To: Ahmed Zsales <ahmedzsales18@gmail.com>
Content-Type: text/plain; charset=UTF-8
X-Spam-Status: No, score=-1.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM, HK_RANDOM_ENVFROM,
HK_RANDOM_FROM, RCVD_IN_DNSWL_LOW autolearn=no 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:47:32 -0000
I have read the proposal. I think you missed my point: every existing
transaction author would be required to agree to your proposals for
them to be legal, and that's clearly impossible. You'd also need every
single miner who published a block. You're much better taking the line
that actually, the data is public domain and unrestricted based on
various assumptions.
You make some assumptions that transaction authors use Bitcoin Core to
"contract with the network", but in fact transactions are written and
broadcast by a number of means, arguably very few are created by
Bitcoin Core these days. How exactly do you expect to get a legally
binding agreement from all future transaction authors agreeing to your
terms? How would you prove Alice agreed 10 years later? If it was a
proprietary system like Paypal who can force you to agree or close
your account, the Bitcoin protocol is permissionless and anyone can
author a transaction using any means they like, not just Bitcoin Core.
So again I come back to the point your proposal would have to get
permission from all existing authors, and all future authors to work.
Overall I think the proposal is trying to fix something that doesn't
need fixing and get into a quagmire in the process. In fact, I see it
as an impossible task.
On Tue, Sep 1, 2015 at 11:11 PM, Ahmed Zsales <ahmedzsales18@gmail.com> wrote:
> 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
>> >
>
>
|
