From: Tom Harding <tomh@thinlink.com>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Making AsicBoost irrelevant
Date: Wed, 11 May 2016 19:27:09 -0700 [thread overview]
Message-ID: <7a9bf5ac-5d23-c7cd-e297-f7dd6503919b@thinlink.com> (raw)
In-Reply-To: <CAKzdR-ou2FYjjxmRBLARhvfhHO-46weiMc2Q2f+GZf1E_JUEAg@mail.gmail.com>
On 5/10/2016 2:43 PM, Sergio Demian Lerner via bitcoin-dev wrote:
>
> If we change the protocol then the message to the ecosystem is that
> ASIC optimizations should be kept secret.
Further to that point, if THIS optimization had been kept secret, nobody
would be talking about doing anything, as with countless other
optimizations.
next prev parent reply other threads:[~2016-05-12 2:27 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-10 18:57 [bitcoin-dev] Making AsicBoost irrelevant Peter Todd
2016-05-10 20:27 ` Tier Nolan
2016-05-10 21:35 ` Matt Corallo
2016-05-10 21:43 ` Sergio Demian Lerner
2016-05-10 22:59 ` Matt Corallo
2016-05-11 12:20 ` Sergio Demian Lerner
2016-05-11 13:08 ` Marek Palatinus
2016-05-11 21:01 ` Matt Corallo
2016-05-11 22:16 ` Simon Liu
2016-05-11 22:50 ` Peter Todd
2016-05-11 14:28 ` Luke Dashjr
2016-05-11 16:24 ` Timo Hanke
2016-05-11 18:28 ` Timo Hanke
2016-05-11 22:49 ` Timo Hanke
2016-05-12 2:27 ` Tom Harding [this message]
2016-05-12 2:31 ` Allen Piscitello
2016-05-12 2:33 ` Peter Todd
2016-05-12 4:01 ` Tom Harding
2016-05-10 21:49 ` Marco Pontello
2016-05-10 22:17 ` Sergio Demian Lerner
2016-05-10 22:27 ` Chris Riley
2016-05-11 3:14 ` Timo Hanke
2016-05-11 9:21 ` Jannes Faber
2016-05-11 10:36 ` Henning Kopp
2016-05-11 10:47 ` Jannes Faber
2016-05-11 22:42 ` Timo Hanke
2016-05-11 22:58 ` Gregory Maxwell
2016-05-12 7:29 ` Tom
2016-05-12 11:05 ` Jorge Timón
2016-05-11 14:07 ` Jorge Timón
2016-05-11 14:18 ` Sergio Demian Lerner
2016-05-11 14:30 ` Jannes Faber
2016-05-11 20:50 ` Matt Corallo
2016-05-11 22:00 ` James Hilliard
2016-05-11 23:01 ` Peter Todd
2016-05-12 0:02 ` Gregory Maxwell
2016-05-12 1:23 ` Russell O'Connor
2016-05-12 1:58 ` Peter Todd
2016-05-12 1:58 ` Matt Corallo
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=7a9bf5ac-5d23-c7cd-e297-f7dd6503919b@thinlink.com \
--to=tomh@thinlink.com \
--cc=bitcoin-dev@lists.linuxfoundation.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