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

On Sun, Oct 2, 2016 at 11:19 PM, Matt Corallo <lf-lists@mattcorallo.com> wrote:
> 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.

We can't change the past (besides, would you want BCF to have owned
that patent? I didn't)-- only the future.

To do so requires collaboration, so lets focus on that.


      reply	other threads:[~2016-10-02 23:27 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
2016-10-02 23:27         ` Gregory Maxwell [this message]

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