public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Daniele Pinna <daniele.pinna@gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: [bitcoin-dev] Dev-list's stance on potentially altering the PoW algorithm
Date: Fri, 2 Oct 2015 10:02:43 +0200	[thread overview]
Message-ID: <CAEgR2PFQtr78B3t147=3Ko4VnTGevb0QCySk=hDSqeFHZk=MPQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 810 bytes --]

The following paper proposing an asymmetric memory-hard PoW had been
recently published:

http://eprint.iacr.org/2015/946.pdf

My intent is not to promote the paper as I have not finished studying it
myself. I am however interested in the dev-list's stance on potentially
altering the bitcoin PoW protocol should an algorithm that guarantees
protection from ASIC/FPGA optimization be found.

I assume that, given the large amount of money invested by some miners into
their industrial farms this would represent a VERY contentious hard fork.

It is, however, also true that a novel optimization-resistant algorithm
could greatly ameliorate decentralization in the bitcoin network due to a
resurgence of desktop/cellphone mining.

Where do the core devs stand on this matter, hypothetical as it may be?

Dpinna

[-- Attachment #2: Type: text/html, Size: 988 bytes --]

             reply	other threads:[~2015-10-02  8:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-02  8:02 Daniele Pinna [this message]
2015-10-02  8:20 ` [bitcoin-dev] Dev-list's stance on potentially altering the PoW algorithm 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
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='CAEgR2PFQtr78B3t147=3Ko4VnTGevb0QCySk=hDSqeFHZk=MPQ@mail.gmail.com' \
    --to=daniele.pinna@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /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