From: Gregory Maxwell <gmaxwell@gmail•com>
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 16:45:45 +0000 [thread overview]
Message-ID: <CAAS2fgTSjnjk60_c0nc4UYYV-w3ZonO_6HuLW+k-SVPyCSc-jQ@mail.gmail.com> (raw)
In-Reply-To: <CAEgR2PFCLKSDveHQ1xZX0zSdT6_C=ee0-JCQ3REARhCLU6nCYg@mail.gmail.com>
On Fri, Oct 2, 2015 at 8:30 AM, Daniele Pinna via bitcoin-dev
<bitcoin-dev@lists•linuxfoundation.org> wrote:
> The recently published paper I referenced cite's the Cuckoo cycle algorithm,
> discusses its limitations and explains how their proposed algorithm greatly
> improves on it.
They discuss a very old version of the Cuckoo cycle paper, and I
believe none of their analysis is applicable to the most recent
revision. :(
In any case, I commented more about functions of this class here:
https://www.reddit.com/r/Bitcoin/comments/3n5nws/research_paper_asymmetric_proofofwork_based_on/cvl922x
I don't believe changing the POW function is impossible in principle,
but I expect it would only happen due to problems with the composition
of current hash-power and not even if it were universally agreed that
some other construction were technically better (though that is a high
bar.)
next prev parent reply other threads:[~2015-10-02 16:45 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
[not found] ` <CALqxMTH6r8eJN2Xw+nn1z=6x9Q3TRSQQ6ZMXsmHPyX8dNx+EgA@mail.gmail.com>
2015-10-02 8:30 ` Daniele Pinna
2015-10-02 16:45 ` Gregory Maxwell [this message]
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=CAAS2fgTSjnjk60_c0nc4UYYV-w3ZonO_6HuLW+k-SVPyCSc-jQ@mail.gmail.com \
--to=gmaxwell@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=daniele.pinna@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