public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Warren Togami Jr." <wtogami@gmail.com>
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Open Block Chain Licence, BIP[xxxx] Draft
Date: Wed, 2 Sep 2015 01:56:30 -0700	[thread overview]
Message-ID: <CAEz79Po2S0VS0xEvzciLq4w7bLMuLF3Kyr0H5h+jWeYZW1QSpQ@mail.gmail.com> (raw)
In-Reply-To: <CADr=VrRT2tdN0jjkZ7HjjeyqonrHG=j+uh8m1L2nhew7c1gnng@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3135 bytes --]

I am skeptical that any license for the blockchain itself is needed because
of the possibility that the blockchain is not entitled to copyright
protection.  While I am not a lawyer, I have stared hard at the copyright
doctrine of the U.S. in multiple law school Intellectual Property courses
and during my previous career in Open Source Software where copyright
matters a great deal.

As each owner of a
> coin makes a transfer by digitally signing a hash of the previous
> transaction along with the
> new owner’s public key, the block chain is a perpetual compilation of
> unique data.
> *It is therefore compiled in a creative and non-obvious way.* In the USA,
> for example, these
> attributes confer legal protections for databases which have been ruled
> upon by the courts.


This portion of your paper I believe is not true and requires citations if
you want to be convincing.  Is it truly "creative and non-obvious"?  My
understanding under at least U.S. law, the blockchain may not be entitled
to copyright protection because a compilation created in a mechanical
manner is not a creative work of a human.

I suppose a transaction could contain a "creative" element if it contains
arbitrary bytes of a message or clever script.  For the most part though
most of what you call "digitally signing a hash of the previous transaction
along with the new owner’s public key" is purely the result of a mechanical
process and really is not creative.  Furthermore, even if that output were
"non-obvious", obviousness has nothing to do with copyrightability.

Your license is correct in intent in attempting to exclude from the royalty
free grant works within the blockchain that themselves may be subject to
copyright of third parties.  The elements within the blockchain may be
entitled individually to copyright if they are in any way a creative work
of a human, but as a compilation I am doubtful the blockchain itself is
entitled to copyright.

I understand copyright with respect to databases can be different under
other jurisdictions.  Your paper mentions the European database law that is
indeed different from the U.S.  Your paper is incomplete in scholarly and
legal citations.  I myself and we as a community don't know enough.  I
suppose this topic merits further study.

Warren Togami

On Tue, Sep 1, 2015 at 6:30 AM, 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
>
>

[-- Attachment #2: Type: text/html, Size: 4333 bytes --]

  parent reply	other threads:[~2015-09-02  8:56 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-01 13:30 [bitcoin-dev] Open Block Chain Licence, BIP[xxxx] Draft Ahmed Zsales
2015-09-01 13:43 ` Milly Bitcoin
2015-09-01 13:50 ` Bryan Bishop
2015-09-01 15:11   ` Ahmed Zsales
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. [this message]
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=CAEz79Po2S0VS0xEvzciLq4w7bLMuLF3Kyr0H5h+jWeYZW1QSpQ@mail.gmail.com \
    --to=wtogami@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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