From: David Vorick <david.vorick@gmail•com>
To: Nick ODell <nickodell@gmail•com>,
Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Malice Reactive Proof of Work Additions (MR POWA): Protecting Bitcoin from malicious miners
Date: Mon, 20 Mar 2017 14:51:51 -0400 [thread overview]
Message-ID: <CAFVRnyrsH_Oh2XXzRf9P5shysw4ah6AGmHhNyJ582AAhnDcaTw@mail.gmail.com> (raw)
In-Reply-To: <CANN4kmdMcbQ9pYC44a02+wzzVzoMt8n5TAL=Z3bRaBkT_6Vnpg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 539 bytes --]
I am in support of having multiple PoW forks to choose from, but it is
indeed problematic to have one chain running a rotation of algorithms.
The reason I support multiple algos is because we don't want an attacker
secretly making asics ahead of time in the event of an emergency PoW fork.
We want them to be uncertain which of a large selection of algorithms are
going to be used, making pre-emptive asic manufacturing more difficult.
But once an algorithm is chosen that should be the end of the story, just
one algo without rotation.
[-- Attachment #2: Type: text/html, Size: 780 bytes --]
next prev parent reply other threads:[~2017-03-20 18:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-18 16:01 John Hardy
2017-03-20 15:38 ` Andrew Johnson
2017-03-20 15:46 ` John Hardy
2017-03-20 16:10 ` Andrew Johnson
2017-03-20 15:55 ` Marcos mayorga
2017-04-16 20:04 ` Erik Aronesty
2017-04-17 1:28 ` bfd
[not found] ` <CAJowKg+1vUBmr7cTzUy8gAdjEWTM_+07G9Z96Bo=wd6_htgv1Q@mail.gmail.com>
[not found] ` <CAJowKgJPjWb_S0jb+RJ9-90sucb=ZeU2-qrNqrVN5USTaxDjDw@mail.gmail.com>
2017-04-17 7:47 ` Erik Aronesty
[not found] ` <CAJowKgKqyb7DCs-yrbj4Z8Kzmgg0GCKXh+wwdSvfPHregiwdvA@mail.gmail.com>
[not found] ` <CAJowKgL=UmJvE0KpSsa20AJBF6Ur85ghRymHY+=11VOezmaaxw@mail.gmail.com>
2017-04-17 11:17 ` Erik Aronesty
2017-04-17 22:34 ` Natanael
2017-03-20 18:02 ` Nick ODell
2017-03-20 18:51 ` David Vorick [this message]
2017-03-20 21:29 ` John Hardy
2017-03-20 17:49 ` Bram Cohen
2017-03-20 21:23 ` John Hardy
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=CAFVRnyrsH_Oh2XXzRf9P5shysw4ah6AGmHhNyJ582AAhnDcaTw@mail.gmail.com \
--to=david.vorick@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=nickodell@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