From: Milly Bitcoin <milly@bitcoins.info>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Open Block Chain Licence, BIP[xxxx] Draft
Date: Tue, 1 Sep 2015 18:42:39 -0400 [thread overview]
Message-ID: <55E629DF.3030407@bitcoins.info> (raw)
In-Reply-To: <CADr=VrQeQ2=Htcen-oJrJWWhf5aQ8-cjYK28ic1UWNFWMf2nDQ@mail.gmail.com>
> The general points and questions you have raised are covered in the
> draft BIP:
No, the BIP makes some weird statements that don't really make sense.
Number one rule here: To put a license on something you have to own it
in the first place.
Let's say for the sake of argument that Miners own the copyright on a
block they find (as pointed out something like does not normally get
copyright protection but let's just pretend). Then the miner can charge
a fee for any public block explorer that wants to display the block at
their web site. They could also try to collect a fee from anyone who
distributes it (like Bitcoin users using p2p to distribute the
blockchain). A copyright is about protecting revenue. Is there some
other purpose of putting a license on intellectual property?
Also, it is not up to you, or anyone else, to come up with the form of a
license to control data owned by someone else. How can you force miners
or users to use any specific license that you come up with?
There are a number of other weird statements that really don't make any
kind of sense:
"In the USA, for example, these attributes confer legal protections for
databases which have been ruled upon by the courts." I have no idea
what this means or what court cases you are referring to.
"The Bitcoin Core Miners" is not an identifiable entity and cannot own
intellectual property rights. What is the purpose of you putting a
notice that some unidentifiable entity has some sort of rights over the
blockchain data? You are not that entity and neither are the
developers. If there are rights it is up to miners to come up with
their license.
"[users] own the rights to their individual transactions through
cryptograph security." I have no idea what this means. It is certainly
not intellectual property rights of anything I am familiar with. Once
again, if the users do have intellectual rights then someone else cannot
dictate the terms of the license. They could charge a fee for miners
publishing their transaction data.
Russ
next prev parent reply other threads:[~2015-09-01 22:42 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 [this message]
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=55E629DF.3030407@bitcoins.info \
--to=milly@bitcoins.info \
--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