From: Peter Todd <pete@petertodd.org>
To: Sergio Demian Lerner <sergio.d.lerner@gmail.com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Drivechain proposal using OP_COUNT_ACKS
Date: Sun, 2 Oct 2016 12:17:17 -0400 [thread overview]
Message-ID: <20161002161717.GA13915@fedora-21-dvm> (raw)
In-Reply-To: <CAKzdR-rsy1m-H4fYFuCim5+YJi_C2kgjxymM8A7_nEuqsZoO+g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1222 bytes --]
On Sun, Oct 02, 2016 at 12:49:08PM -0300, Sergio Demian Lerner via bitcoin-dev wrote:
I think your history of patenting(1) Bitcoin consensus relevant technology is
sufficient by itself to be extremely dubious of any proposals coming from you
or your colleagues; patents on Bitcoin consensus technology are a serious
threat to decentralization. Personally, I'm NACKing this proposal on that basis
alone.
You need to rectify this dangerous and unethical behavior in a convincing,
legally binding way. I'd suggest looking into Blockstream's patent pledges as a
way forward:
https://www.blockstream.com/about/patent_pledge/
I see no reason to have any further discussion of your proposal until this is
rectified.
1) "AsicBoost is a patent-pending method to improve the efficiency and cost of Bitcoin mining by approximately 20%"
http://www.asicboost.com/single-post/2016/03/24/AsicBoost-Press-Release
> Since ScalingBitcoin is close, I think this is a good moment to publish our
> proposal on drivechains. This BIP proposed the drivechain we'd like to use
> in RSK (a.k.a. Rootstock) two-way pegged blockchain and see it implemented
--
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 16:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-02 15:49 [bitcoin-dev] Drivechain proposal using OP_COUNT_ACKS Sergio Demian Lerner
2016-10-02 16:17 ` Peter Todd [this message]
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
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=20161002161717.GA13915@fedora-21-dvm \
--to=pete@petertodd.org \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=sergio.d.lerner@gmail.com \
/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