public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Matt Corallo <lf-lists@mattcorallo.com>
To: Gregory Maxwell <greg@xiph.org>,
	Bitcoin Protocol Discussion
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] About ASICBoost
Date: Sun, 2 Oct 2016 23:19:08 +0000	[thread overview]
Message-ID: <57F195EC.30009@mattcorallo.com> (raw)
In-Reply-To: <CAAS2fgQ6Xip=6nrdSM82hAhd47CKGPXLCXMOkBohrZWxJyqFoQ@mail.gmail.com>

Even if the Bitcoin Foundation decided to recklessly disregard Bitcoin's
future centralization, I'm not sure going to them and asking them to pay
a license fee in order to keep from holding the rest of the Bitcoin
mining community hostage counts as "regard for centralization pressure".
It also doesn't excuse the lack of transparent licensing being available
today, or the lack of transparency when discussing it in public after
the patent had been filed.

Matt

On 10/02/16 22:58, Gregory Maxwell via bitcoin-dev wrote:
> On Sun, Oct 2, 2016 at 10:51 PM, Matt Corallo via bitcoin-dev
> <bitcoin-dev@lists.linuxfoundation.org> wrote:
>> If you had acted in a way which indicated even the slightest regard for
>> centralization pressure and the harm it can do to Bitcoin in the
>> long-term, then I dont think many would be blaming you. Instead of any
> 
> Sergio was concerned about centralization pressure in private. He
> reached out to the BCF on 2013-11-23 and asked if they would license
> the patent from him so they could make it equally available to all
> under "fair" terms.  BCF responded that they didn't think it (a
> proprietary patent encumbered enhancement that would make its user(s)
> 30% more effective than others) would be a big deal and basically
> encouraged him to go ahead and seek the patent.
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> 


  reply	other threads:[~2016-10-02 23:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-02 17:13 [bitcoin-dev] About ASICBoost Sergio Demian Lerner
2016-10-02 19:36 ` Btc Drak
2016-10-02 22:25   ` Sergio Demian Lerner
2016-10-02 22:56   ` Timo Hanke
2016-10-02 22:51 ` Matt Corallo
     [not found]   ` <CAAS2fgSwgdvb9gWc8A2SPhJAL36Ss4EY_DTtc6sQj=G3X66OWA@mail.gmail.com>
2016-10-02 22:58     ` Gregory Maxwell
2016-10-02 23:19       ` Matt Corallo [this message]
2016-10-02 23:27         ` Gregory Maxwell

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=57F195EC.30009@mattcorallo.com \
    --to=lf-lists@mattcorallo.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=greg@xiph.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