From: Peter Todd <pete@petertodd•org>
To: Andrew Johnson <andrew.johnson83@gmail•com>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Drivechain proposal using OP_COUNT_ACKS
Date: Sun, 2 Oct 2016 13:24:15 -0400 [thread overview]
Message-ID: <20161002172415.GA18641@fedora-21-dvm> (raw)
In-Reply-To: <CAAy62_+cqR0-DBbKhePo+VqTJc099zXJR0EurLyb1XURUCT36g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1142 bytes --]
On Sun, Oct 02, 2016 at 12:18:08PM -0500, Andrew Johnson wrote:
> The purpose of this list is highly technical discussion, not political
> disagreements.
>
> Is this particular proposal encumbered by a licensing type, patent, or
> pending patent which would preclude it from being used in the bitcoin
> project? If not, you're wildly off topic.
I don't know if it is; that's the problem.
Given Sergio's prior behavior of attempting to use patents offensively, it's
perfectly reasonable to suspect that Rootstock does in fact intend to encumber
this proposal with patents. So the obvious thing to do, is for Rootstock to
give us all a legally binding guarantee that they will not be using patents
offensively, eliminating the problem and allowing us to return to productive
collaboration.
Remember that this kind of requirement is very common in standards bodies, e.g.
by having all companies contributing to the standards in question join a patent
pool, or by making legally binding pledges/licenses to ensure any patents they
hold can't be used offensively.
--
https://petertodd.org 'peter'[:-1]@petertodd.org
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2016-10-02 17:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-02 15:49 Sergio Demian Lerner
2016-10-02 16:17 ` Peter Todd
2016-10-02 17:00 ` Sergio Demian Lerner
2016-10-02 17:11 ` Peter Todd
2016-10-02 17:18 ` Andrew Johnson
2016-10-02 17:24 ` Peter Todd [this message]
2016-10-02 21:28 ` Luke Dashjr
2016-10-02 21:46 ` Russell O'Connor
2016-10-02 22:36 ` Sergio Demian Lerner
[not found] ` <CAMZUoKnE9VNnUHrDTtZOroBp=SC_eY1fEAsEOz=4b1=5v_wHaA@mail.gmail.com>
2016-10-02 23:00 ` [bitcoin-dev] Fwd: " Russell O'Connor
[not found] ` <CAKzdR-oxpDdXEcPTYtj6os58cVMgwoqyXvu5UMMQzD3QbvMtxA@mail.gmail.com>
2016-10-02 23:26 ` [bitcoin-dev] " Russell O'Connor
2016-10-02 21:54 ` Russell O'Connor
2016-10-02 17:26 ` Sergio Demian Lerner
2016-10-02 17:34 ` Peter Todd
2016-10-02 18:17 ` Russell O'Connor
2016-10-24 17:37 ` Johnson Lau
2016-10-25 16:38 ` Sergio Demian Lerner
2016-10-25 17:45 ` Johnson Lau
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=20161002172415.GA18641@fedora-21-dvm \
--to=pete@petertodd$(echo .)org \
--cc=andrew.johnson83@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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