From: "Jorge Timón" <jtimon@jtimon•cc>
To: NxtChg <nxtchg@hush•com>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>,
Daniele Pinna <daniele.pinna@gmail•com>
Subject: Re: [bitcoin-dev] Dev-list's stance on potentially altering the PoW algorithm
Date: Fri, 2 Oct 2015 13:00:57 +0200 [thread overview]
Message-ID: <CABm2gDrp1SJqRKg5+cgw03BJn84oROQya05pofU4fawRT3UGkQ@mail.gmail.com> (raw)
In-Reply-To: <20151002104630.5F7A720101@smtp.hushmail.com>
[-- Attachment #1: Type: text/plain, Size: 688 bytes --]
On Oct 2, 2015 12:46 PM, "NxtChg" <nxtchg@hush•com> wrote:
>
>
> >...obviously not for so called "ASIC-resistance" [an absurd term coined
to promote some altcoins]
>
> Yet another fallacy of "all-or-nothing" thinking, which is so abundant in
the Core camp.
>
> The fact that you can build ASIC for any kind of algorithm _in_theory_
doesn't mean you can't make it _arbitrary_hard_ in practice.
>
> So I would tone down the arrogance a bit.
>
ASIC-RESISTANCE is simply not possible, I'm sorry if that position strikes
you as arrogant. Note that I didn't say anything about memory-hard, which
is possible (but not necessarily preferrable to
simple-to-implement-in-hardware pow algorithms).
[-- Attachment #2: Type: text/html, Size: 901 bytes --]
next prev parent reply other threads:[~2015-10-02 11:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 8:02 Daniele Pinna
2015-10-02 8:20 ` Jorge Timón
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 [this message]
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=CABm2gDrp1SJqRKg5+cgw03BJn84oROQya05pofU4fawRT3UGkQ@mail.gmail.com \
--to=jtimon@jtimon$(echo .)cc \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=daniele.pinna@gmail$(echo .)com \
--cc=nxtchg@hush$(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