Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 4522D121D for ; Tue, 1 Sep 2015 22:21:02 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-lb0-f176.google.com (mail-lb0-f176.google.com [209.85.217.176]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 669221E2 for ; Tue, 1 Sep 2015 22:21:01 +0000 (UTC) Received: by lbcao8 with SMTP id ao8so7846046lbc.3 for ; Tue, 01 Sep 2015 15:20:59 -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 :cc:content-type; bh=Di6shBY3LaNLPnb5QFvMgyKMui3/YHzQXtpdgYlU5go=; b=e86xGZnjc+pVT4sTQ0IZdz0t5Om4MQgad6e5Ugm3gEVWYp3q9tge/q3VZx2L4loJzu nk7AOt7QvneZIp6uKeNcZIUWXp4uHwq0oUUTJeOv2lJIGcXwKKvttvPvnS6c1nJdC91j GRyFWZCFPjyIEvHN1UQJEI320nvcRhWWBHBtQplcI45w4UcUVrrW7Lvwk3fB+AquT7Pw HM7RjDPI/t9rj0+9t9WCd/c4C765nda9DrGAaSSDBGGJNf0wmh8+lhLFQyQO73x6c1fj TJC9J3GcR+Huy3fBtrwcIwv3kTHML5NNu4MtnktFOEhIjLZLpKumJP+Zdqqvt0pZadfT +/6w== MIME-Version: 1.0 X-Received: by 10.152.6.41 with SMTP id x9mr11284311lax.120.1441146059698; Tue, 01 Sep 2015 15:20:59 -0700 (PDT) Received: by 10.114.220.225 with HTTP; Tue, 1 Sep 2015 15:20:59 -0700 (PDT) Received: by 10.114.220.225 with HTTP; Tue, 1 Sep 2015 15:20:59 -0700 (PDT) In-Reply-To: References: Date: Wed, 2 Sep 2015 00:20:59 +0200 Message-ID: From: Natanael To: Btc Drak Content-Type: multipart/alternative; boundary=089e0141a9a2f53a4e051eb6f6a9 X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,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 Cc: Bitcoin Dev 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Sep 2015 22:21:02 -0000 --089e0141a9a2f53a4e051eb6f6a9 Content-Type: text/plain; charset=UTF-8 Den 2 sep 2015 00:03 skrev "Btc Drak via bitcoin-dev" < bitcoin-dev@lists.linuxfoundation.org>: > > 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. Worse yet - transaction malleability creates derative works with multiple copyright holders (the original one, plus the author of the modification). Is that even legal to do? What to do if a miner unknowingly accepts an illegally modified transaction in a block? And can he who modified it ALSO sue anybody replicating the block for infringement? Better just put everything in public domain, or the closest thing to it you can get. Copyright in the blockchain is essentially the DVDCSS illegal prime mess all over again, but in a P2P network. --089e0141a9a2f53a4e051eb6f6a9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


Den 2 sep 2015 00:03 skrev "Btc Drak via bitcoin-dev" <bitcoin-dev@lists.linuxfo= undation.org>:
>
> I think it gets worse. Who are the copyright owners (if this actually<= br> > applies). You've got people publishing transaction messages, you&#= 39;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<= br> > the messages are reproducing others copyright/licensed material? It= 9;s
> not possible to license someone else's work. There are plenty rabb= it
> holes to go down with this train of thought.

Worse yet - transaction malleability creates derative works = with multiple copyright holders (the original one, plus the author of the m= odification). Is that even legal to do? What to do if a miner unknowingly a= ccepts an illegally modified transaction in a block? And can he who modifie= d it ALSO sue anybody replicating the block for infringement?

Better just put everything in public domain, or the closest = thing to it you can get. Copyright in the blockchain is essentially the DVD= CSS illegal prime mess all over again, but in a P2P network.

--089e0141a9a2f53a4e051eb6f6a9--