From: praxeology_guy <praxeology_guy@protonmail•com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Praxeological Analysis of PoW Policy Changes, Re: ASICBOOST
Date: Thu, 06 Apr 2017 20:11:00 -0400 [thread overview]
Message-ID: <HMvQbNz-DH5yhGdXbW3GPQOjj6z5lP0H-nTKxvSMuj8emQcTCwyAhluGY67VINDFrO1CrMG_ImlKhJRNk1eE2Yj1bnZycQX8RCc4aiMFvOo=@protonmail.com> (raw)
In-Reply-To: <rwp8cX-r5lyaz_L10JuFh8xejucD5PWyc02ZJ6m7y39ddHo1IPgYJdhIvTl6oQNf-8-4PKQ_tUWEYxZW5gZd6KZvp2xz6iYv7n5GzvUCU0U=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 874 bytes --]
> "... put a damper on advancing the development of more efficient mining hardware, which is once again desirable to users as it makes the transaction ordering more future proof."
Run on sentence sorry. I meant to say that development of more efficient/mature mining hardware sooner is desirable to money owners/traders. So anything that could dis-incentivize R&D to mature ASICs would be bad. PoW policy changes should be made carefully in order to minimize this hampering effect.
I didn't mean to imply that Gregory Maxwell's current BIP countered/disabled both the evident and covert versions of asicboost. I think his BIP is a good idea, to quickly release a version that blocks the patented covert optimization... and then later we can consider taking steps to further disable the patented evident version of asicboost if it becomes a problem.
Cheers,
Praxeology Guy
[-- Attachment #2: Type: text/html, Size: 1018 bytes --]
prev parent reply other threads:[~2017-04-07 0:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 20:12 praxeology_guy
2017-04-07 0:11 ` praxeology_guy [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='HMvQbNz-DH5yhGdXbW3GPQOjj6z5lP0H-nTKxvSMuj8emQcTCwyAhluGY67VINDFrO1CrMG_ImlKhJRNk1eE2Yj1bnZycQX8RCc4aiMFvOo=@protonmail.com' \
--to=praxeology_guy@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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