summaryrefslogtreecommitdiff
path: root/06/cc7b6c288193cd0d98b71b9d96d4db4bda6c52
blob: 88dc48bdc22f3715d72acba5b83d5e8474459464 (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
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 9A6E714B0
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue,  1 Sep 2015 15:11:40 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-vk0-f43.google.com (mail-vk0-f43.google.com
	[209.85.213.43])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id E330C126
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue,  1 Sep 2015 15:11:31 +0000 (UTC)
Received: by vkhf67 with SMTP id f67so58752682vkh.1
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue, 01 Sep 2015 08:11:31 -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=QfVpNDqsy1lfZ75yMYWAnBYl5+FTalGIC0KaLcY0h+c=;
	b=rDdfI/hYOfUlKRINUtR/hftKFv6YsSwWr/NEdbPbWCq+z20jsKw5a64BY0nJ8k++K2
	zpVpWlBypzrrRLM+FfrpiMQapOF0nn5KZz1BYfMvnAjn+xfQ2ULFbewtJvLOoqmMFoGl
	Bth1YIqEiwMRUeSlunM5gFcYebG/mKqJYOFKVPNgHZxp+6N8yKJawWsm4cXKOjHSWkJq
	MurMc2ooDp60tvybYd4+1pELI4bMWF32Qda7KpYEKKbe09kRjW0nsJmwEmhkvySK5kp0
	i2oAnjbU5OWOhHZbWXGez/7P2GjttsmEGpAmT/UCld5Kwin85MXJ3fklxU85hjn4JcMb
	AhnQ==
MIME-Version: 1.0
X-Received: by 10.52.243.232 with SMTP id xb8mr29344812vdc.40.1441120288051;
	Tue, 01 Sep 2015 08:11:28 -0700 (PDT)
Received: by 10.31.109.134 with HTTP; Tue, 1 Sep 2015 08:11:27 -0700 (PDT)
In-Reply-To: <CABaSBawtAn5YCSngPcawVkUcGKNvMJvCTbwrQzZFywdv=zptMQ@mail.gmail.com>
References: <CADr=VrRT2tdN0jjkZ7HjjeyqonrHG=j+uh8m1L2nhew7c1gnng@mail.gmail.com>
	<CABaSBawtAn5YCSngPcawVkUcGKNvMJvCTbwrQzZFywdv=zptMQ@mail.gmail.com>
Date: Tue, 1 Sep 2015 16:11:27 +0100
Message-ID: <CADr=VrTQMqqKJJdZJ2tdCixM+nx-W_F+AHqrqrDrmqD+_sLaYA@mail.gmail.com>
From: Ahmed Zsales <ahmedzsales18@gmail.com>
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=001a11c1d63ed919dc051eb0f64e
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 15:11:40 -0000

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

Thank you. We hadn't seen that before.  It is an interesting discussion.

We did think about including some references to protections for private
keys while they remained in your control and you could prove as much. In
theory it should be no different to dropping money on the floor. The money
still belongs to you, even if someone else comes along and finds it. The
onus of proof is on you as the owner to demonstrate private keys are yours,
but you also need the goodwill of the person finding the money.

However, this raised a number of issues including whether finding private
keys attached to coins and moving the funds constituted theft, in which
case there are already criminal protections if you are able to track the
coins to an individual. We decided not to include anything specific in the
draft licence to keep it simple, relying instead on the generic definitions
of rights to *private transaction data* of which private keys would come
under.

Regards,

Ahmed



On Tue, Sep 1, 2015 at 2:50 PM, Bryan Bishop <kanzure@gmail.com> wrote:

> On Tue, Sep 1, 2015 at 8:30 AM, Ahmed Zsales via bitcoin-dev <
> bitcoin-dev@lists.linuxfoundation.org> wrote:
>
>> We believe the network requires a block chain licence
>
>
> Here is a previous discussion of this topic (2012):
> https://bitcointalk.org/index.php?topic=117663.0
>
> - Bryan
> http://heybryan.org/
> 1 512 203 0507
>

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

<div dir=3D"ltr">Thank you. We hadn&#39;t seen that before.=C2=A0 It is an =
interesting discussion.<div><br></div><div>We did think about including som=
e references to protections for private keys while they remained in your co=
ntrol and you could prove as much. In theory it should be no different to d=
ropping money on the floor. The money still belongs to you, even if someone=
 else comes along and finds it. The onus of proof is on you as the owner to=
 demonstrate private keys are yours, but you also need the goodwill of the =
person finding the money.</div><div><br></div><div>However, this raised a n=
umber of issues including whether finding private keys attached to coins an=
d moving the funds constituted theft, in which case there are already crimi=
nal protections if you are able to track the coins to an individual. We dec=
ided not to include anything specific in the draft licence to keep it simpl=
e, relying instead on the generic definitions of rights to <i>private trans=
action data</i> of which private keys would come under.</div><div><br></div=
><div>Regards,</div><div><br></div><div>Ahmed</div><div><br></div><div><br>=
</div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tu=
e, Sep 1, 2015 at 2:50 PM, Bryan Bishop <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:kanzure@gmail.com" target=3D"_blank">kanzure@gmail.com</a>&gt;</span> =
wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bord=
er-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gma=
il_extra"><span class=3D""><div class=3D"gmail_quote">On Tue, Sep 1, 2015 a=
t 8:30 AM, Ahmed Zsales via bitcoin-dev <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">bitcoin-dev@l=
ists.linuxfoundation.org</a>&gt;</span> wrote:<br><blockquote class=3D"gmai=
l_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-lef=
t-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">We belie=
ve the network requires a block chain licence</blockquote></div><br></span>=
Here is a previous discussion of this topic (2012):<br><a href=3D"https://b=
itcointalk.org/index.php?topic=3D117663.0" target=3D"_blank">https://bitcoi=
ntalk.org/index.php?topic=3D117663.0</a><br><div><br></div><div>- Bryan<br>=
<a href=3D"http://heybryan.org/" target=3D"_blank">http://heybryan.org/</a>=
<br><a href=3D"tel:1%20512%20203%200507" value=3D"+15122030507" target=3D"_=
blank">1 512 203 0507</a></div>
</div></div>
</blockquote></div><br></div>

--001a11c1d63ed919dc051eb0f64e--