From: "Jorge Timón" <jtimon@jtimon.cc>
To: Daniele Pinna <daniele.pinna@gmail.com>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Dev-list's stance on potentially altering the PoW algorithm
Date: Fri, 2 Oct 2015 10:20:55 +0200 [thread overview]
Message-ID: <CABm2gDrOt2m6xfYjtVJne6Cm2nawXtA2-a4y7kaEA1fEgkUUUA@mail.gmail.com> (raw)
In-Reply-To: <CAEgR2PFQtr78B3t147=3Ko4VnTGevb0QCySk=hDSqeFHZk=MPQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 664 bytes --]
On Oct 2, 2015 10:03 AM, "Daniele Pinna via bitcoin-dev" <
bitcoin-dev@lists.linuxfoundation.org> wrote:
>
> should an algorithm that guarantees protection from ASIC/FPGA
optimization be found.
This is demonstrably impossible: anything that can be done with software
can be done with hardware. This is computer science 101.
And specialized hardware can always be more efficient, at least
energy-wise.
On the other hand, BIP99 explicitly contemplates "anti-miner hardforks"
(obviously not for so called "ASIC-resistance" [an absurd term coined to
promote some altcoins], but just for restarting the ASIC and mining market
in case mining becomes too centralized).
[-- Attachment #2: Type: text/html, Size: 838 bytes --]
next prev parent reply other threads:[~2015-10-02 8:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 8:02 [bitcoin-dev] Dev-list's stance on potentially altering the PoW algorithm Daniele Pinna
2015-10-02 8:20 ` Jorge Timón [this message]
2015-10-02 8:30 ` Adam Back
2015-10-02 8:31 ` Daniele Pinna
2015-10-02 10:46 ` NxtChg
2015-10-02 11:00 ` Jorge Timón
2015-10-02 16:38 ` Peter R
[not found] ` <CALqxMTH6r8eJN2Xw+nn1z=6x9Q3TRSQQ6ZMXsmHPyX8dNx+EgA@mail.gmail.com>
2015-10-02 8:30 ` Daniele Pinna
2015-10-02 16:45 ` Gregory Maxwell
2015-10-02 21:37 ` Dave Scotese
2015-10-02 21:31 ` Luke Dashjr
2015-10-02 23:19 ` Milly Bitcoin
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=CABm2gDrOt2m6xfYjtVJne6Cm2nawXtA2-a4y7kaEA1fEgkUUUA@mail.gmail.com \
--to=jtimon@jtimon.cc \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=daniele.pinna@gmail.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