From: Ahmed Zsales <ahmedzsales18@gmail•com>
To: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Open Block Chain Licence, BIP[xxxx] Draft
Date: Tue, 1 Sep 2015 16:11:27 +0100 [thread overview]
Message-ID: <CADr=VrTQMqqKJJdZJ2tdCixM+nx-W_F+AHqrqrDrmqD+_sLaYA@mail.gmail.com> (raw)
In-Reply-To: <CABaSBawtAn5YCSngPcawVkUcGKNvMJvCTbwrQzZFywdv=zptMQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1386 bytes --]
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
>
[-- Attachment #2: Type: text/html, Size: 2422 bytes --]
next prev parent reply other threads:[~2015-09-01 15:11 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 13:30 Ahmed Zsales
2015-09-01 13:43 ` Milly Bitcoin
2015-09-01 13:50 ` Bryan Bishop
2015-09-01 15:11 ` Ahmed Zsales [this message]
2015-09-01 16:05 ` Natanael
2015-09-01 17:39 ` Luke Dashjr
2015-09-01 18:12 ` Btc Drak
2015-09-01 19:36 ` Ahmed Zsales
2015-09-01 21:36 ` Milly Bitcoin
2015-09-01 22:02 ` Ahmed Zsales
2015-09-01 22:42 ` Milly Bitcoin
2015-09-01 23:21 ` Ahmed Zsales
2015-09-01 23:40 ` Milly Bitcoin
2015-09-01 22:02 ` Btc Drak
2015-09-01 22:11 ` Ahmed Zsales
2015-09-01 22:47 ` Btc Drak
2015-09-01 22:20 ` Natanael
2015-09-01 22:28 ` Ahmed Zsales
2015-09-01 21:51 ` Wladimir J. van der Laan
2015-09-01 23:39 ` hurricanewarn1
2015-09-02 8:56 ` Warren Togami Jr.
2015-09-02 20:28 ` Ahmed Zsales
2015-09-02 20:58 ` Milly Bitcoin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADr=VrTQMqqKJJdZJ2tdCixM+nx-W_F+AHqrqrDrmqD+_sLaYA@mail.gmail.com' \
--to=ahmedzsales18@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox