path: root/93/3f868138e85f9a59dc2cac446c0cf47e37d60e

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 E2F7F135C
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue,  1 Sep 2015 22:03:13 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com
	[209.85.212.178])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 6337615E
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue,  1 Sep 2015 22:03:13 +0000 (UTC)
Received: by wicge5 with SMTP id ge5so21402519wic.0
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue, 01 Sep 2015 15:03:12 -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=YSqTU4g3YmWgR/QxEZRyLy1FVgrJylW6BpzNFnehj0M=;
	b=SjWa2bNvYiWwg3XRT1tuVnJS4XA8uHbfAHFk29lNNwbm+1BhtIwOVCc8MxgOXYhfvy
	6CJSKIk58aHkG/ikyCK1rAUT0pAzqBuTh//oWaI5Sdki5+7jCotCrilPxe2gMXpFrmEV
	NDfMWfKW4YxtSxqy9nkUsSidHA/uE7qm1AFngFdpNBXmnrdWYNhYa8BIxRfIwlrgbGaI
	jsQSQqj2XrOvQFqM306qfZFb8VbcRSmwEabclsdlpA41Bg2kuBa6xU0Mk2mb4Hy98D30
	8sxdKgLcUc4KQj1edRd/sLnyZvMSec+ruy+6GkhYv9229AHjUHs0i4RGIEkxVNjnZfyi
	+SbA==
X-Received: by 10.194.121.131 with SMTP id lk3mr34549179wjb.77.1441144992145; 
	Tue, 01 Sep 2015 15:03:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.28.211.16 with HTTP; Tue, 1 Sep 2015 15:02:52 -0700 (PDT)
In-Reply-To: <CADr=VrQ42Gqv7fUFVpaburw0=08SNXb0TUCBWd3arREbpdfCkA@mail.gmail.com>
References: <CADr=VrRT2tdN0jjkZ7HjjeyqonrHG=j+uh8m1L2nhew7c1gnng@mail.gmail.com>
	<CADJgMztScEsDEy277Jksy2RckbpzeRw6RbQzyVrdkjJSS=hHPA@mail.gmail.com>
	<CADr=VrQ42Gqv7fUFVpaburw0=08SNXb0TUCBWd3arREbpdfCkA@mail.gmail.com>
From: Btc Drak <btcdrak@gmail.com>
Date: Tue, 1 Sep 2015 23:02:52 +0100
Message-ID: <CADJgMzvBCiHJo++zrZtA4XuMnNd8D8fHEiS4E2OfoKm4j8sY1w@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:03:14 -0000

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
>