From: Peter R <peter_r@gmx•com>
To: "Jorge Timón" <jtimon@jtimon•cc>
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 09:38:26 -0700 [thread overview]
Message-ID: <EA4673B8-C895-40F8-A71D-4BD5045A57D8@gmx.com> (raw)
In-Reply-To: <CABm2gDrOt2m6xfYjtVJne6Cm2nawXtA2-a4y7kaEA1fEgkUUUA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1430 bytes --]
> On Oct 2, 2015, at 1:20 AM, Jorge Timón via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> wrote:
> On Oct 2, 2015 10:03 AM, "Daniele Pinna via bitcoin-dev" <bitcoin-dev@lists•linuxfoundation.org <mailto: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.
>
I encourage Alex and Dmitry to consider submitting their paper to Ledger, where it will be reviewed objectively and with an open mind. The authors have motivated their work, framed it in its scholarly context, and made explicit the contributions their paper makes. Their manuscript, "Asymmetric proof-of-work based on the Generalized Birthday problem," clearly represents a great deal of work by the authors and I commend them for their efforts.
In the link Adam Back provided, Greg Maxwell mentioned that “it is far from clear that 'memory hardness' is actually a useful goal.” I agree with this statement; however, regardless of whether memory hardness turns out to be a useful goal in regards to cryptocurrency or not, a paper analyzing memory-hard proof-of-work schemes is certainly useful in helping us to figure that out.
Best regards,
Peter
[-- Attachment #2: Type: text/html, Size: 2146 bytes --]
next prev parent reply other threads:[~2015-10-02 16:38 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
2015-10-02 16:38 ` Peter R [this message]
[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=EA4673B8-C895-40F8-A71D-4BD5045A57D8@gmx.com \
--to=peter_r@gmx$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=daniele.pinna@gmail$(echo .)com \
--cc=jtimon@jtimon$(echo .)cc \
/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