From: Sergio Demian Lerner <sergio.d.lerner@gmail•com>
To: Btc Drak <btcdrak@gmail•com>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] About ASICBoost
Date: Sun, 2 Oct 2016 19:25:52 -0300 [thread overview]
Message-ID: <CAKzdR-p4gs3nz9efYadTehi-KhCh7xRoVXqPN==U9z1PM9SLpw@mail.gmail.com> (raw)
In-Reply-To: <CADJgMzuPrvoz5TpO+SvHs_Eix7usFTPuEgxhocjc8tf23LnuOg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1086 bytes --]
It's good you bring that point, and it's very interesting to analyze what
happened then.
We shared our findings with some core developers much earlier than the BIP
proposal. Wether they kept it secret or they shared it with some ASIC
manufacturers is something I don't know. I even mentioned my wishes to try
to give the patent to public domain.
I remember the reason we proposed the BIP is because ASICBoost actually
does NOT require that BIP at all. And that BIP was not a consensus change,
but just a semantic re-interpretation.
ASICBoost can roll the nVersion field or the Merkle root hash. Doing the
former currently generates a strange warning message on nodes and can be
confusing, but doing the later makes ASICBoost completely stealthy. That
BIP could help the community to monitor its use in non-confusing way to the
users. What is worse? I think forcing it to be stealthy is worse.
I never opposed changing Bitcoin to be more decentralized, but hard-forking
a change to the PoW function may be contentious and that path of thought
must be walked very carefully.
Regards
[-- Attachment #2: Type: text/html, Size: 1273 bytes --]
next prev parent reply other threads:[~2016-10-02 22:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-02 17:13 Sergio Demian Lerner
2016-10-02 19:36 ` Btc Drak
2016-10-02 22:25 ` Sergio Demian Lerner [this message]
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
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='CAKzdR-p4gs3nz9efYadTehi-KhCh7xRoVXqPN==U9z1PM9SLpw@mail.gmail.com' \
--to=sergio.d.lerner@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=btcdrak@gmail$(echo .)com \
/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