From: Natanael <natanael.l@gmail•com>
To: "JOSE FEMENIAS CAÑUELO" <jose.femenias@gmail•com>,
"Bitcoin Dev" <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Possible change to the MIT license
Date: Tue, 13 Feb 2018 15:25:10 +0100 [thread overview]
Message-ID: <CAAt2M1-fEnQxjX40c-sjUYpfLpJtS-fy5t244vUOZSb8Pm=MrQ@mail.gmail.com> (raw)
In-Reply-To: <65F92B37-48C1-4CD5-8F17-47BF9BD231A9@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1147 bytes --]
Den 13 feb. 2018 15:07 skrev "JOSE FEMENIAS CAÑUELO via bitcoin-dev" <
bitcoin-dev@lists•linuxfoundation.org>:
***
NO PART OF THIS SOFTWARE CAN BE INCLUDED IN ANY OTHER PROJECT THAT USES THE
NAME BITCOIN AS PART OF ITS NAME AND/OR ITS MARKETING MATERIAL UNLESS THE
SOFTWARE PRODUCED BY THAT PROJECT IS FULLY COMPATIBLE WITH THE BITCOIN
(CORE) BLOCKCHAIN
***
That's better solved with trademarks. (whoever would be the trademark
holder - Satoshi?)
This would also prohibit any reimplementation that's not formally verified
to be perfectly compatible from using the name.
It also adds legal uncertainty.
Another major problem is that it neither affects anybody forking older
versions of Bitcoin, not people using existing independent blockchain
implementations and renaming them Bitcoin-Whatsoever.
And what happens when an old version is technically incompatible with a
future version by the Core team due to not understanding various new
softforks? Which version wins the right to the name?
Also, being unable to even mention Bitcoin is overkill.
The software license also don't affect the blockchain data.
[-- Attachment #2: Type: text/html, Size: 1986 bytes --]
next prev parent reply other threads:[~2018-02-13 14:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 12:25 JOSE FEMENIAS CAÑUELO
2018-02-13 14:25 ` Natanael [this message]
2018-02-13 15:24 ` Jameson Lopp
2018-02-13 15:37 ` Brian Lockhart
2018-02-13 15:45 ` Jameson Lopp
2018-02-13 17:04 ` Patrick Murck
2018-02-13 15:45 ` Aymeric Vitte
2018-02-13 15:47 ` Bedri Ozgur Guler
2018-02-13 17:28 ` Felix Wolfsteller
2018-02-13 19:08 ` Cory Fields
2018-02-13 19:08 ` CryptAxe
2018-02-13 15:22 ` Aymeric Vitte
2018-02-13 17:53 ` Luke Dashjr
2018-02-13 17:25 Adam Ficsor
2018-02-13 17:46 ` Daniel Robinson
2018-02-14 10:09 Damian Williamson
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='CAAt2M1-fEnQxjX40c-sjUYpfLpJtS-fy5t244vUOZSb8Pm=MrQ@mail.gmail.com' \
--to=natanael.l@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=jose.femenias@gmail$(echo .)com \
/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